1 |
On Sun, 10 Feb 2013 10:10:51 +0200 |
2 |
Samuli Suominen <ssuominen@g.o> wrote: |
3 |
|
4 |
> # Samuli Suominen <ssuominen@g.o> (10 Feb 2013) |
5 |
> # The firmware cleanup, part #1. Can be unmasked after |
6 |
> # cleaning up the package if it's still needed. |
7 |
> # Some of these install to wrong directory, /lib64/firmware |
8 |
> # as opposed to correct /lib/firmware |
9 |
> # Some of these don't have maintainer |
10 |
> # Some of these are replaced by the firmware from the |
11 |
> # linux-firmware package: |
12 |
> # emerge -av linux-firmware |
13 |
> # If you still have a reason to keep the package, please |
14 |
> # let us know by filing a bug report. |
15 |
> net-wireless/ar9271-firmware |
16 |
|
17 |
I didn't know linux-firmware exists at all when added that |
18 |
to the tree (SRC_URI=http://linuxwireless.org). |
19 |
Fine by me. |
20 |
|
21 |
The source of confusion was non-working device by default. |
22 |
Maybe 'IUSE=+firmware; RDEPEND="firmware? ( sys-kernel/linux-firmware )"' |
23 |
for virtual/linux-sources would help user experience a bit. |
24 |
|
25 |
Sometimes firmware loader does not even write fw file |
26 |
it expects to be present on FS in dmesg (like certain broadcom drivers) |
27 |
thus it's nontrivial for user to figure out needed package to be installed. |
28 |
|
29 |
Thanks! |
30 |
|
31 |
-- |
32 |
|
33 |
Sergei |