1menu "Generic Driver Options" 2 3config UEVENT_HELPER_PATH 4 string "path to uevent helper" 5 depends on HOTPLUG 6 default "/sbin/hotplug" 7 help 8 Path to uevent helper program forked by the kernel for 9 every uevent. 10 11config STANDALONE 12 bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL 13 default y 14 help 15 Select this option if you don't have magic firmware for drivers that 16 need it. 17 18 If unsure, say Y. 19 20config PREVENT_FIRMWARE_BUILD 21 bool "Prevent firmware from being built" 22 default y 23 help 24 Say yes to avoid building firmware. Firmware is usually shipped 25 with the driver, and only when updating the firmware a rebuild 26 should be made. 27 If unsure say Y here. 28 29config FW_LOADER 30 tristate "Userspace firmware loading support" if EMBEDDED 31 depends on HOTPLUG 32 default y 33 ---help--- 34 This option is provided for the case where no in-kernel-tree modules 35 require userspace firmware loading support, but a module built outside 36 the kernel tree does. 37 38config FIRMWARE_IN_KERNEL 39 bool "Include in-kernel firmware blobs in kernel binary" 40 depends on FW_LOADER 41 default y 42 help 43 The kernel source tree includes a number of firmware 'blobs' 44 which are used by various drivers. The recommended way to 45 use these is to run "make firmware_install" and to copy the 46 resulting binary files created in usr/lib/firmware directory 47 of the kernel tree to the /lib/firmware on your system so 48 that they can be loaded by userspace helpers on request. 49 50 Enabling this option will build each required firmware blob 51 into the kernel directly, where request_firmware() will find 52 them without having to call out to userspace. This may be 53 useful if your root file system requires a device which uses 54 such firmware, and do not wish to use an initrd. 55 56 This single option controls the inclusion of firmware for 57 every driver which uses request_firmare() and ships its 58 firmware in the kernel source tree, to avoid a proliferation 59 of 'Include firmware for xxx device' options. 60 61 Say 'N' and let firmware be loaded from userspace. 62 63config EXTRA_FIRMWARE 64 string "External firmware blobs to build into the kernel binary" 65 depends on FW_LOADER 66 help 67 This option allows firmware to be built into the kernel, for the 68 cases where the user either cannot or doesn't want to provide it from 69 userspace at runtime (for example, when the firmware in question is 70 required for accessing the boot device, and the user doesn't want to 71 use an initrd). 72 73 This option is a string, and takes the (space-separated) names of the 74 firmware files -- the same names which appear in MODULE_FIRMWARE() 75 and request_firmware() in the source. These files should exist under 76 the directory specified by the EXTRA_FIRMWARE_DIR option, which is 77 by default the firmware/ subdirectory of the kernel source tree. 78 79 So, for example, you might set CONFIG_EXTRA_FIRMWARE="usb8388.bin", 80 copy the usb8388.bin file into the firmware/ directory, and build the 81 kernel. Then any request_firmware("usb8388.bin") will be 82 satisfied internally without needing to call out to userspace. 83 84 WARNING: If you include additional firmware files into your binary 85 kernel image which are not available under the terms of the GPL, 86 then it may be a violation of the GPL to distribute the resulting 87 image -- since it combines both GPL and non-GPL work. You should 88 consult a lawyer of your own before distributing such an image. 89 90config EXTRA_FIRMWARE_DIR 91 string "Firmware blobs root directory" 92 depends on EXTRA_FIRMWARE != "" 93 default "firmware" 94 help 95 This option controls the directory in which the kernel build system 96 looks for the firmware files listed in the EXTRA_FIRMWARE option. 97 The default is the firmware/ directory in the kernel source tree, 98 but by changing this option you can point it elsewhere, such as 99 the /lib/firmware/ directory or another separate directory 100 containing firmware files. 101 102config DEBUG_DRIVER 103 bool "Driver Core verbose debug messages" 104 depends on DEBUG_KERNEL 105 help 106 Say Y here if you want the Driver core to produce a bunch of 107 debug messages to the system log. Select this if you are having a 108 problem with the driver core and want to see more of what is 109 going on. 110 111 If you are unsure about this, say N here. 112 113config DEBUG_DEVRES 114 bool "Managed device resources verbose debug messages" 115 depends on DEBUG_KERNEL 116 help 117 This option enables kernel parameter devres.log. If set to 118 non-zero, devres debug messages are printed. Select this if 119 you are having a problem with devres or want to debug 120 resource management for a managed device. devres.log can be 121 switched on and off from sysfs node. 122 123 If you are unsure about this, Say N here. 124 125config SYS_HYPERVISOR 126 bool 127 default n 128 129endmenu 130