| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # | 
|  | 2 | # Plug and Play configuration | 
|  | 3 | # | 
|  | 4 |  | 
|  | 5 | menu "Plug and Play support" | 
|  | 6 |  | 
|  | 7 | config PNP | 
|  | 8 | bool "Plug and Play support" | 
|  | 9 | depends on ISA || ACPI_BUS | 
|  | 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 | 
|  | 25 | bool "PnP Debug Messages" | 
|  | 26 | depends on PNP | 
|  | 27 | help | 
|  | 28 | Say Y if you want the Plug and Play Layer to print debug messages. | 
|  | 29 | This is useful if you are developing a PnP driver or troubleshooting. | 
|  | 30 |  | 
|  | 31 | comment "Protocols" | 
|  | 32 | depends on PNP | 
|  | 33 |  | 
|  | 34 | source "drivers/pnp/isapnp/Kconfig" | 
|  | 35 |  | 
|  | 36 | source "drivers/pnp/pnpbios/Kconfig" | 
|  | 37 |  | 
|  | 38 | source "drivers/pnp/pnpacpi/Kconfig" | 
|  | 39 |  | 
|  | 40 | endmenu | 
|  | 41 |  |