# SPDX-License-Identifier: GPL-2.0-only # # Plug and Play BIOS configuration # config [31mCONFIG_PNPBIOS[0m bool "Plug and Play BIOS support" depends on [31mCONFIG_ISA[0m && [31mCONFIG_X86_32[0m default n ---help--- Linux uses the [31mCONFIG_PNPBIOS[0m as defined in "Plug and Play BIOS Specification Version 1.0A May 5, 1994" to autodetect built-in mainboard resources (e.g. parallel port resources). Some features (e.g. event notification, docking station information, [31mCONFIG_ISAPNP[0m services) are not currently implemented. If you would like the kernel to detect and allocate resources to your mainboard devices (on some systems they are disabled by the BIOS) say Y here. Also the [31mCONFIG_PNPBIOS[0m can help prevent resource conflicts between mainboard devices and other bus devices. Note: [31mCONFIG_ACPI[0m is expected to supersede [31mCONFIG_PNPBIOS[0m some day, currently it co-exists nicely. If you have a non-[31mCONFIG_ISA[0m system that supports [31mCONFIG_ACPI[0m, you probably don't need [31mCONFIG_PNPBIOS[0m support. config [31mCONFIG_PNPBIOS_PROC_FS[0m bool "Plug and Play BIOS /proc interface" depends on [31mCONFIG_PNPBIOS[0m && [31mCONFIG_PROC_FS[0m ---help--- If you say Y here and to "/proc file system support", you will be able to directly access the [31mCONFIG_PNPBIOS[0m. This includes resource allocation, ESCD, and other [31mCONFIG_PNPBIOS[0m services. Using this interface is potentially dangerous because the [31mCONFIG_PNPBIOS[0m driver will not be notified of any resource changes made by writing directly. Also some buggy systems will fault when accessing certain features in the [31mCONFIG_PNPBIOS[0m /proc interface (e.g. "boot" configs). See the latest pcmcia-cs (stand-alone package) for a nice set of [31mCONFIG_PNPBIOS[0m /proc interface tools (lspnp and setpnp). Unless you are debugging or have other specific reasons, it is recommended that you say N here. |