Linux-2.6.12-rc2v2.6.12-rc2

Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!

1 files changed, 42 insertions, 0 deletions

diff --git a/drivers/pnp/pnpbios/Kconfig b/drivers/pnp/pnpbios/Kconfig
new file mode 100644
index 000000000000..fab848cae89d
--- /dev/null
+++ b/drivers/pnp/pnpbios/Kconfig
@@ -0,0 +1,42 @@
+#
+# Plug and Play BIOS configuration
+#
+config PNPBIOS
+        bool "Plug and Play BIOS support (EXPERIMENTAL)"
+        depends on PNP && ISA && X86 && EXPERIMENTAL
+        default n
+        ---help---
+          Linux uses the PNPBIOS 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,
+          ISAPNP 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 PNPBIOS can help prevent resource
+          conflicts between mainboard devices and other bus devices.
+
+          Note: ACPI is expected to supersede PNPBIOS some day, currently it
+          co-exists nicely.  If you have a non-ISA system that supports ACPI,
+          you probably don't need PNPBIOS support.
+
+config PNPBIOS_PROC_FS
+        bool "Plug and Play BIOS /proc interface"
+        depends on PNPBIOS && PROC_FS
+        ---help---
+          If you say Y here and to "/proc file system support", you will be
+          able to directly access the PNPBIOS.  This includes resource
+          allocation, ESCD, and other PNPBIOS services.  Using this
+          interface is potentially dangerous because the PNPBIOS 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 PNPBIOS /proc interface (e.g. "boot" configs).
+
+          See the latest pcmcia-cs (stand-alone package) for a nice set of
+          PNPBIOS /proc interface tools (lspnp and setpnp).
+
+          Unless you are debugging or have other specific reasons, it is
+          recommended that you say N here.
+