Lines Matching full:firmware
2 menu "Firmware loader"
5 tristate "Firmware loading facility" if EXPERT
10 This enables the firmware loading facility in the kernel. The kernel
11 will first look for built-in firmware, if it has any. Next, it will
12 look for the requested firmware in a series of filesystem paths:
15 o /lib/firmware/updates/UTS_RELEASE
16 o /lib/firmware/updates
17 o /lib/firmware/UTS_RELEASE
18 o /lib/firmware
22 need firmware.
27 enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
30 bool "Log filenames and checksums for loaded firmware"
36 Select this option to use dynamic debug to log firmware filenames and
37 SHA256 checksums to the kernel log for each firmware file that is
49 string "Build named firmware blobs into the kernel binary"
51 Device drivers which require firmware can typically deal with
52 having the kernel load firmware from the various supported
53 /lib/firmware/ paths. This option enables you to build into the
54 kernel firmware files. Built-in firmware searches are preceded
55 over firmware lookups using your filesystem over the supported
56 /lib/firmware paths documented on CONFIG_FW_LOADER.
58 This may be useful for testing or if the firmware is required early on
59 in boot and cannot rely on the firmware being placed in an initrd or
63 firmware files -- the same names that appear in MODULE_FIRMWARE()
66 /lib/firmware by default.
69 the usb8388.bin file into /lib/firmware, and build the kernel. Then
73 WARNING: If you include additional firmware files into your binary
82 string "Firmware blobs root directory"
84 default "/lib/firmware"
87 looks for the firmware files listed in the EXTRA_FIRMWARE option.
90 bool "Enable the firmware sysfs fallback mechanism"
94 This option enables a sysfs loading facility to enable firmware
97 firmware failed using the different /lib/firmware/ paths, or the
101 refer to Documentation/driver-api/firmware/fallback-mechanisms.rst.
103 The direct filesystem lookup for firmware is always used first now.
105 If the kernel's direct filesystem lookup for firmware fails to find
106 the requested firmware a sysfs fallback loading facility is made
111 acknowledge failure to find firmware as the timeout for the fallback
114 This used to be the default firmware loading facility, and udev used
115 to listen for uvents to load firmware for the kernel. The firmware
123 Since this was the default firmware loading facility at one point,
129 load firmware in case it is not found. One main reason for this may
130 be if you have drivers which require firmware built-in and for
131 whatever reason cannot place the required firmware in initramfs.
140 this may be that your firmware resides outside of the paths the kernel
147 to use it to look for and fetch the required firmware. Such type of
150 for provisioning. Since udev's firmware loading facility has been
152 want to load firmware based on uevents issued.
159 certain you need to support some really custom firmware loading
163 bool "Force the firmware sysfs fallback mechanism when possible"
167 to be used for all firmware requests which explicitly do not disable a
168 a fallback mechanism. Firmware calls which do prohibit a fallback
178 bool "Enable compressed firmware support"
180 This option enables the support for loading compressed firmware
181 files. The caller of firmware API receives the decompressed file
185 Compressed firmware support does not apply to firmware images
190 bool "Enable XZ-compressed firmware support"
200 bool "Enable ZSTD-compressed firmware support"
208 bool "Enable firmware caching during suspend"
212 Because firmware caching generates uevent messages that are sent
220 bool "Enable users to initiate firmware updates using sysfs"
225 sysfs interface that allows firmware updates to be initiated from
226 userspace. For example, FPGA based PCIe cards load firmware and FPGA
229 to support cards that rely on user-initiated updates for firmware files.