| |||||||||||||||||||
Re: ipw2100: firmware problem
From: James Ketrenos <jketreno@linux.intel.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. (Log in to post comments)
Re: ipw2100: firmware problem Posted Jun 17, 2005 5:38 UTC (Fri) by goaty (guest, #17783) [Link] I think it's entirely reasonable to use an initrd to do NFS root. You get much more flexibility that way, and reduce the amount of complexity that has to go into the kernel proper. It's quite clear to me that initrd's ARE the elegant way to handle this.
It's a pity they aren't easier to work with, but that's hardly the fault of userspace firmware loaders.
|
|||||||||||||||||||