| Kconfig (573c9774396091dc9d55e7de91026608fa2db3ee) | Kconfig (b83a313bf2520183641cf485d68cc273323597d2) |
|---|---|
| 1menu "Generic Driver Options" 2 3config UEVENT_HELPER_PATH 4 string "path to uevent helper" 5 depends on HOTPLUG 6 default "" 7 help 8 Path to uevent helper program forked by the kernel for 9 every uevent. 10 Before the switch to the netlink-based uevent source, this was 11 used to hook hotplug scripts into kernel device events. It 12 usually pointed to a shell script at /sbin/hotplug. 13 This should not be used today, because usual systems create 14 many events at bootup or device discovery in a very short time 15 frame. One forked process per event can create so many processes 16 that it creates a high system load, or on smaller systems 17 it is known to create out-of-memory situations during bootup. 18 | 1menu "Generic Driver Options" 2 3config UEVENT_HELPER_PATH 4 string "path to uevent helper" 5 depends on HOTPLUG 6 default "" 7 help 8 Path to uevent helper program forked by the kernel for 9 every uevent. 10 Before the switch to the netlink-based uevent source, this was 11 used to hook hotplug scripts into kernel device events. It 12 usually pointed to a shell script at /sbin/hotplug. 13 This should not be used today, because usual systems create 14 many events at bootup or device discovery in a very short time 15 frame. One forked process per event can create so many processes 16 that it creates a high system load, or on smaller systems 17 it is known to create out-of-memory situations during bootup. 18 |
| 19 To disable user space helper program execution at early boot 20 time specify an empty string here. This setting can be altered 21 via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper 22 later at runtime. 23 | |
| 24config DEVTMPFS 25 bool "Maintain a devtmpfs filesystem to mount at /dev" 26 depends on HOTPLUG 27 help 28 This creates a tmpfs/ramfs filesystem instance early at bootup. 29 In this filesystem, the kernel driver core maintains device 30 nodes with their default names and permissions for all 31 registered devices with an assigned major/minor number. --- 33 unchanged lines hidden (view full) --- 65 66 If unsure, say Y. 67 68config PREVENT_FIRMWARE_BUILD 69 bool "Prevent firmware from being built" 70 default y 71 help 72 Say yes to avoid building firmware. Firmware is usually shipped | 19config DEVTMPFS 20 bool "Maintain a devtmpfs filesystem to mount at /dev" 21 depends on HOTPLUG 22 help 23 This creates a tmpfs/ramfs filesystem instance early at bootup. 24 In this filesystem, the kernel driver core maintains device 25 nodes with their default names and permissions for all 26 registered devices with an assigned major/minor number. --- 33 unchanged lines hidden (view full) --- 60 61 If unsure, say Y. 62 63config PREVENT_FIRMWARE_BUILD 64 bool "Prevent firmware from being built" 65 default y 66 help 67 Say yes to avoid building firmware. Firmware is usually shipped |
| 73 with the driver and only when updating the firmware should a 74 rebuild be made. 75 If unsure, say Y here. | 68 with the driver, and only when updating the firmware a rebuild 69 should be made. 70 If unsure say Y here. |
| 76 77config FW_LOADER 78 tristate "Userspace firmware loading support" if EXPERT 79 default y 80 ---help--- | 71 72config FW_LOADER 73 tristate "Userspace firmware loading support" if EXPERT 74 default y 75 ---help--- |
| 81 This option is provided for the case where none of the in-tree modules 82 require userspace firmware loading support, but a module built 83 out-of-tree does. | 76 This option is provided for the case where no in-kernel-tree modules 77 require userspace firmware loading support, but a module built outside 78 the kernel tree does. |
| 84 85config FIRMWARE_IN_KERNEL 86 bool "Include in-kernel firmware blobs in kernel binary" 87 depends on FW_LOADER 88 default y 89 help 90 The kernel source tree includes a number of firmware 'blobs' | 79 80config FIRMWARE_IN_KERNEL 81 bool "Include in-kernel firmware blobs in kernel binary" 82 depends on FW_LOADER 83 default y 84 help 85 The kernel source tree includes a number of firmware 'blobs' |
| 91 that are used by various drivers. The recommended way to 92 use these is to run "make firmware_install", which, after 93 converting ihex files to binary, copies all of the needed 94 binary files in firmware/ to /lib/firmware/ on your system so | 86 which are used by various drivers. The recommended way to 87 use these is to run "make firmware_install" and to copy the 88 resulting binary files created in usr/lib/firmware directory 89 of the kernel tree to the /lib/firmware on your system so |
| 95 that they can be loaded by userspace helpers on request. 96 97 Enabling this option will build each required firmware blob 98 into the kernel directly, where request_firmware() will find 99 them without having to call out to userspace. This may be | 90 that they can be loaded by userspace helpers on request. 91 92 Enabling this option will build each required firmware blob 93 into the kernel directly, where request_firmware() will find 94 them without having to call out to userspace. This may be |
| 100 useful if your root file system requires a device that uses 101 such firmware and do not wish to use an initrd. | 95 useful if your root file system requires a device which uses 96 such firmware, and do not wish to use an initrd. |
| 102 103 This single option controls the inclusion of firmware for | 97 98 This single option controls the inclusion of firmware for |
| 104 every driver that uses request_firmware() and ships its 105 firmware in the kernel source tree, which avoids a 106 proliferation of 'Include firmware for xxx device' options. | 99 every driver which uses request_firmware() and ships its 100 firmware in the kernel source tree, to avoid a proliferation 101 of 'Include firmware for xxx device' options. |
| 107 108 Say 'N' and let firmware be loaded from userspace. 109 110config EXTRA_FIRMWARE 111 string "External firmware blobs to build into the kernel binary" 112 depends on FW_LOADER 113 help | 102 103 Say 'N' and let firmware be loaded from userspace. 104 105config EXTRA_FIRMWARE 106 string "External firmware blobs to build into the kernel binary" 107 depends on FW_LOADER 108 help |
| 114 This option allows firmware to be built into the kernel for the case 115 where the user either cannot or doesn't want to provide it from | 109 This option allows firmware to be built into the kernel, for the 110 cases where the user either cannot or doesn't want to provide it from |
| 116 userspace at runtime (for example, when the firmware in question is 117 required for accessing the boot device, and the user doesn't want to 118 use an initrd). 119 | 111 userspace at runtime (for example, when the firmware in question is 112 required for accessing the boot device, and the user doesn't want to 113 use an initrd). 114 |
| 120 This option is a string and takes the (space-separated) names of the 121 firmware files -- the same names that appear in MODULE_FIRMWARE() | 115 This option is a string, and takes the (space-separated) names of the 116 firmware files -- the same names which appear in MODULE_FIRMWARE() |
| 122 and request_firmware() in the source. These files should exist under 123 the directory specified by the EXTRA_FIRMWARE_DIR option, which is | 117 and request_firmware() in the source. These files should exist under 118 the directory specified by the EXTRA_FIRMWARE_DIR option, which is |
| 124 by default the firmware subdirectory of the kernel source tree. | 119 by default the firmware/ subdirectory of the kernel source tree. |
| 125 | 120 |
| 126 For example, you might set CONFIG_EXTRA_FIRMWARE="usb8388.bin", copy 127 the usb8388.bin file into the firmware directory, and build the kernel. 128 Then any request_firmware("usb8388.bin") will be satisfied internally 129 without needing to call out to userspace. | 121 So, for example, you might set CONFIG_EXTRA_FIRMWARE="usb8388.bin", 122 copy the usb8388.bin file into the firmware/ directory, and build the 123 kernel. Then any request_firmware("usb8388.bin") will be 124 satisfied internally without needing to call out to userspace. |
| 130 131 WARNING: If you include additional firmware files into your binary | 125 126 WARNING: If you include additional firmware files into your binary |
| 132 kernel image that are not available under the terms of the GPL, | 127 kernel image which are not available under the terms of the GPL, |
| 133 then it may be a violation of the GPL to distribute the resulting | 128 then it may be a violation of the GPL to distribute the resulting |
| 134 image since it combines both GPL and non-GPL work. You should | 129 image -- since it combines both GPL and non-GPL work. You should |
| 135 consult a lawyer of your own before distributing such an image. 136 137config EXTRA_FIRMWARE_DIR 138 string "Firmware blobs root directory" 139 depends on EXTRA_FIRMWARE != "" 140 default "firmware" 141 help 142 This option controls the directory in which the kernel build system 143 looks for the firmware files listed in the EXTRA_FIRMWARE option. | 130 consult a lawyer of your own before distributing such an image. 131 132config EXTRA_FIRMWARE_DIR 133 string "Firmware blobs root directory" 134 depends on EXTRA_FIRMWARE != "" 135 default "firmware" 136 help 137 This option controls the directory in which the kernel build system 138 looks for the firmware files listed in the EXTRA_FIRMWARE option. |
| 144 The default is firmware/ in the kernel source tree, but by changing 145 this option you can point it elsewhere, such as /lib/firmware/ or 146 some other directory containing the firmware files. | 139 The default is the firmware/ directory in the kernel source tree, 140 but by changing this option you can point it elsewhere, such as 141 the /lib/firmware/ directory or another separate directory 142 containing firmware files. |
| 147 148config DEBUG_DRIVER 149 bool "Driver Core verbose debug messages" 150 depends on DEBUG_KERNEL 151 help 152 Say Y here if you want the Driver core to produce a bunch of 153 debug messages to the system log. Select this if you are having a 154 problem with the driver core and want to see more of what is --- 12 unchanged lines hidden (view full) --- 167 switched on and off from sysfs node. 168 169 If you are unsure about this, Say N here. 170 171config SYS_HYPERVISOR 172 bool 173 default n 174 | 143 144config DEBUG_DRIVER 145 bool "Driver Core verbose debug messages" 146 depends on DEBUG_KERNEL 147 help 148 Say Y here if you want the Driver core to produce a bunch of 149 debug messages to the system log. Select this if you are having a 150 problem with the driver core and want to see more of what is --- 12 unchanged lines hidden (view full) --- 163 switched on and off from sysfs node. 164 165 If you are unsure about this, Say N here. 166 167config SYS_HYPERVISOR 168 bool 169 default n 170 |
| 171source "drivers/base/regmap/Kconfig" 172 |
|
| 175endmenu | 173endmenu |