On Tue, 15 Jul 2008, Willy Tarreau wrote:
quoted text
> > 
> > But once you can load a module, you can load the firmware. You just have 
> > to _remember_ to move it along with the module.
> 
> In order to transfer it, right now you feed it through a working device.
> When that device itself requires firmware to work, you will suddenly
> discover that it becomes harder and harder to get any communication device
> to work on your target system.

Willy, stop this blathering.

I suspect I will have to just delete this thread unread because it's so 
full of total crap.

This whole "working device" argument is total bullshit.

If the driver was a module before, it needed a module load to become 
working. If you could load the module, you could load the firmware. Thus 
the transfer is non-issue.

And if the driver was built-in, you can still build in the firmware.

And by proof of induction - your "now you feed it through a working 
device" - this also holds for that "a working device" driver. The device 
you load the module off has exactly the same rules: you can build in the 
firmware.

So it didn't get any harder at all. Except for the fact that you need to 
remember to install the firmware. 

Which is just about the same thing as asking people to remember to do 
"make modules_install" to get a working system. Yes, if you have a driver 
as a module, you need to install that module for the device to work. Yes, 
it's definitely "harder", but seriously..

			Linus
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/