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 "Maintain a devtmpfs filesystem to mount at /dev"
13 depends on HOTPLUG && SHMEM && TMPFS
15 This creates a tmpfs filesystem instance early at bootup.
16 In this filesystem, the kernel driver core maintains device
17 nodes with their default names and permissions for all
18 registered devices with an assigned major/minor number.
19 Userspace can modify the filesystem content as needed, add
20 symlinks, and apply needed permissions.
21 It provides a fully functional /dev directory, where usually
22 udev runs on top, managing permissions and adding meaningful
24 In very limited environments, it may provide a sufficient
25 functional /dev without any further help. It also allows simple
26 rescue systems, and reliably handles dynamic major/minor numbers.
29 bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
32 This will instruct the kernel to automatically mount the
33 devtmpfs filesystem at /dev, directly after the kernel has
34 mounted the root filesystem. The behavior can be overridden
35 with the commandline parameter: devtmpfs.mount=0|1.
36 This option does not affect initramfs based booting, here
37 the devtmpfs filesystem always needs to be mounted manually
38 after the roots is mounted.
39 With this option enabled, it allows to bring up a system in
40 rescue mode with init=/bin/sh, even when the /dev directory
41 on the rootfs is completely empty.
44 bool "Select only drivers that don't need compile-time external firmware" if EXPERIMENTAL
47 Select this option if you don't have magic firmware for drivers that
52 config PREVENT_FIRMWARE_BUILD
53 bool "Prevent firmware from being built"
56 Say yes to avoid building firmware. Firmware is usually shipped
57 with the driver, and only when updating the firmware a rebuild
62 tristate "Userspace firmware loading support" if EMBEDDED
66 This option is provided for the case where no in-kernel-tree modules
67 require userspace firmware loading support, but a module built outside
70 config FIRMWARE_IN_KERNEL
71 bool "Include in-kernel firmware blobs in kernel binary"
75 The kernel source tree includes a number of firmware 'blobs'
76 which are used by various drivers. The recommended way to
77 use these is to run "make firmware_install" and to copy the
78 resulting binary files created in usr/lib/firmware directory
79 of the kernel tree to the /lib/firmware on your system so
80 that they can be loaded by userspace helpers on request.
82 Enabling this option will build each required firmware blob
83 into the kernel directly, where request_firmware() will find
84 them without having to call out to userspace. This may be
85 useful if your root file system requires a device which uses
86 such firmware, and do not wish to use an initrd.
88 This single option controls the inclusion of firmware for
89 every driver which uses request_firmware() and ships its
90 firmware in the kernel source tree, to avoid a proliferation
91 of 'Include firmware for xxx device' options.
93 Say 'N' and let firmware be loaded from userspace.
96 string "External firmware blobs to build into the kernel binary"
99 This option allows firmware to be built into the kernel, for the
100 cases where the user either cannot or doesn't want to provide it from
101 userspace at runtime (for example, when the firmware in question is
102 required for accessing the boot device, and the user doesn't want to
105 This option is a string, and takes the (space-separated) names of the
106 firmware files -- the same names which appear in MODULE_FIRMWARE()
107 and request_firmware() in the source. These files should exist under
108 the directory specified by the EXTRA_FIRMWARE_DIR option, which is
109 by default the firmware/ subdirectory of the kernel source tree.
111 So, for example, you might set CONFIG_EXTRA_FIRMWARE="usb8388.bin",
112 copy the usb8388.bin file into the firmware/ directory, and build the
113 kernel. Then any request_firmware("usb8388.bin") will be
114 satisfied internally without needing to call out to userspace.
116 WARNING: If you include additional firmware files into your binary
117 kernel image which are not available under the terms of the GPL,
118 then it may be a violation of the GPL to distribute the resulting
119 image -- since it combines both GPL and non-GPL work. You should
120 consult a lawyer of your own before distributing such an image.
122 config EXTRA_FIRMWARE_DIR
123 string "Firmware blobs root directory"
124 depends on EXTRA_FIRMWARE != ""
127 This option controls the directory in which the kernel build system
128 looks for the firmware files listed in the EXTRA_FIRMWARE option.
129 The default is the firmware/ directory in the kernel source tree,
130 but by changing this option you can point it elsewhere, such as
131 the /lib/firmware/ directory or another separate directory
132 containing firmware files.
135 bool "Driver Core verbose debug messages"
136 depends on DEBUG_KERNEL
138 Say Y here if you want the Driver core to produce a bunch of
139 debug messages to the system log. Select this if you are having a
140 problem with the driver core and want to see more of what is
143 If you are unsure about this, say N here.
146 bool "Managed device resources verbose debug messages"
147 depends on DEBUG_KERNEL
149 This option enables kernel parameter devres.log. If set to
150 non-zero, devres debug messages are printed. Select this if
151 you are having a problem with devres or want to debug
152 resource management for a managed device. devres.log can be
153 switched on and off from sysfs node.
155 If you are unsure about this, Say N here.
157 config SYS_HYPERVISOR