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 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. 27 Userspace can modify the filesystem content as needed, add 28 symlinks, and apply needed permissions. 29 It provides a fully functional /dev directory, where usually 30 udev runs on top, managing permissions and adding meaningful 31 symlinks. 32 In very limited environments, it may provide a sufficient 33 functional /dev without any further help. It also allows simple 34 rescue systems, and reliably handles dynamic major/minor numbers. 35 36 Notice: if CONFIG_TMPFS isn't enabled, the simpler ramfs 37 file system will be used instead. 38 39config DEVTMPFS_MOUNT 40 bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs" 41 depends on DEVTMPFS 42 help 43 This will instruct the kernel to automatically mount the 44 devtmpfs filesystem at /dev, directly after the kernel has 45 mounted the root filesystem. The behavior can be overridden 46 with the commandline parameter: devtmpfs.mount=0|1. 47 This option does not affect initramfs based booting, here 48 the devtmpfs filesystem always needs to be mounted manually 49 after the roots is mounted. 50 With this option enabled, it allows to bring up a system in 51 rescue mode with init=/bin/sh, even when the /dev directory 52 on the rootfs is completely empty. 53 54config STANDALONE 55 bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL 56 default y 57 help 58 Select this option if you don't have magic firmware for drivers that 59 need it. 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 68 with the driver, and only when updating the firmware a rebuild 69 should be made. 70 If unsure say Y here. 71 72config FW_LOADER 73 tristate "Userspace firmware loading support" if EMBEDDED 74 depends on HOTPLUG 75 default y 76 ---help--- 77 This option is provided for the case where no in-kernel-tree modules 78 require userspace firmware loading support, but a module built outside 79 the kernel tree does. 80 81config FIRMWARE_IN_KERNEL 82 bool "Include in-kernel firmware blobs in kernel binary" 83 depends on FW_LOADER 84 default y 85 help 86 The kernel source tree includes a number of firmware 'blobs' 87 which are used by various drivers. The recommended way to 88 use these is to run "make firmware_install" and to copy the 89 resulting binary files created in usr/lib/firmware directory 90 of the kernel tree to the /lib/firmware on your system so 91 that they can be loaded by userspace helpers on request. 92 93 Enabling this option will build each required firmware blob 94 into the kernel directly, where request_firmware() will find 95 them without having to call out to userspace. This may be 96 useful if your root file system requires a device which uses 97 such firmware, and do not wish to use an initrd. 98 99 This single option controls the inclusion of firmware for 100 every driver which uses request_firmware() and ships its 101 firmware in the kernel source tree, to avoid a proliferation 102 of 'Include firmware for xxx device' options. 103 104 Say 'N' and let firmware be loaded from userspace. 105 106config EXTRA_FIRMWARE 107 string "External firmware blobs to build into the kernel binary" 108 depends on FW_LOADER 109 help 110 This option allows firmware to be built into the kernel, for the 111 cases where the user either cannot or doesn't want to provide it from 112 userspace at runtime (for example, when the firmware in question is 113 required for accessing the boot device, and the user doesn't want to 114 use an initrd). 115 116 This option is a string, and takes the (space-separated) names of the 117 firmware files -- the same names which appear in MODULE_FIRMWARE() 118 and request_firmware() in the source. These files should exist under 119 the directory specified by the EXTRA_FIRMWARE_DIR option, which is 120 by default the firmware/ subdirectory of the kernel source tree. 121 122 So, for example, you might set CONFIG_EXTRA_FIRMWARE="usb8388.bin", 123 copy the usb8388.bin file into the firmware/ directory, and build the 124 kernel. Then any request_firmware("usb8388.bin") will be 125 satisfied internally without needing to call out to userspace. 126 127 WARNING: If you include additional firmware files into your binary 128 kernel image which are not available under the terms of the GPL, 129 then it may be a violation of the GPL to distribute the resulting 130 image -- since it combines both GPL and non-GPL work. You should 131 consult a lawyer of your own before distributing such an image. 132 133config EXTRA_FIRMWARE_DIR 134 string "Firmware blobs root directory" 135 depends on EXTRA_FIRMWARE != "" 136 default "firmware" 137 help 138 This option controls the directory in which the kernel build system 139 looks for the firmware files listed in the EXTRA_FIRMWARE option. 140 The default is the firmware/ directory in the kernel source tree, 141 but by changing this option you can point it elsewhere, such as 142 the /lib/firmware/ directory or another separate directory 143 containing firmware files. 144 145config DEBUG_DRIVER 146 bool "Driver Core verbose debug messages" 147 depends on DEBUG_KERNEL 148 help 149 Say Y here if you want the Driver core to produce a bunch of 150 debug messages to the system log. Select this if you are having a 151 problem with the driver core and want to see more of what is 152 going on. 153 154 If you are unsure about this, say N here. 155 156config DEBUG_DEVRES 157 bool "Managed device resources verbose debug messages" 158 depends on DEBUG_KERNEL 159 help 160 This option enables kernel parameter devres.log. If set to 161 non-zero, devres debug messages are printed. Select this if 162 you are having a problem with devres or want to debug 163 resource management for a managed device. devres.log can be 164 switched on and off from sysfs node. 165 166 If you are unsure about this, Say N here. 167 168config SYS_HYPERVISOR 169 bool 170 default n 171 172endmenu 173