Gentoo Archives: gentoo-user

From: Nikos Chantziaras <realnc@×××××.de>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Re: Firmware exists but fails to load
Date: Mon, 15 Aug 2011 12:54:37
Message-Id: j2b4ql$gr$1@dough.gmane.org
In Reply to: Re: [gentoo-user] Re: Firmware exists but fails to load by Adam Carter
1 On 08/15/2011 02:59 PM, Adam Carter wrote:
2 >> Is the firmware path set correctly in the kernel config? In "Device
3 >> Drivers->Generic Driver Options", set "Firmware blobs root directory" to
4 >> "/lib/firmware" and build a new kernel.
5 >
6 > [...]
7 >
8 > Firmware blobs root directory is EXTRA_FIRMWARE_DIR which is only
9 > available once i enable EXTRA_FIRMWARE, but the help for that says;
10 > "This option allows firmware to be built into the kernel, for the
11 >
12 > │
13 > │ cases where the user either cannot or doesn't want to provide it
14 > from
15 > │
16 > │ userspace at runtime"
17 >
18 > So that's a workaround, not a fix, but it works so it'll do. Thanks.
19
20 It's not a workaround, but how it's supposed to work. "Loading from
21 userspace" means using a user-space program to load the firmware. This
22 is not what you're trying to do, since you don't have such a program.
23 You're trying to have the kernel itself load the firmware, and the
24 EXTRA_FIRMWARE mechanism is how this is done.
25
26 Your other option is writing a userspace program that reads the firmware
27 after the kernel has booted and patches it into the hardware. But why
28 would you want to do something like that anyway?

Replies

Subject Author
Re: [gentoo-user] Re: Firmware exists but fails to load Andrea Conti <alyf@××××.net>