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