Lines Matching full:firmware
2 menu "Firmware loader"
5 tristate "Firmware loading facility" if EXPERT
9 This enables the firmware loading facility in the kernel. The kernel
10 will first look for built-in firmware, if it has any. Next, it will
11 look for the requested firmware in a series of filesystem paths:
14 o /lib/firmware/updates/UTS_RELEASE
15 o /lib/firmware/updates
16 o /lib/firmware/UTS_RELEASE
17 o /lib/firmware
21 need firmware.
26 enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
29 bool "Log filenames and checksums for loaded firmware"
34 Select this option to use dynamic debug to log firmware filenames and
35 SHA256 checksums to the kernel log for each firmware file that is
39 bool "Rust Firmware Loader abstractions"
43 This enables the Rust abstractions for the firmware loader API.
54 string "Build named firmware blobs into the kernel binary"
56 Device drivers which require firmware can typically deal with
57 having the kernel load firmware from the various supported
58 /lib/firmware/ paths. This option enables you to build into the
59 kernel firmware files. Built-in firmware searches are preceded
60 over firmware lookups using your filesystem over the supported
61 /lib/firmware paths documented on CONFIG_FW_LOADER.
63 This may be useful for testing or if the firmware is required early on
64 in boot and cannot rely on the firmware being placed in an initrd or
68 firmware files -- the same names that appear in MODULE_FIRMWARE()
71 /lib/firmware by default.
74 the usb8388.bin file into /lib/firmware, and build the kernel. Then
78 WARNING: If you include additional firmware files into your binary
87 string "Firmware blobs root directory"
89 default "/lib/firmware"
92 looks for the firmware files listed in the EXTRA_FIRMWARE option.
95 bool "Enable the firmware sysfs fallback mechanism"
99 This option enables a sysfs loading facility to enable firmware
102 firmware failed using the different /lib/firmware/ paths, or the
106 refer to Documentation/driver-api/firmware/fallback-mechanisms.rst.
108 The direct filesystem lookup for firmware is always used first now.
110 If the kernel's direct filesystem lookup for firmware fails to find
111 the requested firmware a sysfs fallback loading facility is made
116 acknowledge failure to find firmware as the timeout for the fallback
119 This used to be the default firmware loading facility, and udev used
120 to listen for uvents to load firmware for the kernel. The firmware
128 Since this was the default firmware loading facility at one point,
134 load firmware in case it is not found. One main reason for this may
135 be if you have drivers which require firmware built-in and for
136 whatever reason cannot place the required firmware in initramfs.
145 this may be that your firmware resides outside of the paths the kernel
152 to use it to look for and fetch the required firmware. Such type of
155 for provisioning. Since udev's firmware loading facility has been
157 want to load firmware based on uevents issued.
164 certain you need to support some really custom firmware loading
168 bool "Force the firmware sysfs fallback mechanism when possible"
172 to be used for all firmware requests which explicitly do not disable a
173 a fallback mechanism. Firmware calls which do prohibit a fallback
183 bool "Enable compressed firmware support"
185 This option enables the support for loading compressed firmware
186 files. The caller of firmware API receives the decompressed file
190 Compressed firmware support does not apply to firmware images
195 bool "Enable XZ-compressed firmware support"
205 bool "Enable ZSTD-compressed firmware support"
213 bool "Enable firmware caching during suspend"
217 Because firmware caching generates uevent messages that are sent
225 bool "Enable users to initiate firmware updates using sysfs"
230 sysfs interface that allows firmware updates to be initiated from
231 userspace. For example, FPGA based PCIe cards load firmware and FPGA
234 to support cards that rely on user-initiated updates for firmware files.