Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more drivers.

[Jeff Garzik <jeff@garzik.org>]

Linus Torvalds wrote:
> 
> On Tue, 15 Jul 2008, Linus Torvalds wrote:
>> This is the "I'm too stupid to live" argument. I've already answered that. 
>> What's so hard with "make firmware_install"?
> 
> Btw, that is by no means the only way to handle it either. As I said in 
> other emails - about trying to find _productive_ questions to answer - 
> maybe we could also just install it in the modules directory or some 
> similar per-kernel location, and just teach request_firmware() to load 
> binary blobs directly.
> 
> Then - horror of horrors - we could even make "make modules_install" do 
> things like that automatically for you with some Makefile rule trickery.
> 
> See? There are _productive_ things you can do or ask others to do.
> 
> But singing the same "I'm so stupid that I cannot install the firmware" 
> song over and over again doesn't make me think you are worth listening to.

Can't you see that changing build processes takes time?  Fixing driver 
disk creation tools take time?  Validating that each driver is packaged 
with its correct firmware takes time?

With each driver converted, it is entirely possible that all users are 
completely unaware that it even had a firmware, much less that it now 
needs 'make firmware_install' to continue working.

If one is completely unaware of a driver's firmware need, (a) you don't 
know you need to install it and (b) you don't find out you need it until 
you boot and the driver fails to work.

I am trying to work to minimize (a) and (b) here, because as deployed, 
there are large chances for failure here, across a random selection of 
drivers.

	Jeff


P.S.  AFAIK, 'make modules_install' installs firmware, unless that 
change was not pushed upstream.