MAJOR=13 MINOR=65 DEVNAME=input/event1 9/ˆl–Ü4ý(© ³( Å €fàD¦-ÿÍ ƒx/»a–Ým_J*j"Tâ‚ Æ_¸ÐTÅ£Ì /# SPDX-License-Identifier: GPL-2.0 menu "Generic Driver Options" config AUXILIARY_BUS bool config UEVENT_HELPER bool "Support for uevent helper" help The uevent helper program is forked by the kernel for every uevent. Before the switch to the netlink-based uevent source, this was used to hook hotplug scripts into kernel device events. It usually pointed to a shell script at /sbin/hotplug. This should not be used today, because usual systems create many events at bootup or device discovery in a very short time frame. One forked process per event can create so many processes that it creates a high system load, or on smaller systems it is known to create out-of-memory situations during bootup. config UEVENT_HELPER_PATH string "path to uevent helper" depends on UEVENT_HELPER default "" help To disable user space helper program execution at by default specify an empty string here. This setting can still be altered via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper later at runtime. config DEVTMPFS bool "Maintain a devtmpfs filesystem to mount at /dev" help This creates a tmpfs/ramfs filesystem instance early at bootup. In this filesystem, the kernel driver core maintains device nodes with their default names and permissions for all registered devices with an assigned major/minor number. Userspace can modify the filesystem content as needed, add symlinks, and apply needed permissions. It provides a fully functional /dev directory, where usually udev runs on top, managing permissions and adding meaningful symlinks. In very limited environments, it may provide a sufficient functional /dev without any further help. It also allows simple rescue systems, and reliably handles dynamic major/minor numbers. Notice: if CONFIG_TMPFS isn't enabled, the simpler ramfs file system will be used instead. config DEVTMPFS_MOUNT bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs" depends on DEVTMPFS help This will instruct the kernel to automatically mount the devtmpfs filesystem at /dev, directly after the kernel has mounted the root filesystem. The behavior can be overridden with the commandline parameter: devtmpfs.mount=0|1. This option does not affect initramfs based booting, here the devtmpfs filesystem always needs to be mounted manually after the rootfs is mounted. With this option enabled, it allows to bring up a system in rescue mode with init=/bin/sh, even when the /dev directory on the rootfs is completely empty. config DEVTMPFS_SAFE bool "Use nosuid,noexec mount options on devtmpfs" depends on DEVTMPFS help This instructs the kernel to include the MS_NOEXEC and MS_NOSUID mount flags when mounting devtmpfs. Notice: If enabled, things like /dev/mem cannot be mmapped with the PROT_EXEC flag. This can break, for example, non-KMS video drivers. config STANDALONE bool "Select only drivers that don't need compile-time external firmware" default y help Select this option if you don't have magic firmware for drivers that need it. If unsure, say Y. config PREVENT_FIRMWARE_BUILD bool "Disable drivers features which enable custom firmware building" default y help Say yes to disable driver features which enable building a custom driver firmware at kernel build time. These drivers do not use the kernel firmware API to load firmware (CONFIG_FW_LOADER), instead they use their own custom loading mechanism. The required firmware is usually shipped with the driver, building the driver firmware should only be needed if you have an updated firmware source. Firmware should not be being built as part of kernel, these days you should always prevent this and say Y here. There are only two old drivers which enable building of its firmware at kernel build time: o CONFIG_WANXL through CONFIG_WANXL_BUILD_FIRMWARE