Maxim Kammerer schrieb: > On Sat, Feb 16, 2013 at 8:14 AM, Rick "Zero_Chaos" Farina > <[email protected]> wrote: >>>> Kernel sources providing /lib/firmware itself shouldn't be a problem >>>> either, as that's just a dir, which many packages may own. The >>>> individual firmware files would be a problem, but the USE=firmware >>>> RDEPEND solution should solve that. >> What is everyone's opinion of adding a USE=firmware option to pull in >> PDEPEND="linux-firmware" in linux-2.eclass? > Not exactly an opinion, but a couple of notes: > > 1. Kernel's "make modules_install" triggers "make firmware_install", > which installs a strict subset of linux-firmware (for enabled modules > — e.g., "3com/typhoon.bin"). A way to work around that is to supply > INSTALL_FW_PATH=... to make.
Most if not all such conflicts can be avoided by USE="deblob" Best regards, Chí-Thanh Christopher Nguyễn
