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