| 1 |
>> it does not actually matter how you configured the driver -- built-in kernel or |
| 2 |
>> as module: everytime when driver operates the device, it checks whether firmware |
| 3 |
>> is loaded. |
| 4 |
> Are you sure about that? AFAIK firmware loading is only attempted once, |
| 5 |
> when the driver is first initialized. |
| 6 |
|
| 7 |
i'm not sure - just spent few minutes looking through the drivers/net/r8169.c |
| 8 |
code: the driver attempts to load firmware every time when opening a particular |
| 9 |
pci eth device |
| 10 |
|
| 11 |
>> functionality of /lib/udev/firmware is controlled by USE=extras. |
| 12 |
> That might have been the case at some point but now sys-fs/udev-164-r2 |
| 13 |
> and sys-fs/udev-171-r1 both install the firmware-related stuff (rules |
| 14 |
> and helper) even with USE=-extras |
| 15 |
|
| 16 |
you are right (also reviewed contents of udev tarbal and appropriate ebuild |
| 17 |
code) - `extras' use flag just adds some runtime dependencies |
| 18 |
|
| 19 |
> andrea |
| 20 |
> |
| 21 |
thank you, |
| 22 |
|
| 23 |
victor |
Archives