Lines Matching +full:built +full:- +full:in

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:
21 	  You typically want this built-in (=y) but you can also enable this
22 	  as a module, in which case the firmware_class module will be built.
23 	  You also want to be sure to enable this built-in if you are going to
24 	  enable built-in firmware (CONFIG_EXTRA_FIRMWARE).
34 	  kernel firmware files. Built-in firmware searches are preceded
39 	  in boot and cannot rely on the firmware being placed in an initrd or
42 	  This option is a string and takes the (space-separated) names of the
43 	  firmware files -- the same names that appear in MODULE_FIRMWARE()
44 	  and request_firmware() in the source. These files should exist under
56 	  image since it combines both GPL and non-GPL work. You should
64 	  This option controls the directory in which the kernel build system
65 	  looks for the firmware files listed in the EXTRA_FIRMWARE option.
74 	  path specified in the firmware_class path module parameter, or the
76 	  built-in. For details on how to work with the sysfs fallback mechanism
77 	  refer to Documentation/driver-api/firmware/fallback-mechanisms.rst.
92 	  loading facility functionality in udev has been removed, as such it
94 	  relies on or uses a fallback mechanism in userspace. If you need to
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.
119 	  if firmware_class is built-in.
136 	  facility in userspace.