Lines Matching full:firmware
2 menu "Firmware loader"
5 tristate "Firmware loading facility" if EXPERT
8 This enables the firmware loading facility in the kernel. The kernel
9 will first look for built-in firmware, if it has any. Next, it will
10 look for the requested firmware in a series of filesystem paths:
13 o /lib/firmware/updates/UTS_RELEASE
14 o /lib/firmware/updates
15 o /lib/firmware/UTS_RELEASE
16 o /lib/firmware
20 need firmware.
25 enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
36 string "Build named firmware blobs into the kernel binary"
38 Device drivers which require firmware can typically deal with
39 having the kernel load firmware from the various supported
40 /lib/firmware/ paths. This option enables you to build into the
41 kernel firmware files. Built-in firmware searches are preceded
42 over firmware lookups using your filesystem over the supported
43 /lib/firmware paths documented on CONFIG_FW_LOADER.
45 This may be useful for testing or if the firmware is required early on
46 in boot and cannot rely on the firmware being placed in an initrd or
50 firmware files -- the same names that appear in MODULE_FIRMWARE()
53 /lib/firmware by default.
56 the usb8388.bin file into /lib/firmware, and build the kernel. Then
60 WARNING: If you include additional firmware files into your binary
69 string "Firmware blobs root directory"
71 default "/lib/firmware"
74 looks for the firmware files listed in the EXTRA_FIRMWARE option.
77 bool "Enable the firmware sysfs fallback mechanism"
81 This option enables a sysfs loading facility to enable firmware
84 firmware failed using the different /lib/firmware/ paths, or the
88 refer to Documentation/driver-api/firmware/fallback-mechanisms.rst.
90 The direct filesystem lookup for firmware is always used first now.
92 If the kernel's direct filesystem lookup for firmware fails to find
93 the requested firmware a sysfs fallback loading facility is made
98 acknowledge failure to find firmware as the timeout for the fallback
101 This used to be the default firmware loading facility, and udev used
102 to listen for uvents to load firmware for the kernel. The firmware
110 Since this was the default firmware loading facility at one point,
116 load firmware in case it is not found. One main reason for this may
117 be if you have drivers which require firmware built-in and for
118 whatever reason cannot place the required firmware in initramfs.
127 this may be that your firmware resides outside of the paths the kernel
134 to use it to look for and fetch the required firmware. Such type of
137 for provisioning. Since udev's firmware loading facility has been
139 want to load firmware based on uevents issued.
146 certain you need to support some really custom firmware loading
150 bool "Force the firmware sysfs fallback mechanism when possible"
154 to be used for all firmware requests which explicitly do not disable a
155 a fallback mechanism. Firmware calls which do prohibit a fallback
165 bool "Enable compressed firmware support"
167 This option enables the support for loading compressed firmware
168 files. The caller of firmware API receives the decompressed file
172 Compressed firmware support does not apply to firmware images
177 bool "Enable XZ-compressed firmware support"
187 bool "Enable ZSTD-compressed firmware support"
195 bool "Enable firmware caching during suspend"
199 Because firmware caching generates uevent messages that are sent
207 bool "Enable users to initiate firmware updates using sysfs"
212 sysfs interface that allows firmware updates to be initiated from
213 userspace. For example, FPGA based PCIe cards load firmware and FPGA
216 to support cards that rely on user-initiated updates for firmware files.