Linus Torvalds wrote:
quoted text
> 
> On Tue, 15 Jul 2008, Jeff Garzik wrote:
>> Which is why 'make modules_install' installs the firmware, or at least it did
>> before David W pushed upstream.
> 
> So you're literally just about making this be "make modules_install" 
> rather than "make firmware_install"
> 
> Ok. Are you going to be happy if "make modules_install" just copies the 
> firmware files of the affected modules too?

Re-read the above, and what you snipped.  My statement was

* upstream _already_ does this (installs firmware via modules_install)

* it is a good thing, because it means existing build scripts and 
processes will Do The Right Thing and produce a working driver

* thus eliminating the most common problem likely to be encountered

That does not eliminate all problems, because build processes still have 
hardcoded assumptions about outputs.

Restoring firmware-in-module ability closes the last logical hole, last 
fundamental flaw in the scheme, by permitting distros to reproduce 
precisely what they built in 2.6.26.

All of the regressions examples I am citing are cured by 
firmware-in-module, because they are all examples of problems that occur 
when you remove the ability to reproduce the same functional pieces as 
2.6.26.

	Jeff



--
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/