^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) # SPDX-License-Identifier: GPL-2.0-only
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) # Plug and Play BIOS configuration
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) #
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) config PNPBIOS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) bool "Plug and Play BIOS support"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) depends on ISA && X86_32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8) default n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) Linux uses the PNPBIOS as defined in "Plug and Play BIOS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) Specification Version 1.0A May 5, 1994" to autodetect built-in
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) mainboard resources (e.g. parallel port resources).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) Some features (e.g. event notification, docking station information,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) ISAPNP services) are not currently implemented.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) If you would like the kernel to detect and allocate resources to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) your mainboard devices (on some systems they are disabled by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) BIOS) say Y here. Also the PNPBIOS can help prevent resource
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) conflicts between mainboard devices and other bus devices.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) Note: ACPI is expected to supersede PNPBIOS some day, currently it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) co-exists nicely. If you have a non-ISA system that supports ACPI,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) you probably don't need PNPBIOS support.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) config PNPBIOS_PROC_FS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) bool "Plug and Play BIOS /proc interface"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) depends on PNPBIOS && PROC_FS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) If you say Y here and to "/proc file system support", you will be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) able to directly access the PNPBIOS. This includes resource
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32) allocation, ESCD, and other PNPBIOS services. Using this
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) interface is potentially dangerous because the PNPBIOS driver will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) not be notified of any resource changes made by writing directly.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) Also some buggy systems will fault when accessing certain features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) in the PNPBIOS /proc interface (e.g. "boot" configs).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) See the latest pcmcia-cs (stand-alone package) for a nice set of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) PNPBIOS /proc interface tools (lspnp and setpnp).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) Unless you are debugging or have other specific reasons, it is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) recommended that you say N here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43)