|| ||"David S. Miller" <davem-AT-davemloft.net>|
|| ||Re: ipw2100: firmware problem|
|| ||Wed, 08 Jun 2005 12:43:32 -0700 (PDT)|
|| ||vda-AT-ilport.com.ua, pavel-AT-ucw.cz, jgarzik-AT-pobox.com, netdev-AT-oss.sgi.com,
From: James Ketrenos <email@example.com>
Date: Wed, 08 Jun 2005 12:10:37 -0500
> My approach is to make the driver so it supports as many usage models as
> possible, leaving policy to other components of the system.
I don't see how this kind of firmware load setup handles something
like an NFS root over such a device that requires firmware.
And let's not mention that I have to setup an initrd to make that
work, that's rediculious.
This is the kind of crap that happens when drivers in the kernel
are not self contained, and need "external stuff" to work properly.
It means that simple things like NFS root over the device do not
work in a straightforward, simple, and elegant manner.
I am likely to always take the position that device firmware
belongs in the kernel proper, not via these userland and filesystem
loading mechanism, none of which may be even _available_ when
we first need to get the device going.
to post comments)