Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Plug and Play configuration | |
3 | # | |
4 | ||
5 | menu "Plug and Play support" | |
e25df120 | 6 | depends on HAS_IOMEM |
1da177e4 LT |
7 | |
8 | config PNP | |
9 | bool "Plug and Play support" | |
76f58584 | 10 | depends on ISA || ACPI |
1da177e4 LT |
11 | ---help--- |
12 | Plug and Play (PnP) is a standard for peripherals which allows those | |
13 | peripherals to be configured by software, e.g. assign IRQ's or other | |
14 | parameters. No jumpers on the cards are needed, instead the values | |
15 | are provided to the cards from the BIOS, from the operating system, | |
16 | or using a user-space utility. | |
17 | ||
18 | Say Y here if you would like Linux to configure your Plug and Play | |
19 | devices. You should then also say Y to all of the protocols below. | |
20 | Alternatively, you can say N here and configure your PnP devices | |
21 | using user space utilities such as the isapnptools package. | |
22 | ||
23 | If unsure, say Y. | |
24 | ||
25 | config PNP_DEBUG | |
26 | bool "PnP Debug Messages" | |
27 | depends on PNP | |
28 | help | |
29 | Say Y if you want the Plug and Play Layer to print debug messages. | |
30 | This is useful if you are developing a PnP driver or troubleshooting. | |
31 | ||
32 | comment "Protocols" | |
33 | depends on PNP | |
34 | ||
35 | source "drivers/pnp/isapnp/Kconfig" | |
36 | ||
37 | source "drivers/pnp/pnpbios/Kconfig" | |
38 | ||
39 | source "drivers/pnp/pnpacpi/Kconfig" | |
40 | ||
41 | endmenu | |
42 |