5c493f5c90
Use menuconfigs instead of menus, so the whole menu can be disabled at once instead of going through all options. Signed-off-by: Jan Engelhardt <jengelh@gmx.de> Cc: Adam Belay <ambx1@neo.rr.com> Cc: Bjorn Helgaas <bjorn.helgaas@hp.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
39 lines
1.1 KiB
Text
39 lines
1.1 KiB
Text
#
|
|
# Plug and Play configuration
|
|
#
|
|
|
|
menuconfig PNP
|
|
bool "Plug and Play support"
|
|
depends on HAS_IOMEM
|
|
depends on ISA || ACPI
|
|
---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.
|
|
|
|
if PNP
|
|
|
|
config PNP_DEBUG
|
|
bool "PnP Debug Messages"
|
|
help
|
|
Say Y if you want the Plug and Play Layer to print debug messages.
|
|
This is useful if you are developing a PnP driver or troubleshooting.
|
|
|
|
comment "Protocols"
|
|
|
|
source "drivers/pnp/isapnp/Kconfig"
|
|
|
|
source "drivers/pnp/pnpbios/Kconfig"
|
|
|
|
source "drivers/pnp/pnpacpi/Kconfig"
|
|
|
|
endif # PNP
|