Lines Matching refs:firmware
7 This enables the firmware loading facility in the kernel. The kernel
8 will first look for built-in firmware, if it has any. Next, it will
9 look for the requested firmware in a series of filesystem paths:
12 o /lib/firmware/updates/UTS_RELEASE
13 o /lib/firmware/updates
14 o /lib/firmware/UTS_RELEASE
15 o /lib/firmware
19 need firmware.
24 enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
29 string "Build named firmware blobs into the kernel binary"
31 Device drivers which require firmware can typically deal with
32 having the kernel load firmware from the various supported
33 /lib/firmware/ paths. This option enables you to build into the
34 kernel firmware files. Built-in firmware searches are preceded
35 over firmware lookups using your filesystem over the supported
36 /lib/firmware paths documented on CONFIG_FW_LOADER.
38 This may be useful for testing or if the firmware is required early on
39 in boot and cannot rely on the firmware being placed in an initrd or
43 firmware files -- the same names that appear in MODULE_FIRMWARE()
46 /lib/firmware by default.
49 the usb8388.bin file into /lib/firmware, and build the kernel. Then
53 WARNING: If you include additional firmware files into your binary
62 default "/lib/firmware"
65 looks for the firmware files listed in the EXTRA_FIRMWARE option.
68 bool "Enable the firmware sysfs fallback mechanism"
70 This option enables a sysfs loading facility to enable firmware
73 firmware failed using the different /lib/firmware/ paths, or the
77 refer to Documentation/driver-api/firmware/fallback-mechanisms.rst.
79 The direct filesystem lookup for firmware is always used first now.
81 If the kernel's direct filesystem lookup for firmware fails to find
82 the requested firmware a sysfs fallback loading facility is made
87 acknowledge failure to find firmware as the timeout for the fallback
90 This used to be the default firmware loading facility, and udev used
91 to listen for uvents to load firmware for the kernel. The firmware
99 Since this was the default firmware loading facility at one point,
105 load firmware in case it is not found. One main reason for this may
106 be if you have drivers which require firmware built-in and for
107 whatever reason cannot place the required firmware in initramfs.
116 this may be that your firmware resides outside of the paths the kernel
123 to use it to look for and fetch the required firmware. Such type of
126 for provisioning. Since udev's firmware loading facility has been
128 want to load firmware based on uevents issued.
135 certain you need to support some really custom firmware loading
139 bool "Force the firmware sysfs fallback mechanism when possible"
143 to be used for all firmware requests which explicitly do not disable a