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