1 menu "Generic Driver Options"
3 config UEVENT_HELPER_PATH
4 string "path to uevent helper"
6 default "/sbin/hotplug"
8 Path to uevent helper program forked by the kernel for
12 bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL
15 Select this option if you don't have magic firmware for drivers that
20 config PREVENT_FIRMWARE_BUILD
21 bool "Prevent firmware from being built"
24 Say yes to avoid building firmware. Firmware is usually shipped
25 with the driver, and only when updating the firmware a rebuild
30 tristate "Userspace firmware loading support" if EMBEDDED
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
38 config FIRMWARE_IN_KERNEL
39 bool "Include in-kernel firmware blobs in kernel binary"
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.
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.
56 This single option controls the inclusion of firmware for
57 every driver which usees request_firmare() and ships its
58 firmware in the kernel source tree, to avoid a proliferation
59 of 'Include firmware for xxx device' options.
61 Say 'N' and let firmware be loaded from userspace.
64 string "External firmware blobs to build into the kernel binary"
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
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.
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.
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.
90 config EXTRA_FIRMWARE_DIR
91 string "Firmware blobs root directory"
92 depends on EXTRA_FIRMWARE != ""
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.
103 bool "Driver Core verbose debug messages"
104 depends on DEBUG_KERNEL
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
111 If you are unsure about this, say N here.
114 bool "Managed device resources verbose debug messages"
115 depends on DEBUG_KERNEL
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.
123 If you are unsure about this, Say N here.
125 config SYS_HYPERVISOR