| | 1 | # SPDX-License-Identifier: GPL-2.0-only |
| | 2 | # |
| | 3 | # Plug and Play configuration |
| | 4 | # |
| | 5 | |
| | 6 | menuconfig PNP |
| | 7 | bool "Plug and Play support" |
| | 8 | depends on HAS_IOMEM |
| | 9 | depends on ISA || ACPI |
| | 10 | help |
| | 11 | Plug and Play (PnP) is a standard for peripherals which allows those |
| | 12 | peripherals to be configured by software, e.g. assign IRQ's or other |
| | 13 | parameters. No jumpers on the cards are needed, instead the values |
| | 14 | are provided to the cards from the BIOS, from the operating system, |
| | 15 | or using a user-space utility. |
| | 16 | |
| | 17 | Say Y here if you would like Linux to configure your Plug and Play |
| | 18 | devices. You should then also say Y to all of the protocols below. |
| | 19 | Alternatively, you can say N here and configure your PnP devices |
| | 20 | using user space utilities such as the isapnptools package. |
| | 21 | |
| | 22 | If unsure, say Y. |
| | 23 | |
| | 24 | config PNP_DEBUG_MESSAGES |
| | 25 | default y |
| | 26 | bool "PNP debugging messages" |
| | 27 | depends on PNP |
| | 28 | help |
| | 29 | Say Y here if you want the PNP layer to be able to produce debugging |
| | 30 | messages if needed. The messages can be enabled at boot-time with |
| | 31 | the pnp.debug kernel parameter. |
| | 32 | |
| | 33 | This option allows you to save a bit of space if you do not want |
| | 34 | the messages to even be built into the kernel. |
| | 35 | |
| | 36 | If you have any doubts about this, say Y here. |
| | 37 | |
| | 38 | if PNP |
| | 39 | |
| | 40 | comment "Protocols" |
| | 41 | |
| | 42 | source "drivers/pnp/isapnp/Kconfig" |
| | 43 | |
| | 44 | source "drivers/pnp/pnpbios/Kconfig" |
| | 45 | |
| | 46 | source "drivers/pnp/pnpacpi/Kconfig" |
| | 47 | |
| | 48 | endif # PNP |
projects / linux-2.6-block.git / blame_incremental