162306a36Sopenharmony_ci# SPDX-License-Identifier: GPL-2.0-only
262306a36Sopenharmony_ci#
362306a36Sopenharmony_ci# Plug and Play BIOS configuration
462306a36Sopenharmony_ci#
562306a36Sopenharmony_ciconfig PNPBIOS
662306a36Sopenharmony_ci	bool "Plug and Play BIOS support"
762306a36Sopenharmony_ci	depends on ISA && X86_32
862306a36Sopenharmony_ci	default n
962306a36Sopenharmony_ci	help
1062306a36Sopenharmony_ci	  Linux uses the PNPBIOS as defined in "Plug and Play BIOS
1162306a36Sopenharmony_ci	  Specification Version 1.0A May 5, 1994" to autodetect built-in
1262306a36Sopenharmony_ci	  mainboard resources (e.g. parallel port resources).
1362306a36Sopenharmony_ci
1462306a36Sopenharmony_ci	  Some features (e.g. event notification, docking station information,
1562306a36Sopenharmony_ci	  ISAPNP services) are not currently implemented.
1662306a36Sopenharmony_ci
1762306a36Sopenharmony_ci	  If you would like the kernel to detect and allocate resources to
1862306a36Sopenharmony_ci	  your mainboard devices (on some systems they are disabled by the
1962306a36Sopenharmony_ci	  BIOS) say Y here.  Also the PNPBIOS can help prevent resource
2062306a36Sopenharmony_ci	  conflicts between mainboard devices and other bus devices.
2162306a36Sopenharmony_ci
2262306a36Sopenharmony_ci	  Note: ACPI is expected to supersede PNPBIOS some day, currently it
2362306a36Sopenharmony_ci	  co-exists nicely.  If you have a non-ISA system that supports ACPI,
2462306a36Sopenharmony_ci	  you probably don't need PNPBIOS support.
2562306a36Sopenharmony_ci
2662306a36Sopenharmony_ciconfig PNPBIOS_PROC_FS
2762306a36Sopenharmony_ci	bool "Plug and Play BIOS /proc interface"
2862306a36Sopenharmony_ci	depends on PNPBIOS && PROC_FS
2962306a36Sopenharmony_ci	help
3062306a36Sopenharmony_ci	  If you say Y here and to "/proc file system support", you will be
3162306a36Sopenharmony_ci	  able to directly access the PNPBIOS.  This includes resource
3262306a36Sopenharmony_ci	  allocation, ESCD, and other PNPBIOS services.  Using this
3362306a36Sopenharmony_ci	  interface is potentially dangerous because the PNPBIOS driver will
3462306a36Sopenharmony_ci	  not be notified of any resource changes made by writing directly.
3562306a36Sopenharmony_ci	  Also some buggy systems will fault when accessing certain features
3662306a36Sopenharmony_ci	  in the PNPBIOS /proc interface (e.g. "boot" configs).
3762306a36Sopenharmony_ci
3862306a36Sopenharmony_ci	  See the latest pcmcia-cs (stand-alone package) for a nice set of
3962306a36Sopenharmony_ci	  PNPBIOS /proc interface tools (lspnp and setpnp).
4062306a36Sopenharmony_ci
4162306a36Sopenharmony_ci	  Unless you are debugging or have other specific reasons, it is
4262306a36Sopenharmony_ci	  recommended that you say N here.
4362306a36Sopenharmony_ci
44