[PATCH] new kernel configuration 6/7

This adds the driver config files. (part 2)

drivers/net/Kconfig

+#
+# Network device configuration
+#
+source "drivers/net/arcnet/Kconfig"
+
+config DUMMY
+	tristate "Dummy net driver support"
+	depends on NETDEVICES
+	---help---
+	  This is essentially a bit-bucket device (i.e. traffic you send to
+	  this device is consigned into oblivion) with a configurable IP
+	  address. It is most commonly used in order to make your currently
+	  inactive SLIP address seem like a real address for local programs.
+	  If you use SLIP or PPP, you might want to say Y here. Since this
+	  thing often comes in handy, the default is Y. It won't enlarge your
+	  kernel either. What a deal. Read about it in the Network
+	  Administrator's Guide, available from
+	  <http://www.linuxdoc.org/docs.html#guide>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called dummy.o.  If you want to use more than one dummy
+	  device at a time, you need to compile this driver as a module.
+	  Instead of 'dummy', the devices will then be called 'dummy0',
+	  'dummy1' etc.
+
+config BONDING
+	tristate "Bonding driver support"
+	depends on NETDEVICES
+	---help---
+	  Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
+	  Channels together. This is called 'Etherchannel' by Cisco,
+	  'Trunking' by Sun, and 'Bonding' in Linux.
+
+	  If you have two Ethernet connections to some other computer, you can
+	  make them behave like one double speed connection using this driver.
+	  Naturally, this has to be supported at the other end as well, either
+	  with a similar Bonding Linux driver, a Cisco 5500 switch or a
+	  SunTrunking SunSoft driver.
+
+	  This is similar to the EQL driver, but it merges Ethernet segments
+	  instead of serial lines.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called bonding.o.
+
+config EQUALIZER
+	tristate "EQL (serial line load balancing) support"
+	depends on NETDEVICES
+	---help---
+	  If you have two serial connections to some other computer (this
+	  usually requires two modems and two telephone lines) and you use
+	  SLIP (the protocol for sending Internet traffic over telephone
+	  lines) or PPP (a better SLIP) on them, you can make them behave like
+	  one double speed connection using this driver.  Naturally, this has
+	  to be supported at the other end as well, either with a similar EQL
+	  Linux driver or with a Livingston Portmaster 2e.
+
+	  Say Y if you want this and read
+	  <file:Documentation/networking/eql.txt>.  You may also want to read
+	  section 6.2 of the NET-3-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called eql.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.  If
+	  unsure, say N.
+
+config TUN
+	tristate "Universal TUN/TAP device driver support"
+	depends on NETDEVICES
+	---help---
+	  TUN/TAP provides packet reception and transmission for user space
+	  programs.  It can be viewed as a simple Point-to-Point or Ethernet
+	  device, which instead of receiving packets from a physical media,
+	  receives them from user space program and instead of sending packets
+	  via physical media writes them to the user space program.
+
+	  When a program opens /dev/net/tun, driver creates and registers
+	  corresponding net device tunX or tapX.  After a program closed above
+	  devices, driver will automatically delete tunXX or tapXX device and
+	  all routes corresponding to it.
+
+	  Please read <file:Documentation/networking/tuntap.txt> for more
+	  information.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called tun.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+	  If you don't know what to use this for, you don't need it.
+
+config ETHERTAP
+	tristate "Ethertap network tap (OBSOLETE)"
+	depends on NETDEVICES && EXPERIMENTAL
+	---help---
+	  If you say Y here (and have said Y to "Kernel/User network link
+	  driver", above) and create a character special file /dev/tap0 with
+	  major number 36 and minor number 16 using mknod ("man mknod"), you
+	  will be able to have a user space program read and write raw
+	  Ethernet frames from/to that special file.  tap0 can be configured
+	  with ifconfig and route like any other Ethernet device but it is not
+	  connected to any physical LAN; everything written by the user to
+	  /dev/tap0 is treated by the kernel as if it had come in from a LAN
+	  to the device tap0; everything the kernel wants to send out over the
+	  device tap0 can instead be read by the user from /dev/tap0: the user
+	  mode program replaces the LAN that would be attached to an ordinary
+	  Ethernet device. Please read the file
+	  <file:Documentation/networking/ethertap.txt> for more information.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ethertap.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+	  If you don't know what to use this for, you don't need it.
+
+config NET_SB1000
+	tristate "General Instruments Surfboard 1000"
+	depends on NETDEVICES && ISAPNP
+	---help---
+	  This is a driver for the General Instrument (also known as
+	  NextLevel) SURFboard 1000 internal
+	  cable modem. This is an ISA card which is used by a number of cable
+	  TV companies to provide cable modem access. It's a one-way
+	  downstream-only cable modem, meaning that your upstream net link is
+	  provided by your regular phone modem.
+
+	  At present this driver only compiles as a module, so say M here if
+	  you have this card. The module will be called sb1000.o. Then read
+	  <file:Documentation/networking/README.sb1000> for information on how
+	  to use this module, as it needs special ppp scripts for establishing
+	  a connection. Further documentation and the necessary scripts can be
+	  found at:
+
+	  <http://www.jacksonville.net/~fventuri/>
+	  <http://home.adelphia.net/~siglercm/sb1000.html>
+	  <http://linuxpower.cx/~cable/>
+
+	  If you don't have this card, of course say N.
+
+#
+#	Ethernet
+#
+
+menu "Ethernet (10 or 100Mbit)"
+	depends on NETDEVICES
+
+config NET_ETHERNET
+	bool "Ethernet (10 or 100Mbit)"
+	---help---
+	  Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
+	  type of Local Area Network (LAN) in universities and companies.
+
+	  Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
+	  coaxial cable, linking computers in a chain), 10BASE-T or twisted
+	  pair (10 Mbps over twisted pair cable, linking computers to central
+	  hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
+	  100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
+	  100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
+	  cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
+	  [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
+	  Ethernet (1 Gbps over optical fiber or short copper links).
+
+	  If your Linux machine will be connected to an Ethernet and you have
+	  an Ethernet network interface card (NIC) installed in your computer,
+	  say Y here and read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>. You will then also have
+	  to say Y to the driver for your particular NIC.
+
+	  Note that the answer to this question won't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions about Ethernet network cards. If unsure, say N.
+
+config ARM_AM79C961A
+	bool "ARM EBSA110 AM79C961A support"
+	depends on NET_ETHERNET && ARM && ARCH_EBSA110
+	help
+	  If you wish to compile a kernel for the EBSA-110, then you should
+	  always answer Y to this.
+
+source "drivers/acorn/net/Kconfig"
+
+config MACE
+	tristate "MACE (Power Mac ethernet) support"
+	depends on NET_ETHERNET && PPC && ALL_PPC
+	help
+	  Power Macintoshes and clones with Ethernet built-in on the
+	  motherboard will usually use a MACE (Medium Access Control for
+	  Ethernet) interface. Say Y to include support for the MACE chip.
+
+	  This driver is also available as a module called mace.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config MACE_AAUI_PORT
+	bool "Use AAUI port instead of TP by default"
+	depends on MACE
+	help
+	  Some Apple machines (notably the Apple Network Server) which use the
+	  MACE ethernet chip have an Apple AUI port (small 15-pin connector),
+	  instead of an 8-pin RJ45 connector for twisted-pair ethernet.  Say
+	  Y here if you have such a machine.  If unsure, say N.
+	  The driver will default to AAUI on ANS anyway, and if you use it as
+	  a module, you can provide the port_aaui=0|1 to force the driver.
+
+config BMAC
+	tristate "BMAC (G3 ethernet) support"
+	depends on NET_ETHERNET && PPC && ALL_PPC
+	help
+	  Say Y for support of BMAC Ethernet interfaces. These are used on G3
+	  computers.
+
+	  This driver is also available as a module called bmac.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config OAKNET
+	tristate "National DP83902AV (Oak ethernet) support"
+	depends on NET_ETHERNET && PPC
+	help
+	  Say Y if your machine has this type of Ethernet network card.
+
+	  This driver is also available as a module called oaknet.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config ARIADNE
+	tristate "Ariadne support"
+	depends on NET_ETHERNET && ZORRO
+	help
+	  If you have a Village Tronic Ariadne Ethernet adapter, say Y.
+	  Otherwise, say N.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you
+	  want). The module is called ariadne.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config NE2K_ZORRO
+	tristate "Ariadne II and X-Surf support"
+	depends on NET_ETHERNET && ZORRO
+
+config A2065
+	tristate "A2065 support"
+	depends on NET_ETHERNET && ZORRO
+	help
+	  If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
+	  say N.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you
+	  want). The module is called a2065.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config HYDRA
+	tristate "Hydra support"
+	depends on NET_ETHERNET && ZORRO
+	help
+	  If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you
+	  want). The module is called hydra.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config LASI_82596
+	tristate "Lasi ethernet"
+	depends on NET_ETHERNET && PARISC && GSC_LASI
+	help
+	  Say Y here to support the on-board Intel 82596 ethernet controller
+	  built into Hewlett-Packard PA-RISC machines.
+
+config MIPS_JAZZ_SONIC
+	tristate "MIPS JAZZ onboard SONIC Ethernet support"
+	depends on NET_ETHERNET && MIPS_JAZZ
+	help
+	  This is the driver for the onboard card of MIPS Magnum 4000,
+	  Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
+
+config MIPS_GT96100ETH
+	bool "MIPS GT96100 Ethernet support"
+	depends on NET_ETHERNET && MIPS_GT96100
+	help
+	  Say Y here to support the Ethernet subsystem on your GT96100 card.
+
+config MIPS_AU1000_ENET
+	bool "MIPS AU1000 Ethernet support"
+	depends on NET_ETHERNET && MIPS_AU1000
+	help
+	  If you have an Alchemy Semi AU1000 ethernet controller
+	  on an SGI MIPS system, say Y.  Otherwise, say N.
+
+config NET_SB1250_MAC
+	tristate "SB1250 Ethernet support"
+	depends on NET_ETHERNET && SIBYTE_SB1250
+
+config SGI_IOC3_ETH
+	bool "SGI IOC3 Ethernet"
+	depends on NET_ETHERNET && (IA64_SGI_SN1 || SGI_IP27)
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+config STNIC
+	tristate "National DP83902AV  support"
+	depends on NET_ETHERNET && SUPERH
+	help
+	  Support for cards based on the National Semiconductor DP83902AV
+	  ST-NIC Serial Network Interface Controller for Twisted Pair.  This
+	  is a 10Mbit/sec Ethernet controller.  Product overview and specs at
+	  <http://www.national.com/pf/DP/DP83902A.html>.
+
+	  If unsure, say N.
+
+config SUNLANCE
+	tristate "Sun LANCE support"
+	depends on NET_ETHERNET && SBUS
+	help
+	  This driver supports the "le" interface present on all 32-bit Sparc
+	  systems, on some older Ultra systems and as an Sbus option.  These
+	  cards are based on the AMD Lance chipset, which is better known
+	  via the NE2100 cards.
+
+	  This support is also available as a module called sunlance.o ( =
+	  code which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config HAPPYMEAL
+	tristate "Sun Happy Meal 10/100baseT support"
+	depends on NET_ETHERNET && (SBUS || PCI)
+	help
+	  This driver supports the "hme" interface present on most Ultra
+	  systems and as an option on older Sbus systems. This driver supports
+	  both PCI and Sbus devices. This driver also supports the "qfe" quad
+	  100baseT device available in both PCI and Sbus configurations.
+
+	  This support is also available as a module called sunhme.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config SUNBMAC
+	tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
+	depends on NET_ETHERNET && SBUS && EXPERIMENTAL
+	help
+	  This driver supports the "be" interface available as an Sbus option.
+	  This is Sun's older 100baseT Ethernet device.
+
+	  This support is also available as a module called sunbmac.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config SUNQE
+	tristate "Sun QuadEthernet support"
+	depends on NET_ETHERNET && SBUS
+	help
+	  This driver supports the "qe" 10baseT Ethernet device, available as
+	  an Sbus option. Note that this is not the same as Quad FastEthernet
+	  "qfe" which is supported by the Happy Meal driver instead.
+
+	  This support is also available as a module called sunqe.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config SUNGEM
+	tristate "Sun GEM support"
+	depends on NET_ETHERNET && PCI
+	help
+	  Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0.  See also
+	  <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
+
+config NET_VENDOR_3COM
+	bool "3COM cards"
+	depends on NET_ETHERNET
+	help
+	  If you have a network (Ethernet) card belonging to this class, say Y
+	  and read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  Note that the answer to this question doesn't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions about 3COM cards. If you say Y, you will be asked for
+	  your specific card in the following questions.
+
+config EL1
+	tristate "3c501 \"EtherLink\" support"
+	depends on NET_VENDOR_3COM && ISA
+	---help---
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  Also, consider buying a
+	  new card, since the 3c501 is slow, broken, and obsolete: you will
+	  have problems.  Some people suggest to ping ("man ping") a nearby
+	  machine every minute ("man cron") when using this card.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called 3c501.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config EL2
+	tristate "3c503 \"EtherLink II\" support"
+	depends on NET_VENDOR_3COM && ISA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called 3c503.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config ELPLUS
+	tristate "3c505 \"EtherLink Plus\" support"
+	depends on NET_VENDOR_3COM && ISA
+	---help---
+	  Information about this network (Ethernet) card can be found in
+	  <file:Documentation/networking/3c505.txt>.  If you have a card of
+	  this type, say Y and read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called 3c505.o.
+
+config EL16
+	tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
+	depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called 3c507.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config EL3
+	tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
+	depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
+	---help---
+	  If you have a network (Ethernet) card belonging to the 3Com
+	  EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
+	  from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If your card is not working you may need to use the DOS
+	  setup disk to disable Plug & Play mode, and to select the default
+	  media type.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called 3c509.o.
+
+config 3C515
+	tristate "3c515 ISA \"Fast EtherLink\""
+	depends on NET_VENDOR_3COM && (ISA || EISA)
+	help
+	  If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
+	  network card, say Y and read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called 3c515.o.
+
+config ELMC
+	tristate "3c523 \"EtherLink/MC\" support"
+	depends on NET_VENDOR_3COM && MCA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called 3c523.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config ELMC_II
+	tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
+	depends on NET_VENDOR_3COM && MCA && EXPERIMENTAL
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called 3c527.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config VORTEX
+	tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
+	depends on NET_VENDOR_3COM && (PCI || EISA)
+	---help---
+	  This option enables driver support for a large number of 10mbps and
+	  10/100mbps EISA, PCI and PCMCIA 3Com network cards:
+
+	  "Vortex"    (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
+	  "Boomerang" (EtherLink XL 3c900 or 3c905)            PCI
+	  "Cyclone"   (3c540/3c900/3c905/3c980/3c575/3c656)    PCI and Cardbus
+	  "Tornado"   (3c905)                                  PCI
+	  "Hurricane" (3c555/3cSOHO)                           PCI
+
+	  If you have such a card, say Y and read the Ethernet-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>. More
+	  specific information is in
+	  <file:Documentation/networking/vortex.txt> and in the comments at
+	  the beginning of <file:drivers/net/3c59x.c>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.
+
+config LANCE
+	tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
+	depends on NET_ETHERNET && ISA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>. Some LinkSys cards are
+	  of this type.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called lance.o.
+
+config NET_VENDOR_SMC
+	bool "Western Digital/SMC cards"
+	depends on NET_ETHERNET
+	help
+	  If you have a network (Ethernet) card belonging to this class, say Y
+	  and read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  Note that the answer to this question doesn't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions about Western Digital cards. If you say Y, you will be
+	  asked for your specific card in the following questions.
+
+config WD80x3
+	tristate "WD80*3 support"
+	depends on NET_VENDOR_SMC && ISA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called wd.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config ULTRAMCA
+	tristate "SMC Ultra MCA support"
+	depends on NET_VENDOR_SMC && MCA
+	help
+	  If you have a network (Ethernet) card of this type and are running
+	  an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called smc-mca.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config ULTRA
+	tristate "SMC Ultra support"
+	depends on NET_VENDOR_SMC && ISA
+	---help---
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  Important: There have been many reports that, with some motherboards
+	  mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
+	  such as some BusLogic models) causes corruption problems with many
+	  operating systems. The Linux smc-ultra driver has a work-around for
+	  this but keep it in mind if you have such a SCSI card and have
+	  problems.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called smc-ultra.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt> as
+	  well as <file:Documentation/networking/net-modules.txt>.
+
+config ULTRA32
+	tristate "SMC Ultra32 EISA support"
+	depends on NET_VENDOR_SMC && EISA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called smc-ultra32.o.  If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt> as
+	  well as <file:Documentation/networking/net-modules.txt>.
+
+config SMC9194
+	tristate "SMC 9194 support"
+	depends on NET_VENDOR_SMC && ISA
+	---help---
+	  This is support for the SMC9xxx based Ethernet cards. Choose this
+	  option if you have a DELL laptop with the docking station, or
+	  another SMC9192/9194 based chipset.  Say Y if you want it compiled
+	  into the kernel, and read the file
+	  <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called smc9194.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config NET_VENDOR_RACAL
+	bool "Racal-Interlan (Micom) NI cards"
+	depends on NET_ETHERNET
+	help
+	  If you have a network (Ethernet) card belonging to this class, such
+	  as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  Note that the answer to this question doesn't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions about NI cards. If you say Y, you will be asked for
+	  your specific card in the following questions.
+
+config NI5010
+	tristate "NI5010 support (EXPERIMENTAL)"
+	depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL
+	---help---
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>. Note that this is still
+	  experimental code.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ni5010.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config NI52
+	tristate "NI5210 support"
+	depends on NET_VENDOR_RACAL && ISA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ni52.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config NI65
+	tristate "NI6510 support"
+	depends on NET_VENDOR_RACAL && ISA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ni65.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+source "drivers/net/tulip/Kconfig"
+
+config AT1700
+	tristate "AT1700/1720 support (EXPERIMENTAL)"
+	depends on NET_ETHERNET && (ISA || MCA) && EXPERIMENTAL
+	---help---
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called at1700.o.
+
+config DEPCA
+	tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
+	depends on NET_ETHERNET && (ISA || EISA || MCA)
+	---help---
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto> as well as
+	  <file:drivers/net/depca.c>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called
+	  depca.o.
+
+config HP100
+	tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
+	depends on NET_ETHERNET && (ISA || EISA || PCI)
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called hp100.o.
+
+config NET_ISA
+	bool "Other ISA cards"
+	depends on NET_ETHERNET && ISA
+	---help---
+	  If your network (Ethernet) card hasn't been mentioned yet and its
+	  bus system (that's the way the cards talks to the other components
+	  of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
+	  Make sure you know the name of your card. Read the Ethernet-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If unsure, say Y.
+
+	  Note that the answer to this question doesn't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the remaining ISA network card questions. If you say Y, you will be
+	  asked for your specific card in the following questions.
+
+config E2100
+	tristate "Cabletron E21xx support"
+	depends on NET_ISA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called e2100.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config EWRK3
+	tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
+	depends on NET_ISA
+	---help---
+	  This driver supports the DE203, DE204 and DE205 network (Ethernet)
+	  cards. If this is for you, say Y and read
+	  <file:Documentation/networking/ewrk3.txt> in the kernel source as
+	  well as the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called ewrk3.o.
+
+config EEXPRESS
+	tristate "EtherExpress 16 support"
+	depends on NET_ISA
+	---help---
+	  If you have an EtherExpress16 network (Ethernet) card, say Y and
+	  read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  Note that the Intel
+	  EtherExpress16 card used to be regarded as a very poor choice
+	  because the driver was very unreliable. We now have a new driver
+	  that should do better.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called eexpress.o.
+
+config EEXPRESS_PRO
+	tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
+	depends on NET_ISA
+	---help---
+	  If you have a network (Ethernet) card of this type, say Y. This
+	  driver supports intel i82595{FX,TX} based boards. Note however
+	  that the EtherExpress PRO/100 Ethernet card has its own separate
+	  driver.  Please read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called eepro.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config FMV18X
+	tristate "FMV-181/182/183/184 support (OBSOLETE)"
+	depends on NET_ISA && OBSOLETE
+	---help---
+	  If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
+	  say Y and read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you use an FMV-183 or FMV-184 and it is not working, you may need
+	  to disable Plug & Play mode of the card.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called fmv18x.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config HPLAN_PLUS
+	tristate "HP PCLAN+ (27247B and 27252A) support"
+	depends on NET_ISA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called hp-plus.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config HPLAN
+	tristate "HP PCLAN (27245 and other 27xxx series) support"
+	depends on NET_ISA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called hp.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config LP486E
+	tristate "LP486E on board Ethernet"
+	depends on NET_ISA
+	help
+	  Say Y here to support the 82596-based on-board Ethernet controller
+	  for the Panther motherboard, which is one of the two shipped in the
+	  Intel Professional Workstation.
+
+config ETH16I
+	tristate "ICL EtherTeam 16i/32 support"
+	depends on NET_ISA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called eth16i.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config NE2000
+	tristate "NE2000/NE1000 support"
+	depends on NET_ISA
+	---help---
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  Many Ethernet cards
+	  without a specific driver are compatible with NE2000.
+
+	  If you have a PCI NE2000 card however, say N here and Y to "PCI
+	  NE2000 support", above. If you have a NE2000 card and are running on
+	  an MCA system (a bus system used on some IBM PS/2 computers and
+	  laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
+	  below.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ne.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config ZNET
+	tristate "Zenith Z-Note support (EXPERIMENTAL)"
+	depends on NET_ISA && EXPERIMENTAL
+	help
+	  The Zenith Z-Note notebook computer has a built-in network
+	  (Ethernet) card, and this is the Linux driver for it. Note that the
+	  IBM Thinkpad 300 is compatible with the Z-Note and is also supported
+	  by this driver. Read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+config SEEQ8005
+	tristate "SEEQ8005 support (EXPERIMENTAL)"
+	depends on NET_ISA && OBSOLETE && EXPERIMENTAL
+	help
+	  This is a driver for the SEEQ 8005 network (Ethernet) card.  If this
+	  is for you, read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called ewrk3.o.
+
+config SK_G16
+	tristate "SK_G16 support (OBSOLETE)"
+	depends on NET_ISA && OBSOLETE
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+config SKMC
+	tristate "SKnet MCA support"
+	depends on NET_ETHERNET && MCA
+	---help---
+	  These are Micro Channel Ethernet adapters. You need to say Y to "MCA
+	  support" in order to use this driver.  Supported cards are the SKnet
+	  Junior MC2 and the SKnet MC2(+).  The driver automatically
+	  distinguishes between the two cards. Note that using multiple boards
+	  of different type hasn't been tested with this driver.  Say Y if you
+	  have one of these Ethernet adapters.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module is called sk_mca.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config NE2_MCA
+	tristate "NE/2 (ne2000 MCA version) support"
+	depends on NET_ETHERNET && MCA
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ne2.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config IBMLANA
+	tristate "IBM LAN Adapter/A support"
+	depends on NET_ETHERNET && MCA
+	---help---
+	  This is a Micro Channel Ethernet adapter.  You need to set
+	  CONFIG_MCA to use this driver.  It is both available as an in-kernel
+	  driver and as a module ( = code which can be inserted in and removed
+	  from the running kernel whenever you want).  If you want to compile
+	  it as a module, say M here and read <file:Documentation/modules.txt>
+	  as well as <file:Documentation/networking/net-modules.txt>. The only
+	  currently supported card is the IBM LAN Adapter/A for Ethernet.  It
+	  will both support 16K and 32K memory windows, however a 32K window
+	  gives a better security against packet losses.  Usage of multiple
+	  boards with this driver should be possible, but has not been tested
+	  up to now due to lack of hardware.
+
+config NET_PCI
+	bool "EISA, VLB, PCI and on board controllers"
+	depends on NET_ETHERNET && (ISA || EISA || PCI)
+	help
+	  This is another class of network cards which attach directly to the
+	  bus. If you have one of those, say Y and read the Ethernet-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  Note that the answer to this question doesn't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions about this class of network cards. If you say Y, you
+	  will be asked for your specific card in the following questions. If
+	  you are unsure, say Y.
+
+config PCNET32
+	tristate "AMD PCnet32 PCI support"
+	depends on NET_PCI && PCI
+	help
+	  If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
+	  answer Y here and read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called pcnet32.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config ADAPTEC_STARFIRE
+	tristate "Adaptec Starfire/DuraLAN support"
+	depends on NET_PCI && PCI
+	help
+	  Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
+	  adapter. The DuraLAN chip is used on the 64 bit PCI boards from
+	  Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
+	  driver.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called starfire.o.
+
+config AC3200
+	tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
+	depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ac3200.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config APRICOT
+	tristate "Apricot Xen-II on board Ethernet"
+	depends on NET_PCI && ISA
+	help
+	  If you have a network (Ethernet) controller of this type, say Y and
+	  read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called apricot.o.
+
+config CS89x0
+	tristate "CS89x0 support"
+	depends on NET_PCI && ISA
+	---help---
+	  Support for CS89x0 chipset based Ethernet cards. If you have a
+	  network (Ethernet) card of this type, say Y and read the
+	  Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto> as well as
+	  <file:Documentation/networking/cs89x0.txt>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called cs89x.o.
+
+config DGRS
+	tristate "Digi Intl. RightSwitch SE-X support"
+	depends on NET_PCI && (PCI || EISA)
+	---help---
+	  This is support for the Digi International RightSwitch series of
+	  PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
+	  models.  If you have a network card of this type, say Y and read the
+	  Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  More specific
+	  information is contained in <file:Documentation/networking/dgrs.txt>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called dgrs.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config EEPRO100
+	tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
+	depends on NET_PCI && PCI
+	help
+	  If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
+	  card, say Y and read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called eepro100.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt> as
+	  well as <file:Documentation/networking/net-modules.txt>.
+
+config E100
+	tristate "EtherExpressPro/100 support (e100, Alternate Intel driver)"
+	depends on NET_PCI && PCI
+	---help---
+	  This driver supports Intel(R) PRO/100 family of adapters, which 
+	  includes:
+
+	  Controller  Adapter Name                       Board IDs
+	  ----------  ------------                       ---------
+
+	  82558       PRO/100+ PCI Adapter               668081-xxx, 
+	  689661-xxx
+	  82558       PRO/100+ Management Adapter        691334-xxx, 
+	  701738-xxx,
+	  721383-xxx
+	  82558       PRO/100+ Dual Port Server Adapter  714303-xxx, 
+	  711269-xxx, 
+	  A28276-xxx
+	  82558       PRO/100+ PCI Server Adapter        710550-xxx
+	  82550       PRO/100 S Server Adapter           752438-xxx
+	  82559                                          A56831-xxx, 
+	  A10563-xxx,
+	  A12171-xxx, 
+	  A12321-xxx, 
+	  A12320-xxx, 
+	  A12170-xxx
+	  748568-xxx
+	  748565-xxx
+	  82550       PRO/100 S Desktop Adapter          751767-xxx
+	  82559                                          748592-xxx, 
+	  A12167-xxx, 
+	  A12318-xxx, 
+	  A12317-xxx, 
+	  A12165-xxx,
+	  748569-xxx 
+	  82559       PRO/100+ Server Adapter            729757-xxx
+	  82559       PRO/100 S Management Adapter       748566-xxx, 
+	  748564-xxx
+	  82550       PRO/100 S Dual Port Server Adapter A56831-xxx
+	  82551       PRO/100 M Desktop Adapter          A80897-xxx
+	  PRO/100 S Advanced Management Adapter 
+	  747842-xxx, 
+	  745171-xxx
+	  CNR         PRO/100 VE Desktop Adapter         A10386-xxx, 
+	  A10725-xxx, 
+	  A23801-xxx, 
+	  A19716-xxx
+	  PRO/100 VM Desktop Adapter         A14323-xxx, 
+	  A19725-xxx, 
+	  A23801-xxx, 
+	  A22220-xxx, 
+	  A23796-xxx
+
+
+	  To verify that your adapter is supported, find the board ID number 
+	  on the adapter. Look for a label that has a barcode and a number 
+	  in the format 123456-001 (six digits hyphen three digits). Match 
+	  this to the list of numbers above.
+
+	  For more information on how to identify your adapter, go to the 
+	  Adapter & Driver ID Guide at:
+
+	  http://support.intel.com/support/network/adapter/pro100/21397.htm
+
+	  For the latest Intel PRO/100 network driver for Linux, see:
+
+	  http://appsr.intel.com/scripts-df/support_intel.asp
+
+	  More specific information on configuring the driver is in 
+	  <file:Documentation/networking/e100.txt>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called e100.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config LNE390
+	tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
+	depends on NET_PCI && EISA && EXPERIMENTAL
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called lne390.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config FEALNX
+	tristate "Myson MTD-8xx PCI Ethernet support"
+	depends on NET_PCI && PCI
+	help
+	  Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
+	  cards. Specifications and data at
+	  <http://www.myson.com.hk/mtd/datasheet/>.
+
+config NATSEMI
+	tristate "National Semiconductor DP8381x series PCI Ethernet support"
+	depends on NET_PCI && PCI
+	help
+	  This driver is for the National Semiconductor DP83810 series,
+	  which is used in cards from PureData, NetGear, Linksys
+	  and others, including the 83815 chip.
+	  More specific information and updates are available from
+	  <http://www.scyld.com/network/natsemi.html>.
+
+config NE2K_PCI
+	tristate "PCI NE2000 and clones support (see help)"
+	depends on NET_PCI && PCI
+	---help---
+	  This driver is for NE2000 compatible PCI cards. It will not work
+	  with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
+	  support" below). If you have a PCI NE2000 network (Ethernet) card,
+	  say Y and read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver also works for the following NE2000 clone cards:
+	  RealTek RTL-8029  Winbond 89C940  Compex RL2000  KTI ET32P2
+	  NetVin NV5000SC   Via 86C926      SureCom NE34   Winbond
+	  Holtek HT80232    Holtek HT80229
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ne2k-pci.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt> as
+	  well as <file:Documentation/networking/net-modules.txt>.
+
+config NE3210
+	tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
+	depends on NET_PCI && EISA && EXPERIMENTAL
+	---help---
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  Note that this driver
+	  will NOT WORK for NE3200 cards as they are completely different.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ne3210.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config ES3210
+	tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
+	depends on NET_PCI && EISA && EXPERIMENTAL
+	help
+	  If you have a network (Ethernet) card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called es3210.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config 8139CP
+	tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
+	depends on NET_PCI && PCI && EXPERIMENTAL
+	help
+	  This is a driver for the Fast Ethernet PCI network cards based on
+	  the RTL8139C+ chips. If you have one of those, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read Documentation/modules.txt. This is recommended.
+	  The module will be called 8139cp.o.
+
+config 8139TOO
+	tristate "RealTek RTL-8139 PCI Fast Ethernet Adapter support"
+	depends on NET_PCI && PCI
+	---help---
+	  This is a driver for the Fast Ethernet PCI network cards based on
+	  the RTL8139 chips. If you have one of those, say Y and read
+	  <file:Documentation/networking/8139too.txt> as well as the
+	  Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called 8139too.o.
+
+config 8139TOO_PIO
+	bool "Use PIO instead of MMIO"
+	depends on 8139TOO
+	help
+	  This instructs the driver to use programmed I/O ports (PIO) instead
+	  of PCI shared memory (MMIO).  This can possibly solve some problems
+	  in case your mainboard has memory consistency issues.  If unsure,
+	  say N.
+
+config 8139TOO_TUNE_TWISTER
+	bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
+	depends on 8139TOO
+	help
+	  This implements a function which might come in handy in case you
+	  are using low quality on long cabling. It is required for RealTek
+	  RTL-8139 revision K boards, and totally unused otherwise.  It tries
+	  to match the transceiver to the cable characteristics. This is
+	  experimental since hardly documented by the manufacturer.
+	  If unsure, say Y.
+
+config 8139TOO_8129
+	bool "Support for older RTL-8129/8130 boards"
+	depends on 8139TOO
+	help
+	  This enables support for the older and uncommon RTL-8129 and
+	  RTL-8130 chips, which support MII via an external transceiver,
+	  instead of an internal one.  Disabling this option will save some
+	  memory by making the code size smaller.  If unsure, say Y.
+
+config 8139_OLD_RX_RESET
+	bool "Use older RX-reset method"
+	depends on 8139TOO
+	help
+	  The 8139too driver was recently updated to contain a more rapid
+	  reset sequence, in the face of severe receive errors.  This "new"
+	  RX-reset method should be adequate for all boards.  But if you
+	  experience problems, you can enable this option to restore the
+	  old RX-reset behavior.  If unsure, say N.
+
+config SIS900
+	tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
+	depends on NET_PCI && PCI
+	---help---
+	  This is a driver for the Fast Ethernet PCI network cards based on
+	  the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
+	  SiS 630 and SiS 540 chipsets.  If you have one of those, say Y and
+	  read the Ethernet-HOWTO, available at
+	  <http://www.linuxdoc.org/docs.html#howto>.  Please read
+	  <file:Documentation/networking/sis900.txt> and comments at the
+	  beginning of <file:drivers/net/sis900.c> for more information.
+
+	  This driver also supports AMD 79C901 HomePNA so that you can use
+	  your phone line as a network cable.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called sis900.o.
+
+config EPIC100
+	tristate "SMC EtherPower II"
+	depends on NET_PCI && PCI
+	help
+	  This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
+	  which is based on the SMC83c17x (EPIC/100).
+	  More specific information and updates are available from
+	  <http://www.scyld.com/network/epic100.html>.
+
+config SUNDANCE
+	tristate "Sundance Alta support"
+	depends on NET_PCI && PCI
+	help
+	  This driver is for the Sundance "Alta" chip.
+	  More specific information and updates are available from
+	  <http://www.scyld.com/network/sundance.html>.
+
+config SUNDANCE_MMIO
+	bool "Use MMIO instead of PIO"
+	depends on SUNDANCE
+	help
+	  Enable memory-mapped I/O for interaction with Sundance NIC registers.
+	  Do NOT enable this by default, PIO (enabled when MMIO is disabled)
+	  is known to solve bugs on certain chips.
+
+	  If unsure, say N.
+
+config TLAN
+	tristate "TI ThunderLAN support"
+	depends on NET_PCI && (PCI || EISA)
+	---help---
+	  If you have a PCI Ethernet network card based on the ThunderLAN chip
+	  which is supported by this driver, say Y and read the
+	  Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  Devices currently supported by this driver are Compaq Netelligent,
+	  Compaq NetFlex and Olicom cards.  Please read the file
+	  <file:Documentation/networking/tlan.txt> for more details.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called tlan.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+	  Please email feedback to  torben.mathiasen@compaq.com.
+
+config VIA_RHINE
+	tristate "VIA Rhine support"
+	depends on NET_PCI && PCI
+	help
+	  If you have a VIA "rhine" based network card (Rhine-I (3043) or
+	  Rhine-2 (VT86c100A)), say Y here.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called via-rhine.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt> as
+	  well as <file:Documentation/networking/net-modules.txt>.
+
+config VIA_RHINE_MMIO
+	bool "Use MMIO instead of PIO (EXPERIMENTAL)"
+	depends on VIA_RHINE && EXPERIMENTAL
+	help
+	  This instructs the driver to use PCI shared memory (MMIO) instead of
+	  programmed I/O ports (PIO). Enabling this gives an improvement in
+	  processing time in parts of the driver.
+
+	  It is not known if this works reliably on all "rhine" based cards,
+	  but it has been tested successfully on some DFE-530TX adapters.
+
+	  If unsure, say N.
+
+config LAN_SAA9730
+	bool "Philips SAA9730 Ethernet support (EXPERIMENTAL)"
+	depends on NET_PCI && EXPERIMENTAL && MIPS
+	help
+	  The SAA9730 is a combined multimedia and peripheral controller used
+	  in thin clients, Internet access terminals, and diskless
+	  workstations.
+	  See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
+
+config NET_POCKET
+	bool "Pocket and portable adapters"
+	depends on NET_ETHERNET
+	---help---
+	  Cute little network (Ethernet) devices which attach to the parallel
+	  port ("pocket adapters"), commonly used with laptops. If you have
+	  one of those, say Y and read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to plug a network (or some other) card into the PCMCIA
+	  (or PC-card) slot of your laptop instead (PCMCIA is the standard for
+	  credit card size extension cards used by all modern laptops), you
+	  need the pcmcia-cs package (location contained in the file
+	  <file:Documentation/Changes>) and you can say N here.
+
+	  Laptop users should read the Linux Laptop home page at
+	  <http://www.cs.utexas.edu/users/kharker/linux-laptop/>.
+
+	  Note that the answer to this question doesn't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions about this class of network devices. If you say Y, you
+	  will be asked for your specific device in the following questions.
+
+config ATP
+	tristate "AT-LAN-TEC/RealTek pocket adapter support"
+	depends on NET_POCKET && ISA && X86
+	---help---
+	  This is a network (Ethernet) device which attaches to your parallel
+	  port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>, if you
+	  want to use this.  If you intend to use this driver, you should have
+	  said N to the "Parallel printer support", because the two drivers
+	  don't like each other.
+
+	  If you want to compile this driver as a module however ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want), say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called atp.o.
+
+config DE600
+	tristate "D-Link DE600 pocket adapter support"
+	depends on NET_POCKET && ISA
+	---help---
+	  This is a network (Ethernet) device which attaches to your parallel
+	  port. Read <file:Documentation/networking/DLINK.txt> as well as the
+	  Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>, if you want to use
+	  this. It is possible to have several devices share a single parallel
+	  port and it is safe to compile the corresponding drivers into the
+	  kernel.
+
+	  If you want to compile this driver as a module however ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want), say M here and read
+	  <file:Documentation/modules.txt>.
+	  The module will be called de600.o.
+
+config DE620
+	tristate "D-Link DE620 pocket adapter support"
+	depends on NET_POCKET && ISA
+	---help---
+	  This is a network (Ethernet) device which attaches to your parallel
+	  port. Read <file:Documentation/networking/DLINK.txt> as well as the
+	  Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>, if you want to use
+	  this. It is possible to have several devices share a single parallel
+	  port and it is safe to compile the corresponding drivers into the
+	  kernel.
+
+	  If you want to compile this driver as a module however ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want), say M here and read
+	  <file:Documentation/modules.txt>.
+	  The module will be called de620.o.
+
+config SGISEEQ
+	bool "SGI Seeq ethernet controller support"
+	depends on NET_ETHERNET && SGI_IP22
+	help
+	  Say Y here if you have an Seeq based Ethernet network card. This is
+	  used in many Silicon Graphics machines.
+
+config DECLANCE
+	bool "DEC LANCE ethernet controller support"
+	depends on NET_ETHERNET && DECSTATION
+	help
+	  This driver is for the series of Ethernet controllers produced by
+	  DEC (now Compaq) based on the AMD Lance chipset, including the
+	  DEPCA series.  (This chipset is better known via the NE2100 cards.)
+
+config BAGETLANCE
+	tristate "Baget AMD LANCE support"
+	depends on NET_ETHERNET && BAGET_MIPS
+	help
+	  Say Y to enable kernel support for AMD Lance Ethernet cards on the
+	  MIPS-32-based Baget embedded system.  This chipset is better known
+	  via the NE2100 cards.
+
+endmenu
+
+#
+#	Gigabit Ethernet
+#
+
+menu "Ethernet (1000 Mbit)"
+	depends on NETDEVICES
+
+config ACENIC
+	tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
+	depends on PCI
+	---help---
+	  Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
+	  GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
+	  adapter. The driver allows for using the Jumbo Frame option (9000
+	  bytes/frame) however it requires that your switches can handle this
+	  as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
+	  line.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called acenic.o.
+
+config ACENIC_OMIT_TIGON_I
+	bool "Omit support for old Tigon I based AceNICs"
+	depends on ACENIC
+	help
+	  Say Y here if you only have Tigon II based AceNICs and want to leave
+	  out support for the older Tigon I based cards which are no longer
+	  being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
+	  version)).  This will reduce the size of the driver object by
+	  app. 100KB.  If you are not sure whether your card is a Tigon I or a
+	  Tigon II, say N here.
+
+	  The safe and default value for this is N.
+
+config DL2K
+	tristate "D-Link DL2000-based Gigabit Ethernet support"
+	depends on PCI
+	help
+	  This driver supports D-Link 2000-based gigabit ethernet cards, which
+	  includes
+	  D-Link DGE-550T Gigabit Ethernet Adapter.
+	  D-Link DL2000-based Gigabit Ethernet Adapter.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called dl2k.o.
+
+config E1000
+	tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
+	depends on PCI
+	---help---
+	  This driver supports Intel(R) PRO/1000 gigabit ethernet family of
+	  adapters, which includes:
+
+	  Controller  Adapter Name                         Board IDs
+	  ----------  ------------                         ---------
+	  82542       PRO/1000 Gigabit Server Adapter      700262-xxx,
+	  717037-xxx
+	  82543       PRO/1000 F Server Adapter            738640-xxx,
+	  A38888-xxx
+	  82543       PRO/1000 T Server Adapter            A19845-xxx,
+	  A33948-xxx
+	  82544       PRO/1000 XT Server Adapter           A51580-xxx
+	  82544       PRO/1000 XF Server Adapter           A50484-xxx
+	  82544       PRO/1000 T Desktop Adapter           A62947-xxx
+	  82540       PRO/1000 MT Desktop Adapter          A78408-xxx
+	  82545       PRO/1000 MT Server Adapter           A92165-xxx
+	  82546       PRO/1000 MT Dual Port Server Adapter A92111-xxx
+	  82545       PRO/1000 MF Server Adapter           A91622-xxx
+	  82545       PRO/1000 MF Server Adapter(LX)       A91624-xxx
+	  82546       PRO/1000 MF Dual Port Server Adapter A91620-xxx 
+
+	  For more information on how to identify your adapter, go to the
+	  Adapter & Driver ID Guide at:
+
+	  <http://support.intel.com/support/network/adapter/pro100/21397.htm>
+
+	  For general information and support, go to the Intel support
+	  website at:
+
+	  <http://support.intel.com>
+
+	  More specific information on configuring the driver is in 
+	  <file:Documentation/networking/e1000.txt>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called e1000.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config E1000_NAPI
+	bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
+	depends on E1000 && EXPERIMENTAL
+
+config MYRI_SBUS
+	tristate "MyriCOM Gigabit Ethernet support"
+	depends on SBUS
+	help
+	  This driver supports MyriCOM Sbus gigabit Ethernet cards.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called myri_sbus.o.
+
+config NS83820
+	tristate "National Semiconduct DP83820 support"
+	depends on PCI
+	help
+	  This is a driver for the National Semiconductor DP83820 series
+	  of gigabit ethernet MACs.  Cards using this chipset include
+	  the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
+	  SOHO-GA2000T, SOHO-GA2500T.  The driver supports the use of
+	  zero copy.
+
+config HAMACHI
+	tristate "Packet Engines Hamachi GNIC-II support"
+	depends on PCI
+	help
+	  If you have a Gigabit Ethernet card of this type, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called hamachi.o.
+
+config YELLOWFIN
+	tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
+	depends on PCI && EXPERIMENTAL
+	---help---
+	  Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
+	  adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
+	  used by the Beowulf Linux cluster project.  See
+	  <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
+	  information about this driver in particular and Beowulf in general.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called yellowfin.o.
+
+config SK98LIN
+	tristate "SysKonnect SK-98xx support"
+	depends on PCI
+	---help---
+	  Say Y here if you have a SysKonnect SK-98xx Gigabit Ethernet Server
+	  Adapter. The following adapters are supported by this driver:
+	  - SK-9841 (single link 1000Base-LX)
+	  - SK-9842 (dual link   1000Base-LX)
+	  - SK-9843 (single link 1000Base-SX)
+	  - SK-9844 (dual link   1000Base-SX)
+	  - SK-9821 (single link 1000Base-T)
+	  - SK-9822 (dual link   1000Base-T)
+	  - SK-9861 (single link Volition connector)
+	  - SK-9862 (dual link   Volition connector)
+	  The driver also supports the following adapters from Allied Telesyn:
+	  - AT2970...
+
+	  The dual link adapters support a link-failover feature.  Read
+	  <file:Documentation/networking/sk98lin.txt> for information about
+	  optional driver parameters.
+	  Questions concerning this driver may be addressed to:
+	  linux@syskonnect.de
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called sk98lin.o.
+
+config TIGON3
+	tristate "Broadcom Tigon3 support"
+	depends on PCI
+	help
+	  This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called tg3.o.
+
+endmenu
+
+config VETH
+	tristate "iSeries Virtual Ethernet driver support"
+	depends on NETDEVICES && PPC_ISERIES
+
+config FDDI
+	bool "FDDI driver support"
+	depends on NETDEVICES
+	help
+	  Fiber Distributed Data Interface is a high speed local area network
+	  design; essentially a replacement for high speed Ethernet. FDDI can
+	  run over copper or fiber. If you are connected to such a network and
+	  want a driver for the FDDI card in your computer, say Y here (and
+	  then also Y to the driver for your FDDI card, below). Most people
+	  will say N.
+
+config DEFXX
+	tristate "Digital DEFEA and DEFPA adapter support"
+	depends on FDDI && (PCI || EISA)
+	help
+	  This is support for the DIGITAL series of EISA (DEFEA) and PCI
+	  (DEFPA) controllers which can connect you to a local FDDI network.
+
+config SKFP
+	tristate "SysKonnect FDDI PCI support"
+	depends on FDDI && PCI
+	---help---
+	  Say Y here if you have a SysKonnect FDDI PCI adapter.
+	  The following adapters are supported by this driver:
+	  - SK-5521 (SK-NET FDDI-UP)
+	  - SK-5522 (SK-NET FDDI-UP DAS)
+	  - SK-5541 (SK-NET FDDI-FP)
+	  - SK-5543 (SK-NET FDDI-LP)
+	  - SK-5544 (SK-NET FDDI-LP DAS)
+	  - SK-5821 (SK-NET FDDI-UP64)
+	  - SK-5822 (SK-NET FDDI-UP64 DAS)
+	  - SK-5841 (SK-NET FDDI-FP64)
+	  - SK-5843 (SK-NET FDDI-LP64)
+	  - SK-5844 (SK-NET FDDI-LP64 DAS)
+	  - Netelligent 100 FDDI DAS Fibre SC
+	  - Netelligent 100 FDDI SAS Fibre SC
+	  - Netelligent 100 FDDI DAS UTP
+	  - Netelligent 100 FDDI SAS UTP
+	  - Netelligent 100 FDDI SAS Fibre MIC
+
+	  Read <file:Documentation/networking/skfp.txt> for information about
+	  the driver.
+
+	  Questions concerning this driver can be addressed to:
+	  linux@syskonnect.de
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called skfp.o.
+
+config HIPPI
+	bool "HIPPI driver support (EXPERIMENTAL)"
+	depends on NETDEVICES && EXPERIMENTAL && INET
+	help
+	  HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
+	  1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
+	  can run over copper (25m) or fiber (300m on multi-mode or 10km on
+	  single-mode). HIPPI networks are commonly used for clusters and to
+	  connect to super computers. If you are connected to a HIPPI network
+	  and have a HIPPI network card in your computer that you want to use
+	  under Linux, say Y here (you must also remember to enable the driver
+	  for your HIPPI card below). Most people will say N here.
+
+config ROADRUNNER
+	tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
+	depends on HIPPI && PCI
+	help
+	  Say Y here if this is your PCI HIPPI network card.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called rrunner.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.  If
+	  unsure, say N.
+
+config ROADRUNNER_LARGE_RINGS
+	bool "Use large TX/RX rings (EXPERIMENTAL)"
+	depends on ROADRUNNER
+	help
+	  If you say Y here, the RoadRunner driver will preallocate up to 2 MB
+	  of additional memory to allow for fastest operation, both for
+	  transmitting and receiving. This memory cannot be used by any other
+	  kernel code or by user space programs. Say Y here only if you have
+	  the memory.
+
+config PLIP
+	tristate "PLIP (parallel port) support"
+	depends on NETDEVICES && PARPORT
+	---help---
+	  PLIP (Parallel Line Internet Protocol) is used to create a
+	  reasonably fast mini network consisting of two (or, rarely, more)
+	  local machines.  A PLIP link from a Linux box is a popular means to
+	  install a Linux distribution on a machine which doesn't have a
+	  CD-ROM drive (a minimal system has to be transferred with floppies
+	  first). The kernels on both machines need to have this PLIP option
+	  enabled for this to work.
+
+	  The PLIP driver has two modes, mode 0 and mode 1.  The parallel
+	  ports (the connectors at the computers with 25 holes) are connected
+	  with "null printer" or "Turbo Laplink" cables which can transmit 4
+	  bits at a time (mode 0) or with special PLIP cables, to be used on
+	  bidirectional parallel ports only, which can transmit 8 bits at a
+	  time (mode 1); you can find the wiring of these cables in
+	  <file:Documentation/networking/PLIP.txt>.  The cables can be up to
+	  15m long.  Mode 0 works also if one of the machines runs DOS/Windows
+	  and has some PLIP software installed, e.g. the Crynwr PLIP packet
+	  driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
+	  and winsock or NCSA's telnet.
+
+	  If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
+	  as the NET-3-HOWTO, both available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  Note that the PLIP
+	  protocol has been changed and this PLIP driver won't work together
+	  with the PLIP support in Linux versions 1.0.x.  This option enlarges
+	  your kernel by about 8 KB.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.  The module will be
+	  called plip.o.  If unsure, say Y or M, in case you buy a laptop
+	  later.
+
+config PPP
+	tristate "PPP (point-to-point protocol) support"
+	depends on NETDEVICES
+	---help---
+	  PPP (Point to Point Protocol) is a newer and better SLIP.  It serves
+	  the same purpose: sending Internet traffic over telephone (and other
+	  serial) lines.  Ask your access provider if they support it, because
+	  otherwise you can't use it; most Internet access providers these
+	  days support PPP rather than SLIP.
+
+	  To use PPP, you need an additional program called pppd as described
+	  in the PPP-HOWTO, available at
+	  <http://www.linuxdoc.org/docs.html#howto>.  Make sure that you have
+	  the version of pppd recommended in <file:Documentation/Changes>.
+	  The PPP option enlarges your kernel by about 16 KB.
+
+	  There are actually two versions of PPP: the traditional PPP for
+	  asynchronous lines, such as regular analog phone lines, and
+	  synchronous PPP which can be used over digital ISDN lines for
+	  example.  If you want to use PPP over phone lines or other
+	  asynchronous serial lines, you need to say Y (or M) here and also to
+	  the next option, "PPP support for async serial ports".  For PPP over
+	  synchronous lines, you should say Y (or M) here and to "Support
+	  synchronous PPP", below.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  If you said Y to "Version information on all symbols" above, then
+	  you cannot compile the PPP driver into the kernel; you can then only
+	  compile it as a module.  The module will be called ppp_generic.o.
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.
+
+config PPP_MULTILINK
+	bool "PPP multilink support (EXPERIMENTAL)"
+	depends on PPP && EXPERIMENTAL
+	help
+	  PPP multilink is a protocol (defined in RFC 1990) which allows you
+	  to combine several (logical or physical) lines into one logical PPP
+	  connection, so that you can utilize your full bandwidth.
+
+	  This has to be supported at the other end as well and you need a
+	  version of the pppd daemon which understands the multilink protocol.
+
+	  If unsure, say N.
+
+config PPP_FILTER
+	bool "PPP filtering"
+	depends on PPP && FILTER
+	help
+	  Say Y here if you want to be able to filter the packets passing over
+	  PPP interfaces.  This allows you to control which packets count as
+	  activity (i.e. which packets will reset the idle timer or bring up
+	  a demand-dialled link) and which packets are to be dropped entirely.
+	  You need to say Y here if you wish to use the pass-filter and
+	  active-filter options to pppd.
+
+	  If unsure, say N.
+
+config PPP_ASYNC
+	tristate "PPP support for async serial ports"
+	depends on PPP
+	---help---
+	  Say Y (or M) here if you want to be able to use PPP over standard
+	  asynchronous serial ports, such as COM1 or COM2 on a PC.  If you use
+	  a modem (not a synchronous or ISDN modem) to contact your ISP, you
+	  need this option.
+
+	  This code is also available as a module (code which can be inserted
+	  into and removed from the running kernel).  If you want to compile
+	  it as a module, say M here and read <file:Documentation/modules.txt>.
+
+	  If unsure, say Y.
+
+config PPP_SYNC_TTY
+	tristate "PPP support for sync tty ports"
+	depends on PPP
+	help
+	  Say Y (or M) here if you want to be able to use PPP over synchronous
+	  (HDLC) tty devices, such as the SyncLink adapter. These devices
+	  are often used for high-speed leased lines like T1/E1.
+
+	  This code is also available as a module (code which can be inserted
+	  into and removed from the running kernel).  If you want to compile
+	  it as a module, say M here and read
+	  <file:Documentation/modules.txt>.
+
+config PPP_DEFLATE
+	tristate "PPP Deflate compression"
+	depends on PPP
+	---help---
+	  Support for the Deflate compression method for PPP, which uses the
+	  Deflate algorithm (the same algorithm that gzip uses) to compress
+	  each PPP packet before it is sent over the wire.  The machine at the
+	  other end of the PPP link (usually your ISP) has to support the
+	  Deflate compression method as well for this to be useful.  Even if
+	  they don't support it, it is safe to say Y here.
+
+	  This code is also available as a module (code which can be inserted
+	  into and removed from the running kernel).  If you want to compile
+	  it as a module, say M here and read
+	  <file:Documentation/modules.txt>.
+
+config PPP_BSDCOMP
+	tristate "PPP BSD-Compress compression"
+	depends on PPP
+	---help---
+	  Support for the BSD-Compress compression method for PPP, which uses
+	  the LZW compression method to compress each PPP packet before it is
+	  sent over the wire. The machine at the other end of the PPP link
+	  (usually your ISP) has to support the BSD-Compress compression
+	  method as well for this to be useful. Even if they don't support it,
+	  it is safe to say Y here.
+
+	  The PPP Deflate compression method ("PPP Deflate compression",
+	  above) is preferable to BSD-Compress, because it compresses better
+	  and is patent-free.
+
+	  Note that the BSD compression code will always be compiled as a
+	  module; it is called bsd_comp.o and will show up in the directory
+	  modules once you have said "make modules". If unsure, say N.
+
+config PPPOE
+	tristate "PPP over Ethernet (EXPERIMENTAL)"
+	depends on EXPERIMENTAL && PPP
+	help
+	  Support for PPP over Ethernet.
+
+	  This driver requires a specially patched pppd daemon.  The patch to
+	  pppd, along with binaries of a patched pppd package can be found at:
+	  <http://www.shoshin.uwaterloo.ca/~mostrows/>.
+
+config PPPOATM
+	tristate "PPP over ATM"
+	depends on ATM && PPP
+	help
+	  Support PPP (Point to Point Protocol) encapsulated in ATM frames.
+	  This implementation does not yet comply with section 8 of RFC2364,
+	  which can lead to bad results if the ATM peer loses state and
+	  changes its encapsulation unilaterally.
+
+config SLIP
+	tristate "SLIP (serial line) support"
+	depends on NETDEVICES
+	---help---
+	  Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
+	  connect to your Internet service provider or to connect to some
+	  other local Unix box or if you want to configure your Linux box as a
+	  Slip/CSlip server for other people to dial in. SLIP (Serial Line
+	  Internet Protocol) is a protocol used to send Internet traffic over
+	  serial connections such as telephone lines or null modem cables;
+	  nowadays, the protocol PPP is more commonly used for this same
+	  purpose.
+
+	  Normally, your access provider has to support SLIP in order for you
+	  to be able to use it, but there is now a SLIP emulator called SLiRP
+	  around (available from
+	  <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
+	  allows you to use SLIP over a regular dial up shell connection. If
+	  you plan to use SLiRP, make sure to say Y to CSLIP, below. The
+	  NET-3-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>, explains how to
+	  configure SLIP. Note that you don't need this option if you just
+	  want to run term (term is a program which gives you almost full
+	  Internet connectivity if you have a regular dial up shell account on
+	  some Internet connected Unix computer. Read
+	  <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
+	  support will enlarge your kernel by about 4 KB. If unsure, say N.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>. The module will be
+	  called slip.o.
+
+config SLIP_COMPRESSED
+	bool "CSLIP compressed headers"
+	depends on SLIP
+	---help---
+	  This protocol is faster than SLIP because it uses compression on the
+	  TCP/IP headers (not on the data itself), but it has to be supported
+	  on both ends. Ask your access provider if you are not sure and
+	  answer Y, just in case. You will still be able to use plain SLIP. If
+	  you plan to use SLiRP, the SLIP emulator (available from
+	  <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
+	  allows you to use SLIP over a regular dial up shell connection, you
+	  definitely want to say Y here. The NET-3-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>, explains how to configure
+	  CSLIP. This won't enlarge your kernel.
+
+config SLIP_SMART
+	bool "Keepalive and linefill"
+	depends on SLIP
+	help
+	  Adds additional capabilities to the SLIP driver to support the
+	  RELCOM line fill and keepalive monitoring. Ideal on poor quality
+	  analogue lines.
+
+config SLIP_MODE_SLIP6
+	bool "Six bit SLIP encapsulation"
+	depends on SLIP
+	help
+	  Just occasionally you may need to run IP over hostile serial
+	  networks that don't pass all control characters or are only seven
+	  bit. Saying Y here adds an extra mode you can use with SLIP:
+	  "slip6". In this mode, SLIP will only send normal ASCII symbols over
+	  the serial device. Naturally, this has to be supported at the other
+	  end of the link as well. It's good enough, for example, to run IP
+	  over the async ports of a Camtec JNT Pad. If unsure, say N.
+
+
+menu "Wireless LAN (non-hamradio)"
+	depends on NETDEVICES
+
+config NET_RADIO
+	bool "Wireless LAN (non-hamradio)"
+	---help---
+	  Support for wireless LANs and everything having to do with radio,
+	  but not with amateur radio or FM broadcasting.
+
+	  Saying Y here also enables the Wireless Extensions (creates
+	  /proc/net/wireless and enables ifconfig access). The Wireless
+	  Extension is a generic API allowing a driver to expose to the user
+	  space configuration and statistics specific to common Wireless LANs.
+	  The beauty of it is that a single set of tool can support all the
+	  variations of Wireless LANs, regardless of their type (as long as
+	  the driver supports Wireless Extension). Another advantage is that
+	  these parameters may be changed on the fly without restarting the
+	  driver (or Linux). If you wish to use Wireless Extensions with
+	  wireless PCMCIA (PC-) cards, you need to say Y here; you can fetch
+	  the tools from
+	  <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
+
+	  Some user-level drivers for scarab devices which don't require
+	  special kernel support are available from
+	  <ftp://shadow.cabi.net/pub/Linux/>.
+
+config STRIP
+	tristate "STRIP (Metricom starmode radio IP)"
+	depends on NET_RADIO && INET
+	---help---
+	  Say Y if you have a Metricom radio and intend to use Starmode Radio
+	  IP. STRIP is a radio protocol developed for the MosquitoNet project
+	  (on the WWW at <http://mosquitonet.stanford.edu/>) to send Internet
+	  traffic using Metricom radios.  Metricom radios are small, battery
+	  powered, 100kbit/sec packet radio transceivers, about the size and
+	  weight of a cellular telephone. (You may also have heard them called
+	  "Metricom modems" but we avoid the term "modem" because it misleads
+	  many people into thinking that you can plug a Metricom modem into a
+	  phone line and use it as a modem.)
+
+	  You can use STRIP on any Linux machine with a serial port, although
+	  it is obviously most useful for people with laptop computers. If you
+	  think you might get a Metricom radio in the future, there is no harm
+	  in saying Y to STRIP now, except that it makes the kernel a bit
+	  bigger.
+
+	  You can also compile this as a module ( = code which can be inserted
+	  in and removed from the running kernel whenever you want), say M
+	  here and read <file:Documentation/modules.txt>.  The module will be
+	  called strip.o.
+
+config ARLAN
+	tristate "Aironet Arlan 655 & IC2200 DS support"
+	depends on NET_RADIO
+	---help---
+	  Aironet makes Arlan, a class of wireless LAN adapters. These use the
+	  www.Telxon.com chip, which is also used on several similar cards.
+	  This driver is tested on the 655 and IC2200 series cards. Look at
+	  <http://www.ylenurme.ee/~elmer/655/> for the latest information.
+
+	  The driver is built as two modules, arlan and arlan-proc. The latter
+	  is the /proc interface and is not needed most of time.
+
+	  On some computers the card ends up in non-valid state after some
+	  time. Use a ping-reset script to clear it.
+
+config AIRONET4500
+	tristate "Aironet 4500/4800 series adapters"
+	depends on NET_RADIO
+	---help---
+	  www.aironet.com (recently bought by Cisco) makes these 802.11 DS
+	  adapters.  Driver by Elmer Joandi (elmer@ylenurme.ee).
+
+	  Say Y here if you have such an adapter, and then say Y below to
+	  the option that applies to your particular type of card (PCI, ISA,
+	  or PCMCIA).
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called aironet4500_core.o. If you want to
+	  compile it as a module, say M here and read
+	  <file:Documentation/modules.txt> as well as
+	  <file:Documentation/networking/net-modules.txt>.
+
+	  quick config parameters:
+	  	SSID=tsunami - "The Password"
+	  	adhoc=1  	there are no Access Points around
+	  	master=1 	Adhoc master (the one who creates network
+	  sync)
+	  	slave=1		Adhoc slave (btw, it is still forming own net
+	  			sometimes, and has problems with firmware...
+	  			change IbssJoinNetTimeout from /proc...)
+	  	channel=1..? 	meaningful in adhoc mode
+
+	  If you have problems with screwing up card, both_bap_lock=1 is a
+	  conservative value (performance hit 15%).
+
+	  All other parameters can be set via the proc interface.
+
+config AIRONET4500_NONCS
+	tristate "Aironet 4500/4800 ISA/PCI/PNP/365 support "
+	depends on AIRONET4500
+	help
+	  If you have an ISA, PCI or PCMCIA Aironet 4500/4800 wireless LAN
+	  card, say Y here, and then also to the options below that apply
+	  to you.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called aironet4500_card.o.  If you want to
+	  compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.
+
+config AIRONET4500_PNP
+	bool "Aironet 4500/4800 PNP support "
+	depends on AIRONET4500_NONCS
+	help
+	  If you have an ISA Aironet 4500/4800 card which you want to use in
+	  PnP (Plug and Play) mode, say Y here. This is the recommended mode
+	  for ISA cards. Remember however to enable the PnP jumper on the
+	  board if you say Y here.
+
+config AIRONET4500_PCI
+	bool "Aironet 4500/4800 PCI support "
+	depends on AIRONET4500_NONCS && PCI
+	help
+	  If you have an PCI Aironet 4500/4800 card, say Y here.
+
+config AIRONET4500_ISA
+	bool "Aironet 4500/4800 ISA broken support (EXPERIMENTAL)"
+	depends on AIRONET4500_NONCS && EXPERIMENTAL
+	help
+	  If you have an ISA Aironet 4500/4800 card which you want to run in
+	  non-PnP mode, say Y here. This is not recommended and does not work
+	  correctly at this point. Say N.
+
+config AIRONET4500_I365
+	bool "Aironet 4500/4800 I365 broken support (EXPERIMENTAL)"
+	depends on AIRONET4500_NONCS && EXPERIMENTAL
+	help
+	  If you have a PCMCIA Aironet 4500/4800 card which you want to use
+	  without the standard PCMCIA cardservices provided by the pcmcia-cs
+	  package, say Y here. This is not recommended, so say N.
+
+config AIRONET4500_PROC
+	tristate "Aironet 4500/4800 PROC interface "
+	depends on AIRONET4500 && m
+	---help---
+	  If you say Y here (and to the "/proc file system" below), you will
+	  be able to configure your Aironet card via the
+	  /proc/sys/aironet4500 interface.
+
+	  Additional info: look in <file:drivers/net/aironet4500_rid.c>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called aironet4500_proc.o. If you want to
+	  compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.
+
+	  NOTE: the proc interface uses a lot of memory, so it is recommended
+	  to compile it as a module and remove the module after
+	  configuration.
+
+# New directory for Wireless LAN devices - cards above will move there
+source "drivers/net/wireless/Kconfig"
+
+endmenu
+
+source "drivers/net/tokenring/Kconfig"
+
+config NET_FC
+	bool "Fibre Channel driver support"
+	depends on NETDEVICES
+	help
+	  Fibre Channel is a high speed serial protocol mainly used to connect
+	  large storage devices to the computer; it is compatible with and
+	  intended to replace SCSI.
+
+	  If you intend to use Fibre Channel, you need to have a Fibre channel
+	  adaptor card in your computer; say Y here and to the driver for your
+	  adaptor below. You also should have said Y to "SCSI support" and
+	  "SCSI generic support".
+
+config IPHASE5526
+	tristate "Interphase 5526 Tachyon chipset based adapter support"
+	depends on NET_FC && SCSI && PCI
+	help
+	  Say Y here if you have a Fibre Channel adaptor of this kind.
+
+	  The driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called iph5526.o. For general information about
+	  modules read <file:Documentation/modules.txt>.
+
+config RCPCI
+	tristate "Red Creek Hardware VPN (EXPERIMENTAL)"
+	depends on NETDEVICES && EXPERIMENTAL && PCI
+	help
+	  This is a driver for hardware which provides a Virtual Private
+	  Network (VPN). Say Y if you have it.
+
+	  This code is also available as a module called rcpci.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config SHAPER
+	tristate "Traffic Shaper (EXPERIMENTAL)"
+	depends on NETDEVICES && EXPERIMENTAL
+	---help---
+	  The traffic shaper is a virtual network device that allows you to
+	  limit the rate of outgoing data flow over some other network device.
+	  The traffic that you want to slow down can then be routed through
+	  these virtual devices. See
+	  <file:Documentation/networking/shaper.txt> for more information.
+
+	  An alternative to this traffic shaper is the experimental
+	  Class-Based Queueing (CBQ) scheduling support which you get if you
+	  say Y to "QoS and/or fair queueing" above.
+
+	  To set up and configure shaper devices, you need the shapecfg
+	  program, available from <ftp://shadow.cabi.net/pub/Linux/> in the
+	  shaper package.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called shaper.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.  If
+	  unsure, say N.
+
+source "drivers/net/wan/Kconfig"
+
+source "drivers/net/pcmcia/Kconfig"
+

drivers/net/appletalk/Kconfig

+#
+# Appletalk driver configuration
+#
+config DEV_APPLETALK
+	bool "Appletalk interfaces support"
+	depends on ATALK
+	help
+	  AppleTalk is the protocol that Apple computers can use to communicate
+	  on a network.  If your Linux box is connected to such a network, and wish
+	  to do IP over it, or you have a LocalTalk card and wish to use it to
+	  connect to the AppleTalk network, say Y.
+	  
+
+config LTPC
+	tristate "Apple/Farallon LocalTalk PC support"
+	depends on DEV_APPLETALK
+	help
+	  This allows you to use the AppleTalk PC card to connect to LocalTalk
+	  networks. The card is also known as the Farallon PhoneNet PC card.
+	  If you are in doubt, this card is the one with the 65C02 chip on it.
+	  You also need version 1.3.3 or later of the netatalk package.
+	  This driver is experimental, which means that it may not work.
+	  See the file <file:Documentation/networking/ltpc.txt>.
+
+config COPS
+	tristate "COPS LocalTalk PC support"
+	depends on DEV_APPLETALK
+	help
+	  This allows you to use COPS AppleTalk cards to connect to LocalTalk
+	  networks. You also need version 1.3.3 or later of the netatalk
+	  package. This driver is experimental, which means that it may not
+	  work. This driver will only work if you choose "AppleTalk DDP"
+	  networking support, above.
+	  Please read the file <file:Documentation/networking/cops.txt>.
+
+config COPS_DAYNA
+	bool "Dayna firmware support"
+	depends on COPS
+	help
+	  Support COPS compatible cards with Dayna style firmware (Dayna
+	  DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
+	  III, Farallon PhoneNET PC II).
+
+config COPS_TANGENT
+	bool "Tangent firmware support"
+	depends on COPS
+	help
+	  Support COPS compatible cards with Tangent style firmware (Tangent
+	  ATB_II, Novell NL-1000, Daystar Digital LT-200.
+
+config IPDDP
+	tristate "Appletalk-IP driver support"
+	depends on DEV_APPLETALK && ATALK
+	---help---
+	  This allows IP networking for users who only have AppleTalk
+	  networking available. This feature is experimental. With this
+	  driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
+	  box is stuck on an AppleTalk only network) or decapsulate (e.g. if
+	  you want your Linux box to act as an Internet gateway for a zoo of
+	  AppleTalk connected Macs). Please see the file
+	  <file:Documentation/networking/ipddp.txt> for more information.
+
+	  If you say Y here, the AppleTalk-IP support will be compiled into
+	  the kernel. In this case, you can either use encapsulation or
+	  decapsulation, but not both. With the following two questions, you
+	  decide which one you want.
+
+	  If you say M here, the AppleTalk-IP support will be compiled as a
+	  module ( = code which can be inserted in and removed from the
+	  running kernel whenever you want, read
+	  <file:Documentation/modules.txt>).  The module is called ipddp.o.
+	  In this case, you will be able to use both encapsulation and
+	  decapsulation simultaneously, by loading two copies of the module
+	  and specifying different values for the module option ipddp_mode.
+
+config IPDDP_ENCAP
+	bool "IP to Appletalk-IP Encapsulation support"
+	depends on IPDDP
+	help
+	  If you say Y here, the AppleTalk-IP code will be able to encapsulate
+	  IP packets inside AppleTalk frames; this is useful if your Linux box
+	  is stuck on an AppleTalk network (which hopefully contains a
+	  decapsulator somewhere). Please see
+	  <file:Documentation/networking/ipddp.txt> for more information. If
+	  you said Y to "AppleTalk-IP driver support" above and you say Y
+	  here, then you cannot say Y to "AppleTalk-IP to IP Decapsulation
+	  support", below.
+
+config IPDDP_DECAP
+	bool "Appletalk-IP to IP Decapsulation support"
+	depends on IPDDP
+	help
+	  If you say Y here, the AppleTalk-IP code will be able to decapsulate
+	  AppleTalk-IP frames to IP packets; this is useful if you want your
+	  Linux box to act as an Internet gateway for an AppleTalk network.
+	  Please see <file:Documentation/networking/ipddp.txt> for more
+	  information.  If you said Y to "AppleTalk-IP driver support" above
+	  and you say Y here, then you cannot say Y to "IP to AppleTalk-IP
+	  Encapsulation support", above.
+

drivers/net/arcnet/Kconfig

+#
+# Arcnet configuration
+#
+
+menu "ARCnet devices"
+	depends on NETDEVICES
+
+config ARCNET
+	tristate "ARCnet support"
+	---help---
+	  If you have a network card of this type, say Y and check out the
+	  (arguably) beautiful poetry in
+	  <file:Documentation/networking/arcnet.txt>.
+
+	  You need both this driver, and the driver for the particular ARCnet
+	  chipset of your card. If you don't know, then it's probably a
+	  COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
+	  support" below.
+
+	  You might also want to have a look at the Ethernet-HOWTO, available
+	  from <http://www.linuxdoc.org/docs.html#howto>(even though ARCnet
+	  is not really Ethernet).
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called arcnet.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config ARCNET_1201
+	tristate "Enable standard ARCNet packet format (RFC 1201)"
+	depends on ARCNET
+	help
+	  This allows you to use RFC1201 with your ARCnet card via the virtual
+	  arc0 device.  You need to say Y here to communicate with
+	  industry-standard RFC1201 implementations, like the arcether.com
+	  packet driver or most DOS/Windows ODI drivers.  Please read the
+	  ARCnet documentation in <file:Documentation/networking/arcnet.txt>
+	  for more information about using arc0.
+
+config ARCNET_1051
+	tristate "Enable old ARCNet packet format (RFC 1051)"
+	depends on ARCNET
+	---help---
+	  This allows you to use RFC1051 with your ARCnet card via the virtual
+	  arc0s device. You only need arc0s if you want to talk to ARCnet
+	  software complying with the "old" standard, specifically, the DOS
+	  arcnet.com packet driver, Amigas running AmiTCP, and some variants
+	  of NetBSD. You do not need to say Y here to communicate with
+	  industry-standard RFC1201 implementations, like the arcether.com
+	  packet driver or most DOS/Windows ODI drivers. RFC1201 is included
+	  automatically as the arc0 device. Please read the ARCnet
+	  documentation in <file:Documentation/networking/arcnet.txt> for more
+	  information about using arc0e and arc0s.
+
+config ARCNET_RAW
+	tristate "Enable raw mode packet interface"
+	depends on ARCNET
+	help
+	  ARCnet "raw mode" packet encapsulation, no soft headers.  Unlikely
+	  to work unless talking to a copy of the same Linux arcnet driver,
+	  but perhaps marginally faster in that case.
+
+config ARCNET_COM90xx
+	tristate "ARCnet COM90xx (normal) chipset driver"
+	depends on ARCNET
+	help
+	  This is the chipset driver for the standard COM90xx cards. If you
+	  have always used the old ARCnet driver without knowing what type of
+	  card you had, this is probably the one for you.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called com90xx.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config ARCNET_COM90xxIO
+	tristate "ARCnet COM90xx (IO mapped) chipset driver"
+	depends on ARCNET
+	---help---
+	  This is the chipset driver for the COM90xx cards, using them in
+	  IO-mapped mode instead of memory-mapped mode. This is slower than
+	  the normal driver. Only use it if your card doesn't support shared
+	  memory.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called com90io.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config ARCNET_RIM_I
+	tristate "ARCnet COM90xx (RIM I) chipset driver"
+	depends on ARCNET
+	---help---
+	  This is yet another chipset driver for the COM90xx cards, but this
+	  time only using memory-mapped mode, and no IO ports at all. This
+	  driver is completely untested, so if you have one of these cards,
+	  please mail dwmw2@infradead.org, especially if it works!
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you
+	  want). The module will be called arc-rimi.o.  If you want to compile
+	  it as a module, say M here and read <file:Documentation/modules.txt>
+	  as  well as <file:Documentation/networking/net-modules.txt>.
+
+config ARCNET_COM20020
+	tristate "ARCnet COM20020 chipset driver"
+	depends on ARCNET
+	help
+	  This is the driver for the new COM20020 chipset. It supports such
+	  things as promiscuous mode, so packet sniffing is possible, and
+	  extra diagnostic information.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called com20020.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt> as
+	  well as <file:Documentation/networking/net-modules.txt>.
+
+config ARCNET_COM20020_ISA
+	tristate "Support for COM20020 on ISA"
+	depends on ARCNET_COM20020 && ISA
+
+config ARCNET_COM20020_PCI
+	tristate "Support for COM20020 on PCI"
+	depends on ARCNET_COM20020 && PCI
+
+endmenu
+

drivers/net/hamradio/Kconfig

+config MKISS
+	tristate "Serial port KISS driver"
+	depends on AX25
+	---help---
+	  KISS is a protocol used for the exchange of data between a computer
+	  and a Terminal Node Controller (a small embedded system commonly
+	  used for networking over AX.25 amateur radio connections; it
+	  connects the computer's serial port with the radio's microphone
+	  input and speaker output).
+
+	  Although KISS is less advanced than the 6pack protocol, it has
+	  the advantage that it is already supported by most modern TNCs
+	  without the need for a firmware upgrade.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called mkiss.o.
+
+config 6PACK
+	tristate "Serial port 6PACK driver"
+	depends on AX25
+	---help---
+	  6pack is a transmission protocol for the data exchange between your
+	  PC and your TNC (the Terminal Node Controller acts as a kind of
+	  modem connecting your computer's serial port to your radio's
+	  microphone input and speaker output). This protocol can be used as
+	  an alternative to KISS for networking over AX.25 amateur radio
+	  connections, but it has some extended functionality.
+
+	  Note that this driver is still experimental and might cause
+	  problems. For details about the features and the usage of the
+	  driver, read <file:Documentation/networking/6pack.txt>.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called 6pack.o.
+
+config BPQETHER
+	tristate "BPQ Ethernet driver"
+	depends on AX25
+	help
+	  AX.25 is the protocol used for computer communication over amateur
+	  radio. If you say Y here, you will be able to send and receive AX.25
+	  traffic over Ethernet (also called "BPQ AX.25"), which could be
+	  useful if some other computer on your local network has a direct
+	  amateur radio connection.
+
+config DMASCC
+	tristate "High-speed (DMA) SCC driver for AX.25"
+	depends on ISA && AX25
+	---help---
+	  This is a driver for high-speed SCC boards, i.e. those supporting
+	  DMA on one port. You usually use those boards to connect your
+	  computer to an amateur radio modem (such as the WA4DSY 56kbps
+	  modem), in order to send and receive AX.25 packet radio network
+	  traffic.
+
+	  Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
+	  PackeTwin, and S5SCC/DMA boards. They are detected automatically.
+	  If you have one of these cards, say Y here and read the AX25-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver can operate multiple boards simultaneously. If you
+	  compile it as a module (by saying M instead of Y), it will be called
+	  dmascc.o. If you don't pass any parameter to the driver, all
+	  possible I/O addresses are probed. This could irritate other devices
+	  that are currently not in use. You may specify the list of addresses
+	  to be probed by "dmascc=addr1,addr2,..." (when compiled into the
+	  kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
+	  network interfaces will be called dmascc0 and dmascc1 for the board
+	  detected first, dmascc2 and dmascc3 for the second one, and so on.
+
+	  Before you configure each interface with ifconfig, you MUST set
+	  certain parameters, such as channel access timing, clock mode, and
+	  DMA channel. This is accomplished with a small utility program,
+	  dmascc_cfg, available at
+	  <http://www.nt.tuwien.ac.at/~kkudielk/Linux/>. Please be sure to get
+	  at least version 1.27 of dmascc_cfg, as older versions will not
+	  work with the current driver.
+
+config SCC
+	tristate "Z8530 SCC driver"
+	depends on ISA && AX25
+	---help---
+	  These cards are used to connect your Linux box to an amateur radio
+	  in order to communicate with other computers. If you want to use
+	  this, read <file:Documentation/networking/z8530drv.txt> and the
+	  AX25-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>. Also make sure to say Y
+	  to "Amateur Radio AX.25 Level 2" support.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called scc.o.
+
+config SCC_DELAY
+	bool "additional delay for PA0HZP OptoSCC compatible boards"
+	depends on SCC
+	help
+	  Say Y here if you experience problems with the SCC driver not
+	  working properly; please read
+	  <file:Documentation/networking/z8530drv.txt> for details. If unsure,
+	  say N.
+
+config SCC_TRXECHO
+	bool "support for TRX that feedback the tx signal to rx"
+	depends on SCC
+	help
+	  Some transmitters feed the transmitted signal back to the receive
+	  line.  Say Y here to foil this by explicitly disabling the receiver
+	  during data transmission.  If in doubt, say Y.
+
+config BAYCOM_SER_FDX
+	tristate "BAYCOM ser12 fullduplex driver for AX.25"
+	depends on AX25
+	---help---
+	  This is one of two drivers for Baycom style simple amateur radio
+	  modems that connect to a serial interface. The driver supports the
+	  ser12 design in full-duplex mode. In addition, it allows the
+	  baudrate to be set between 300 and 4800 baud (however not all modems
+	  support all baudrates). This is the preferred driver. The next
+	  driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old
+	  driver and still provided in case this driver does not work with
+	  your serial interface chip. To configure the driver, use the sethdlc
+	  utility available in the standard ax25 utilities package. For
+	  information on the modems, see <http://www.baycom.de/> and
+	  <file:Documentation/networking/baycom.txt>.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called baycom_ser_fdx.o.
+
+config BAYCOM_SER_HDX
+	tristate "BAYCOM ser12 halfduplex driver for AX.25"
+	depends on AX25
+	---help---
+	  This is one of two drivers for Baycom style simple amateur radio
+	  modems that connect to a serial interface. The driver supports the
+	  ser12 design in full-duplex mode. This is the old driver.  It is
+	  still provided in case your serial interface chip does not work with
+	  the full-duplex driver. This driver is depreciated.  To configure
+	  the driver, use the sethdlc utility available in the standard ax25
+	  utilities package. For information on the modems, see
+	  <http://www.baycom.de/> and
+	  <file:Documentation/networking/baycom.txt>.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called baycom_ser_hdx.o.
+
+config BAYCOM_PAR
+	tristate "BAYCOM picpar and par96 driver for AX.25"
+	depends on PARPORT && AX25
+	---help---
+	  This is a driver for Baycom style simple amateur radio modems that
+	  connect to a parallel interface. The driver supports the picpar and
+	  par96 designs. To configure the driver, use the sethdlc utility
+	  available in the standard ax25 utilities package. For information on
+	  the modems, see <http://www.baycom.de/> and the file
+	  <file:Documentation/networking/baycom.txt>.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called baycom_par.o.
+
+config BAYCOM_EPP
+	tristate "BAYCOM epp driver for AX.25"
+	depends on PARPORT && AX25
+	---help---
+	  This is a driver for Baycom style simple amateur radio modems that
+	  connect to a parallel interface. The driver supports the EPP
+	  designs. To configure the driver, use the sethdlc utility available
+	  in the standard ax25 utilities package. For information on the
+	  modems, see <http://www.baycom.de/> and the file
+	  <file:Documentation/networking/baycom.txt>.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called baycom_par.o.
+
+config SOUNDMODEM
+	tristate "Soundcard modem driver"
+	depends on PARPORT && AX25
+	---help---
+	  This experimental driver allows a standard Sound Blaster or
+	  WindowsSoundSystem compatible sound card to be used as a packet
+	  radio modem (NOT as a telephone modem!), to send digital traffic
+	  over amateur radio.
+
+	  To configure the driver, use the sethdlc, smdiag and smmixer
+	  utilities available in the standard ax25 utilities package. For
+	  information on how to key the transmitter, see
+	  <http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html> and
+	  <file:Documentation/networking/soundmodem.txt>.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  This is
+	  recommended.  The module will be called soundmodem.o.
+
+config SOUNDMODEM_SBC
+	bool "soundmodem support for Soundblaster and compatible cards"
+	depends on SOUNDMODEM
+	help
+	  This option enables the soundmodem driver to use Sound Blaster and
+	  compatible cards. If you have a dual mode card (i.e. a WSS cards
+	  with a Sound Blaster emulation) you should say N here and Y to
+	  "Sound card modem support for WSS and Crystal cards", below, because
+	  this usually results in better performance. This option also
+	  supports SB16/32/64 in full-duplex mode.
+
+config SOUNDMODEM_WSS
+	bool "soundmodem support for WSS and Crystal cards"
+	depends on SOUNDMODEM
+	help
+	  This option enables the soundmodem driver to use WindowsSoundSystem
+	  compatible cards. These cards feature a codec chip from either
+	  Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
+	  Semiconductors (such as CS4248, CS423x). This option also supports
+	  the WSS full-duplex operation which currently works with Crystal
+	  CS423x chips. If you don't need full-duplex operation, do not enable
+	  it to save performance.
+
+config SOUNDMODEM_AFSK1200
+	bool "soundmodem support for 1200 baud AFSK modulation"
+	depends on SOUNDMODEM
+	help
+	  This option enables the soundmodem driver 1200 baud AFSK modem,
+	  compatible to popular modems using TCM3105 or AM7911. The
+	  demodulator requires about 12% of the CPU power of a Pentium 75 CPU
+	  per channel.
+
+config SOUNDMODEM_AFSK2400_7
+	bool "soundmodem support for 2400 baud AFSK modulation (7.3728MHz crystal)"
+	depends on SOUNDMODEM
+	help
+	  This option enables the soundmodem driver 2400 baud AFSK modem,
+	  compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
+	  crystal. Note that the availability of this driver does _not_ imply
+	  that I recommend building such links. It is only here since users
+	  especially in eastern Europe have asked me to do so. In fact this
+	  modulation scheme has many disadvantages, mainly its incompatibility
+	  with many transceiver designs and the fact that the TCM3105 (if
+	  used) is operated widely outside its specifications.
+
+config SOUNDMODEM_AFSK2400_8
+	bool "soundmodem support for 2400 baud AFSK modulation (8MHz crystal)"
+	depends on SOUNDMODEM
+	help
+	  This option enables the soundmodem driver 2400 baud AFSK modem,
+	  compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
+	  Note that the availability of this driver does _not_ imply that I
+	  recommend building such links. It is only here since users
+	  especially in eastern Europe have asked me to do so. In fact this
+	  modulation scheme has many disadvantages, mainly its incompatibility
+	  with many transceiver designs and the fact that the TCM3105 (if
+	  used) is operated widely outside its specifications.
+
+config SOUNDMODEM_AFSK2666
+	bool "soundmodem support for 2666 baud AFSK modulation"
+	depends on SOUNDMODEM
+	help
+	  This option enables the soundmodem driver 2666 baud AFSK modem.
+	  This modem is experimental, and not compatible to anything
+	  else I know of.
+
+config SOUNDMODEM_HAPN4800
+	bool "soundmodem support for 4800 baud HAPN-1 modulation"
+	depends on SOUNDMODEM
+	help
+	  This option enables the soundmodem driver 4800 baud HAPN-1
+	  compatible modem. This modulation seems to be widely used 'down
+	  under' and in the Netherlands. Here, nobody uses it, so I could not
+	  test if it works. It is compatible to itself, however :-)
+
+config SOUNDMODEM_PSK4800
+	bool "soundmodem support for 4800 baud PSK modulation"
+	depends on SOUNDMODEM
+	help
+	  This option enables the soundmodem driver 4800 baud 8PSK modem.
+	  This modem is experimental, and not compatible to anything
+	  else I know of.
+
+config SOUNDMODEM_FSK9600
+	bool "soundmodem support for 9600 baud FSK G3RUH modulation"
+	depends on SOUNDMODEM
+	help
+	  This option enables the soundmodem driver 9600 baud FSK modem,
+	  compatible to the G3RUH standard. The demodulator requires about 4%
+	  of the CPU power of a Pentium 75 CPU per channel. You can say Y to
+	  both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
+	  can only use one protocol at a time, depending on what the other end
+	  can understand).
+
+config YAM
+	tristate "YAM driver for AX.25"
+	depends on AX25
+	help
+	  The YAM is a modem for packet radio which connects to the serial
+	  port and includes some of the functions of a Terminal Node
+	  Controller. If you have one of those, say Y here.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.
+

drivers/net/irda/Kconfig

+
+menu "Infrared-port device drivers"
+	depends on IRDA!=n
+
+comment "SIR device drivers"
+
+config IRTTY_SIR
+	tristate "IrTTY (uses Linux serial driver)"
+	depends on IRDA
+	help
+	  Say Y here if you want to build support for the IrTTY line
+	  discipline.  If you want to compile it as a module (irtty.o), say M
+	  here and read <file:Documentation/modules.txt>.  IrTTY makes it
+	  possible to use Linux's own serial driver for all IrDA ports that
+	  are 16550 compatible.  Most IrDA chips are 16550 compatible so you
+	  should probably say Y to this option.  Using IrTTY will however
+	  limit the speed of the connection to 115200 bps (IrDA SIR mode).
+
+	  If unsure, say Y.
+
+config IRPORT_SIR
+	tristate "IrPORT (IrDA serial driver)"
+	depends on IRDA
+	---help---
+	  Say Y here if you want to build support for the IrPORT IrDA device
+	  driver. If you want to compile it as a module (irport.o), say M here
+	  and read <file:Documentation/modules.txt>.  IrPORT can be used
+	  instead of IrTTY and sometimes this can be better.  One example is
+	  if your IrDA port does not have echo-canceling, which will work OK
+	  with IrPORT since this driver is working in half-duplex mode only.
+	  You don't need to use irattach with IrPORT, but you just insert it
+	  the same way as FIR drivers (insmod irport io=0x3e8 irq=11).  Notice
+	  that IrPORT is a SIR device driver which means that speed is limited
+	  to 115200 bps.
+
+	  If unsure, say Y.
+
+comment "Dongle support"
+
+config DONGLE
+	bool "Serial dongle support"
+	help
+	  Say Y here if you have an infrared device that connects to your
+	  computer's serial port. These devices are called dongles. Then say Y
+	  or M to the driver for your particular dongle below.
+
+	  Note that the answer to this question won't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions about serial dongles.
+
+config ESI_DONGLE
+	tristate "ESI JetEye PC dongle"
+	depends on DONGLE && IRDA
+	help
+	  Say Y here if you want to build support for the Extended Systems
+	  JetEye PC dongle.  If you want to compile it as a module, say M here
+	  and read <file:Documentation/modules.txt>.  The ESI dongle attaches
+	  to the normal 9-pin serial port connector, and can currently only be
+	  used by IrTTY.  To activate support for ESI dongles you will have to
+	  start irattach like this: "irattach -d esi".
+
+config ACTISYS_DONGLE
+	tristate "ACTiSYS IR-220L and IR220L+ dongle"
+	depends on DONGLE && IRDA
+	help
+	  Say Y here if you want to build support for the ACTiSYS IR-220L and
+	  IR220L+ dongles.  If you want to compile it as a module, say M here
+	  and read <file:Documentation/modules.txt>.  The ACTiSYS dongles
+	  attaches to the normal 9-pin serial port connector, and can
+	  currently only be used by IrTTY.  To activate support for ACTiSYS
+	  dongles you will have to start irattach like this:
+	  "irattach -d actisys" or "irattach -d actisys+".
+
+config TEKRAM_DONGLE
+	tristate "Tekram IrMate 210B dongle"
+	depends on DONGLE && IRDA
+	help
+	  Say Y here if you want to build support for the Tekram IrMate 210B
+	  dongle.  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The Tekram dongle attaches to the
+	  normal 9-pin serial port connector, and can currently only be used
+	  by IrTTY.  To activate support for Tekram dongles you will have to
+	  start irattach like this: "irattach -d tekram".
+
+config GIRBIL_DONGLE
+	tristate "Greenwich GIrBIL dongle"
+	depends on DONGLE && IRDA
+	help
+	  Say Y here if you want to build support for the Greenwich GIrBIL
+	  dongle.  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The Greenwich dongle attaches to
+	  the normal 9-pin serial port connector, and can currently only be
+	  used by IrTTY.  To activate support for Greenwich dongles you will
+	  have to insert "irattach -d girbil" in the /etc/irda/drivers script.
+
+config LITELINK_DONGLE
+	tristate "Parallax LiteLink dongle"
+	depends on DONGLE && IRDA
+	help
+	  Say Y here if you want to build support for the Parallax Litelink
+	  dongle.  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The Parallax dongle attaches to
+	  the normal 9-pin serial port connector, and can currently only be
+	  used by IrTTY.  To activate support for Parallax dongles you will
+	  have to start irattach like this "irattach -d litelink".
+
+config MCP2120_DONGLE
+	tristate "Microchip MCP2120"
+	depends on DONGLE && IRDA
+	help
+	  Say Y here if you want to build support for the Microchip MCP2120
+	  dongle.  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The MCP2120 dongle attaches to
+	  the normal 9-pin serial port connector, and can currently only be
+	  used by IrTTY.  To activate support for MCP2120 dongles you will
+	  have to insert "irattach -d mcp2120" in the /etc/irda/drivers script.
+
+	  You must build this dongle yourself.  For more information see:
+	  <http://www.eyetap.org/~tangf/irda_sir_linux.html>
+
+config OLD_BELKIN_DONGLE
+	tristate "Old Belkin dongle"
+	depends on DONGLE && IRDA
+	help
+	  Say Y here if you want to build support for the Adaptec Airport 1000
+	  and 2000 dongles.  If you want to compile it as a module, say M here
+	  and read <file:Documentation/modules.txt>.  The module will be
+	  called old_belkin.o.  Some information is contained in the comments
+	  at the top of <file:drivers/net/irda/old_belkin.c>.
+
+config EP7211_IR
+	tristate "EP7211 I/R support"
+	depends on DONGLE && ARCH_EP7211 && IRDA
+
+config ACT200L_DONGLE
+	tristate "ACTiSYS IR-200L dongle (EXPERIMENTAL)"
+	depends on DONGLE && EXPERIMENTAL && IRDA
+	help
+	  Say Y here if you want to build support for the ACTiSYS IR-200L
+	  dongle. If you want to compile it as a module, say M here and read
+	  Documentation/modules.txt. The ACTiSYS IR-200L dongle attaches to
+	  the normal 9-pin serial port connector, and can currently only be
+	  used by IrTTY. To activate support for ACTiSYS IR-200L dongles
+	  you will have to start irattach like this: "irattach -d act200l".
+
+config MA600_DONGLE
+	tristate "Mobile Action MA600 dongle (EXPERIMENTAL)"
+	depends on DONGLE && EXPERIMENTAL && IRDA
+	---help---
+	  Say Y here if you want to build support for the Mobile Action MA600
+	  dongle.  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The MA600 dongle attaches to
+	  the normal 9-pin serial port connector, and can currently only be
+	  tested on IrCOMM.  To activate support for MA600 dongles you will
+	  have to insert "irattach -d ma600" in the /etc/irda/drivers script.
+	  Note: irutils 0.9.15 requires no modification. irutils 0.9.9 needs
+	  modification. For more information, download the following tar gzip
+	  file.
+
+	  There is a pre-compiled module on
+	  <http://engsvr.ust.hk/~eetwl95/download/ma600-2.4.x.tar.gz>
+
+comment "FIR device drivers"
+
+config USB_IRDA
+	tristate "IrDA USB dongles (EXPERIMENTAL)"
+	depends on IRDA && USB && EXPERIMENTAL
+	---help---
+	  Say Y here if you want to build support for the USB IrDA FIR Dongle
+	  device driver.  If you want to compile it as a module (irda-usb.o),
+	  say M here and read <file:Documentation/modules.txt>.  IrDA-USB
+	  support the various IrDA USB dongles available and most of their
+	  pecularities.  Those dongles plug in the USB port of your computer,
+	  are plug and play, and support SIR and FIR (4Mbps) speeds.  On the
+	  other hand, those dongles tend to be less efficient than a FIR
+	  chipset.
+
+	  Please note that the driver is still experimental.  And of course,
+	  you will need both USB and IrDA support in your kernel...
+
+config NSC_FIR
+	tristate "NSC PC87108/PC87338"
+	depends on IRDA
+	help
+	  Say Y here if you want to build support for the NSC PC87108 and
+	  PC87338 IrDA chipsets.  This driver supports SIR,
+	  MIR and FIR (4Mbps) speeds.
+
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  nsc-ircc.o.
+
+config WINBOND_FIR
+	tristate "Winbond W83977AF (IR)"
+	depends on IRDA
+	help
+	  Say Y here if you want to build IrDA support for the Winbond
+	  W83977AF super-io chipset.  This driver should be used for the IrDA
+	  chipset in the Corel NetWinder.  The driver supports SIR, MIR and
+	  FIR (4Mbps) speeds.
+
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  w83977af_ir.o.
+
+config TOSHIBA_OLD
+	tristate "Toshiba Type-O IR Port (old driver)"
+	depends on IRDA
+	help
+	  Say Y here if you want to build support for the Toshiba Type-O IR
+	  chipset.  This chipset is used by the Toshiba Libretto 100CT, and
+	  many more laptops. This driver is obsolete, will no more be
+	  maintained and will be removed in favor of the new driver.
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.
+	  The module will be called toshoboe.o.
+
+config TOSHIBA_FIR
+	tristate "Toshiba Type-O IR Port"
+	depends on IRDA
+	help
+	  Say Y here if you want to build support for the Toshiba Type-O IR
+	  and Donau oboe chipsets. These chipsets are used by the Toshiba
+	  Libretto 100/110CT, Tecra 8100, Portege 7020 and many more laptops.
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.
+	  The module will be called donauboe.o.
+
+config SMC_IRCC_FIR
+	tristate "SMC IrCC (EXPERIMENTAL)"
+	depends on EXPERIMENTAL && IRDA
+	help
+	  Say Y here if you want to build support for the SMC Infrared
+	  Communications Controller.  It is used in the Fujitsu Lifebook 635t
+	  and Sony PCG-505TX.  If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.  The module will be
+	  called smc-ircc.o.
+
+config ALI_FIR
+	tristate "ALi M5123 FIR (EXPERIMENTAL)"
+	depends on EXPERIMENTAL && IRDA
+	help
+	  Say Y here if you want to build support for the ALi M5123 FIR
+	  Controller.  The ALi M5123 FIR Controller is embedded in ALi M1543C,
+	  M1535, M1535D, M1535+, M1535D Sourth Bridge.  This driver supports
+	  SIR, MIR and FIR (4Mbps) speeds.
+
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  ali-ircc.o.
+
+config VLSI_FIR
+	tristate "VLSI 82C147 SIR/MIR/FIR (EXPERIMENTAL)"
+	depends on EXPERIMENTAL && IRDA
+	help
+	  Say Y here if you want to build support for the VLSI 82C147
+	  PCI-IrDA Controller. This controller is used by the HP OmniBook 800
+	  and 5500 notebooks. The driver provides support for SIR, MIR and
+	  FIR (4Mbps) speeds.
+
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>. The module will be called vlsi_ir.o.
+
+config SA1100_FIR
+	tristate "SA1100 Internal IR"
+	depends on ARCH_SA1100 && IRDA
+
+endmenu
+

drivers/net/pcmcia/Kconfig

+#
+# PCMCIA Network device configuration
+#
+
+menu "PCMCIA network device support"
+	depends on NETDEVICES && HOTPLUG && PCMCIA!=n
+
+config NET_PCMCIA
+	bool "PCMCIA network device support"
+	---help---
+	  Say Y if you would like to include support for any PCMCIA or CardBus
+	  network adapters, then say Y to the driver for your particular card
+	  below.  PCMCIA- or PC-cards are credit-card size devices often used
+	  with laptops computers; CardBus is the newer and faster version of
+	  PCMCIA.
+
+	  To use your PC-cards, you will need supporting software from David
+	  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+	  for location).  You also want to check out the PCMCIA-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If unsure, say N.
+
+config PCMCIA_3C589
+	tristate "3Com 3c589 PCMCIA support"
+	depends on NET_PCMCIA && PCMCIA
+	help
+	  Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA
+	  (PC-card) Ethernet card to your computer.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called 3c589_cs.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>. If
+	  unsure, say N.
+
+config PCMCIA_3C574
+	tristate "3Com 3c574 PCMCIA support"
+	depends on NET_PCMCIA && PCMCIA
+	help
+	  Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA
+	  (PC-card) Fast Ethernet card to your computer.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called 3c574_cs.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.  If
+	  unsure, say N.
+
+config PCMCIA_FMVJ18X
+	tristate "Fujitsu FMV-J18x PCMCIA support"
+	depends on NET_PCMCIA && PCMCIA
+	help
+	  Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible
+	  PCMCIA (PC-card) Ethernet card to your computer.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called fmvj18x_cs.o.  If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+	  If unsure, say N.
+
+config PCMCIA_PCNET
+	tristate "NE2000 compatible PCMCIA support"
+	depends on NET_PCMCIA && PCMCIA
+	help
+	  Say Y here if you intend to attach an NE2000 compatible PCMCIA
+	  (PC-card) Ethernet or Fast Ethernet card to your computer.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called pcnet_cs.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>. If
+	  unsure, say N.
+
+config PCMCIA_NMCLAN
+	tristate "New Media PCMCIA support"
+	depends on NET_PCMCIA && PCMCIA
+	help
+	  Say Y here if you intend to attach a New Media Ethernet or LiveWire
+	  PCMCIA (PC-card) Ethernet card to your computer.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called nmclan_cs.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.  If
+	  unsure, say N.
+
+config PCMCIA_SMC91C92
+	tristate "SMC 91Cxx PCMCIA support"
+	depends on NET_PCMCIA && PCMCIA
+	help
+	  Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
+	  (PC-card) Ethernet or Fast Ethernet card to your computer.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called smc91c92_cs.o.  If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+	  If unsure, say N.
+
+config PCMCIA_XIRC2PS
+	tristate "Xircom 16-bit PCMCIA support"
+	depends on NET_PCMCIA && PCMCIA
+	help
+	  Say Y here if you intend to attach a Xircom 16-bit PCMCIA (PC-card)
+	  Ethernet or Fast Ethernet card to your computer.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called xirc2ps_cs.o.  If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+	  If unsure, say N.
+
+config PCMCIA_AXNET
+	tristate "broken NS8390-cards support"
+	depends on NET_PCMCIA && PCMCIA
+	---help---
+	  Say Y here if you intend to attach an Asix AX88190-based PCMCIA
+	  (PC-card) Fast Ethernet card to your computer.  These cards are
+	  nearly NE2000 compatible but need a separate driver due to a few
+	  misfeatures.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called axnet_cs.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.  If
+	  unsure, say N.
+
+config ARCNET_COM20020_CS
+	tristate "COM20020 ARCnet PCMCIA support"
+	depends on NET_PCMCIA && ARCNET_COM20020 && PCMCIA
+	help
+	  Say Y here if you intend to attach this type of ARCnet PCMCIA card
+	  to your computer.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called com20020_cs.o.  If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+	  If unsure, say N.
+
+config PCMCIA_IBMTR
+	tristate "IBM PCMCIA tokenring adapter support"
+	depends on NET_PCMCIA && IBMTR!=y && TR && PCMCIA
+	help
+	  Say Y here if you intend to attach this type of Token Ring PCMCIA
+	  card to your computer. You then also need to say Y to "Token Ring
+	  driver support".
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ibmtr_cs.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config NET_PCMCIA_RADIO
+	bool "Pcmcia Wireless LAN"
+	depends on NET_PCMCIA
+	help
+	  Say Y here if you would like to use a PCMCIA (PC-card) device to
+	  connect to a wireless local area network. Then say Y to the driver
+	  for your particular card below.
+
+	  To use your PC-cards, you will need supporting software from David
+	  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+	  for location). You also want to check out the PCMCIA-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+config PCMCIA_RAYCS
+	tristate "Aviator/Raytheon 2.4MHz wireless support"
+	depends on NET_PCMCIA_RADIO && PCMCIA
+	---help---
+	  Say Y here if you intend to attach an Aviator/Raytheon PCMCIA
+	  (PC-card) wireless Ethernet networking card to your computer.
+	  Please read the file <file:Documentation/networking/ray_cs.txt> for
+	  details.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ray_cs.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.  If
+	  unsure, say N.
+
+config AIRONET4500_CS
+	tristate "Aironet 4500/4800 PCMCIA support"
+	depends on NET_PCMCIA_RADIO && AIRONET4500 && PCMCIA
+	help
+	  Say Y here if you have a PCMCIA Aironet 4500/4800 card which you
+	  want to use with the standard PCMCIA cardservices provided by the
+	  pcmcia-cs package.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called aironet4500_cs.o. If you want to
+	  compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.
+
+endmenu
+

drivers/net/tokenring/Kconfig

+#
+# Token Ring driver configuration
+#
+
+menu "Token Ring devices"
+	depends on NETDEVICES
+
+# So far, we only have PCI, ISA, and MCA token ring devices
+config TR
+	bool "Token Ring driver support"
+	depends on PCI || ISA || MCA
+	help
+	  Token Ring is IBM's way of communication on a local network; the
+	  rest of the world uses Ethernet. To participate on a Token Ring
+	  network, you need a special Token ring network card. If you are
+	  connected to such a Token Ring network and want to use your Token
+	  Ring card under Linux, say Y here and to the driver for your
+	  particular card below and read the Token-Ring mini-HOWTO, available
+	  from <http://www.linuxdoc.org/docs.html#howto>. Most people can
+	  say N here.
+
+config IBMTR
+	tristate "IBM Tropic chipset based adapter support"
+	depends on TR && (ISA || MCA)
+	---help---
+	  This is support for all IBM Token Ring cards that don't use DMA. If
+	  you have such a beast, say Y and read the Token-Ring mini-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  Warning: this driver will almost definitely fail if more than one
+	  active Token Ring card is present.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ibmtr.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config IBMOL
+	tristate "IBM Olympic chipset PCI adapter support"
+	depends on TR && PCI
+	---help---
+	  This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
+	  Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
+	  Wake On Lan, and PCI 100/16/4 adapters.
+
+	  If you have such an adapter, say Y and read the Token-Ring
+	  mini-HOWTO, available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called olympic.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+	  Also read <file:Documentation/networking/olympic.txt> or check the
+	  Linux Token Ring Project site for the latest information at
+	  <http://www.linuxtr.net/>.
+
+config IBMLS
+	tristate "IBM Lanstreamer chipset PCI adapter support"
+	depends on TR && PCI
+	help
+	  This is support for IBM Lanstreamer PCI Token Ring Cards.
+
+	  If you have such an adapter, say Y and read the Token-Ring
+	  mini-HOWTO, available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a modules ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The modules will be called lanstreamer.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config 3C359
+	tristate "3Com 3C359 Token Link Velocity XL adapter support"
+	depends on TR && PCI
+	---help---
+	  This is support for the 3Com PCI Velocity XL cards, specifically
+	  the 3Com 3C359, please note this is not for the 3C339 cards, you
+	  should use the tms380 driver instead.
+
+	  If you have such an adapter, say Y and read the Token-Ring
+	  mini-HOWTO, available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will will be called 3c359.o. If you want to compile it
+	  as a module, say M here and read Documentation/modules.txt.
+
+	  Also read the file <file:Documentation/networking/3c359.txt> or check the 
+	  Linux Token Ring Project site for the latest information at
+	  <http://www.linuxtr.net>
+
+config TMS380TR
+	tristate "Generic TMS380 Token Ring ISA/PCI adapter support"
+	depends on TR
+	---help---
+	  This driver provides generic support for token ring adapters
+	  based on the Texas Instruments TMS380 series chipsets.  This
+	  includes the SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect
+	  TR4/16(+) PCI (SK-4590), SysKonnect TR4/16 PCI (SK-4591),
+	  Compaq 4/16 PCI, Thomas-Conrad TC4048 4/16 PCI, and several
+	  Madge adapters.  If you say Y here, you will be asked to select
+	  which cards to support below.  If you're using modules, each
+	  class of card will be supported by a separate module.
+
+	  If you have such an adapter and would like to use it, say Y and
+	  read the Token-Ring mini-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  Also read the file <file:Documentation/networking/tms380tr.txt> or
+	  check <http://www.auk.cx/tms380tr/>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called tms380tr.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config TMSPCI
+	tristate "Generic TMS380 PCI support"
+	depends on TR && TMS380TR!=n && PCI
+	---help---
+	  This tms380 module supports generic TMS380-based PCI cards.
+
+	  These cards are known to work:
+	  - Compaq 4/16 TR PCI
+	  - SysKonnect TR4/16 PCI (SK-4590/SK-4591)
+	  - Thomas-Conrad TC4048 PCI 4/16
+	  - 3Com Token Link Velocity
+
+	  This driver is available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called tmspci.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config TMSISA
+	tristate "Generic TMS380 ISA support"
+	depends on TR && TMS380TR!=n && ISA
+	help
+	  This tms380 module supports generic TMS380-based ISA cards.
+
+	  These cards are known to work:
+	  - SysKonnect TR4/16 ISA (SK-4190)
+
+	  This driver is available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called tmsisa.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config ABYSS
+	tristate "Madge Smart 16/4 PCI Mk2 support"
+	depends on TR && TMS380TR!=n && PCI
+	help
+	  This tms380 module supports the Madge Smart 16/4 PCI Mk2
+	  cards (51-02).
+
+	  This driver is available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called abyss.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config MADGEMC
+	tristate "Madge Smart 16/4 Ringnode MicroChannel"
+	depends on TR && TMS380TR!=n && MCA
+	help
+	  This tms380 module supports the Madge Smart 16/4 MC16 and MC32
+	  MicroChannel adapters.
+
+	  This driver is available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called madgemc.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config SMCTR
+	tristate "SMC ISA/MCA adapter support"
+	depends on TR && (ISA || MCA)
+	---help---
+	  This is support for the ISA and MCA SMC Token Ring cards,
+	  specifically SMC TokenCard Elite (8115T) and SMC TokenCard Elite/A
+	  (8115T/A) adapters.
+
+	  If you have such an adapter and would like to use it, say Y or M and
+	  read the Token-Ring mini-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto> and the file
+	  <file:Documentation/networking/smctr.txt>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called smctr.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+endmenu
+

drivers/net/tulip/Kconfig

+#
+# Tulip family network device configuration
+#
+
+menu "Tulip family network device support"
+	depends on NET_ETHERNET && (PCI || EISA || CARDBUS)
+
+config NET_TULIP
+	bool "\"Tulip\" family network device support"
+	help
+	  This selects the "Tulip" family of EISA/PCI network cards.
+
+config DE2104X
+	tristate "Early DECchip Tulip (dc2104x) PCI support (EXPERIMENTAL)"
+	depends on NET_TULIP && PCI && EXPERIMENTAL
+	---help---
+	  This driver is developed for the SMC EtherPower series Ethernet
+	  cards and also works with cards based on the DECchip
+	  21040 (Tulip series) chips.  Some LinkSys PCI cards are
+	  of this type.  (If your card is NOT SMC EtherPower 10/100 PCI
+	  (smc9332dst), you can also try the driver for "Generic DECchip"
+	  cards, above.  However, most people with a network card of this type
+	  will say Y here.) Do read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  More specific
+	  information is contained in
+	  <file:Documentation/DocBook/tulip-user.tmpl>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called tulip.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config TULIP
+	tristate "DECchip Tulip (dc2114x) PCI support"
+	depends on NET_TULIP && PCI
+	---help---
+	  This driver is developed for the SMC EtherPower series Ethernet
+	  cards and also works with cards based on the DECchip 
+	  21040/21041/21140 (Tulip series) chips.  Some LinkSys PCI cards are
+	  of this type.  (If your card is NOT SMC EtherPower 10/100 PCI
+	  (smc9332dst), you can also try the driver for "Generic DECchip"
+	  cards, above.  However, most people with a network card of this type
+	  will say Y here.) Do read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  More specific
+	  information is contained in 
+	  <file:Documentation/networking/tulip.txt>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called tulip.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config TULIP_MWI
+	bool "New bus configuration (EXPERIMENTAL)"
+	depends on TULIP && EXPERIMENTAL
+	help
+	  This configures your Tulip card specifically for the card and
+	  system cache line size type you are using.
+
+	  This is experimental code, not yet tested on many boards.
+
+	  If unsure, say N.
+
+config TULIP_MMIO
+	bool "Use PCI shared mem for NIC registers"
+	depends on TULIP
+	help
+	  Use PCI shared memory for the NIC registers, rather than going through
+	  the Tulip's PIO (programmed I/O ports).  Faster, but could produce
+	  obscure bugs if your mainboard has memory controller timing issues.
+	  If in doubt, say N.
+
+config DE4X5
+	tristate "Generic DECchip & DIGITAL EtherWORKS PCI/EISA"
+	depends on NET_TULIP && (PCI || EISA)
+	---help---
+	  This is support for the DIGITAL series of PCI/EISA Ethernet cards.
+	  These include the DE425, DE434, DE435, DE450 and DE500 models.  If
+	  you have a network card of this type, say Y and read the
+	  Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>. More specific
+	  information is contained in
+	  <file:Documentation/networking/de4x5.txt>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called de4x5.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config WINBOND_840
+	tristate "Winbond W89c840 Ethernet support"
+	depends on NET_TULIP && PCI
+	help
+	  This driver is for the Winbond W89c840 chip.  It also works with 
+	  the TX9882 chip on the Compex RL100-ATX board.
+	  More specific information and updates are available from
+	  <http://www.scyld.com/network/drivers.html>.
+
+config DM9102
+	tristate "Davicom DM910x/DM980x support"
+	depends on NET_TULIP && PCI
+	---help---
+	  This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from
+	  Davicom (<http://www.davicom.com.tw/>).  If you have such a network
+	  (Ethernet) card, say Y.  Some information is contained in the file
+	  <file:Documentation/networking/dmfe.txt>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called dmfe.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+config PCMCIA_XIRCOM
+	tristate "Xircom CardBus support (new driver)"
+	depends on NET_TULIP && CARDBUS
+	---help---
+	  This driver is for the Digital "Tulip" Ethernet CardBus adapters.
+	  It should work with most DEC 21*4*-based chips/ethercards, as well
+	  as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and
+	  ASIX.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called xircom_cb.o.  If you want to compile
+	  it as a module, say M here and read
+	  <file:Documentation/modules.txt>. If unsure, say N.
+
+config PCMCIA_XIRTULIP
+	tristate "Xircom Tulip-like CardBus support (old driver)"
+	depends on NET_TULIP && CARDBUS
+	---help---
+	  This driver is for the Digital "Tulip" Ethernet CardBus adapters.
+	  It should work with most DEC 21*4*-based chips/ethercards, as well
+	  as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and
+	  ASIX.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called xircom_tulip_cb.o.  If you want to compile
+	  it as a module, say M here and read
+	  <file:Documentation/modules.txt>. If unsure, say N.
+
+endmenu
+

drivers/net/wan/Kconfig

+#
+# wan devices configuration
+#
+
+menu "Wan interfaces"
+	depends on NETDEVICES
+
+config WAN
+	bool "Wan interfaces support"
+	---help---
+	  Wide Area Networks (WANs), such as X.25, frame relay and leased
+	  lines, are used to interconnect Local Area Networks (LANs) over vast
+	  distances with data transfer rates significantly higher than those
+	  achievable with commonly used asynchronous modem connections.
+	  Usually, a quite expensive external device called a `WAN router' is
+	  needed to connect to a WAN.
+
+	  As an alternative, a relatively inexpensive WAN interface card can
+	  allow your Linux box to directly connect to a WAN. If you have one
+	  of those cards and wish to use it under Linux, say Y here and also
+	  to the WAN driver for your card, below.
+
+	  If unsure, say N.
+
+# There is no way to detect a comtrol sv11 - force it modular for now.
+config HOSTESS_SV11
+	tristate "Comtrol Hostess SV-11 support"
+	depends on WAN && ISA && m
+	help
+	  This is a network card for low speed synchronous serial links, at
+	  up to 256Kbps. It supports both PPP and Cisco HDLC.
+
+	  At this point, the driver can only be compiled as a module.
+
+# The COSA/SRP driver has not been tested as non-modular yet.
+config COSA
+	tristate "COSA/SRP sync serial boards support"
+	depends on WAN && ISA && m
+	---help---
+	  This is a driver for COSA and SRP synchronous serial boards. These
+	  boards allow to connect synchronous serial devices (for example
+	  base-band modems, or any other device with the X.21, V.24, V.35 or
+	  V.36 interface) to your Linux box. The cards can work as the
+	  character device, synchronous PPP network device, or the Cisco HDLC
+	  network device.
+
+	  To actually use the COSA or SRP board, you will need user-space
+	  utilities for downloading the firmware to the cards and to set them
+	  up. Look at the <http://www.fi.muni.cz/~kas/cosa/> for more
+	  information about the cards (including the pointer to the user-space
+	  utilities). You can also read the comment at the top of the
+	  <file:drivers/net/wan/cosa.c> for details about the cards and the driver
+	  itself.
+
+	  The driver will be compiled as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called cosa.o. For general information about
+	  modules read <file:Documentation/modules.txt>.
+
+#
+# COMX drivers
+#
+config COMX
+	tristate "MultiGate (COMX) synchronous serial boards support"
+	depends on WAN
+	---help---
+	  Say Y if you want to use any board from the MultiGate (COMX) family.
+	  These boards are synchronous serial adapters for the PC,
+	  manufactured by ITConsult-Pro Co, Hungary.
+
+	  Read <file:Documentation/networking/comx.txt> for help on
+	  configuring and using COMX interfaces.  Further info on these cards
+	  can be found at <http://www.itc.hu/> or <info@itc.hu>.
+
+	  You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
+	  use this driver.
+
+	  If you want to compile this as a module, say M and read
+	  <file:Documentation/modules.txt>.  The module will be called comx.o.
+
+config COMX_HW_COMX
+	tristate "Support for COMX/CMX/HiCOMX boards"
+	depends on COMX
+	help
+	  Hardware driver for the 'CMX', 'COMX' and 'HiCOMX' boards from the
+	  MultiGate family. Say Y if you have one of these.
+
+	  You will need additional firmware to use these cards, which are
+	  downloadable from <ftp://ftp.itc.hu/>.
+
+	  If you want to compile this as a module, say M and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  comx-hw-comx.o.
+
+config COMX_HW_LOCOMX
+	tristate "Support for LoCOMX board"
+	depends on COMX
+	help
+	  Hardware driver for the 'LoCOMX' board from the MultiGate family.
+	  Say Y if you have a board like this.
+
+	  If you want to compile this as a module, say M and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  comx-hw-locomx.o.
+
+config COMX_HW_MIXCOM
+	tristate "Support for MixCOM board"
+	depends on COMX
+	---help---
+	  Hardware driver for the 'MixCOM' board from the MultiGate family.
+	  Say Y if you have a board like this.
+
+	  If you want to use the watchdog device on this card, you should
+	  select it in the Watchdog Cards section of the Character Devices
+	  configuration. The ISDN interface of this card is Teles 16.3
+	  compatible, you should enable it in the ISDN configuration menu. The
+	  driver for the flash ROM of this card is available separately on
+	  <ftp://ftp.itc.hu/>.
+
+	  If you want to compile this as a module, say M and read
+	  <file:Documentation/modules.txt>. The module will be called
+	  comx-hw-mixcom.o.
+
+config COMX_HW_MUNICH
+	tristate "Support for MUNICH based boards: SliceCOM, PCICOM (WelCOM)"
+	depends on COMX
+	---help---
+	  Hardware driver for the 'SliceCOM' (channelized E1) and 'PciCOM'
+	  boards (X21) from the MultiGate family.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called comx-hw-munich.o. If you want to compile it
+	  as a module, say M here and read Documentation/modules.txt.
+
+	  Read linux/Documentation/networking/slicecom.txt for help on
+	  configuring and using SliceCOM interfaces. Further info on these cards
+	  can be found at http://www.itc.hu or <info@itc.hu>.
+
+config COMX_PROTO_PPP
+	tristate "Support for HDLC and syncPPP protocols on MultiGate boards"
+	depends on COMX
+	help
+	  Cisco-HDLC and synchronous PPP protocol driver for all MultiGate
+	  boards. Say Y if you want to use either protocol on your MultiGate
+	  boards.
+
+	  If you want to compile this as a module, say M and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  comx-proto-ppp.o.
+
+config COMX_PROTO_LAPB
+	tristate "Support for LAPB protocol on MultiGate boards"
+	depends on WAN && (COMX!=n && LAPB=m && LAPB || LAPB=y && COMX)
+	help
+	  LAPB protocol driver for all MultiGate boards. Say Y if you
+	  want to use this protocol on your MultiGate boards.
+
+	  If you want to compile this as a module, say M and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  comx-proto-lapb.o.
+
+config COMX_PROTO_FR
+	tristate "Support for Frame Relay on MultiGate boards"
+	depends on COMX
+	help
+	  Frame Relay protocol driver for all MultiGate boards. Say Y if you
+	  want to use this protocol on your MultiGate boards.
+
+	  If you want to compile this as a module, say M and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  comx-proto-fr.o.
+
+#
+# The Etinc driver has not been tested as non-modular yet.
+#
+config DSCC4
+	tristate "Etinc PCISYNC serial board support"
+	depends on WAN && m
+	help
+	  This is a driver for Etinc PCISYNC boards based on the Infineon
+	  (ex. Siemens) DSCC4 chipset. It is supposed to work with the four
+	  ports card. Take a look at <http://www.cogenit.fr/dscc4/>
+	  for further informations about the driver and his configuration.
+
+	  The driver will be compiled as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called dscc4.o. For general information about
+	  modules read <file:Documentation/modules.txt>.
+
+#
+# Lan Media's board. Currently 1000, 1200, 5200, 5245
+#
+config LANMEDIA
+	tristate "LanMedia Corp. SSI/V.35, T1/E1, HSSI, T3 boards"
+	depends on WAN
+	---help---
+	  This is a driver for the following Lan Media family of serial
+	  boards.
+
+	  LMC 1000 board allows you to connect synchronous serial devices (for
+	  example base-band modems, or any other device with the X.21, V.24,
+	  V.35 or V.36 interface) to your Linux box.
+
+	  LMC 1200 with on board DSU board allows you to connect your Linux
+	  box dirrectly to a T1 or E1 circuit.
+
+	  LMC 5200 board provides a HSSI interface capable of running up to
+	  52 mbits per second.
+
+	  LMC 5245 board connects directly to a T3 circuit saving the
+	  additional external hardware.
+
+	  To change setting such as syncPPP vs cisco HDLC or clock source you
+	  will need lmcctl.  It is available at <ftp://ftp.lanmedia.com/>.
+
+	  This code is also available as a module called lmc.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+# There is no way to detect a Sealevel board. Force it modular
+config SEALEVEL_4021
+	tristate "Sealevel Systems 4021 support"
+	depends on WAN && m
+	help
+	  This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
+
+	  This driver can only be compiled as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  If you want to do that, say M here. The module will be called
+	  sealevel.o.
+
+config SYNCLINK_SYNCPPP
+	tristate "SyncLink HDLC/SYNCPPP support"
+	depends on WAN
+	help
+	  Enables HDLC/SYNCPPP support for the SyncLink WAN driver.
+	  Normally the SyncLink WAN driver works with the main PPP
+	  driver (ppp.c) and pppd program. HDLC/SYNCPPP support allows use
+	  of the Cisco HDLC/PPP driver (syncppp.c).
+	  The SyncLink WAN driver (in character devices) must also be enabled.
+
+# Generic HDLC
+config HDLC
+	tristate "Generic HDLC layer"
+	depends on WAN
+	help
+	  Say Y to this option if your Linux box contains a WAN card supported
+	  by this driver and you are planning to connect the box to a WAN
+	  ( = Wide Area Network). You will need supporting software from
+	  <http://hq.pm.waw.pl/hdlc/>.
+	  Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame
+	  Relay, synchronous Point-to-Point Protocol (PPP) and X.25.
+
+	  If unsure, say N here.
+
+config HDLC_RAW
+	bool "Raw HDLC support"
+	depends on HDLC
+	help
+	  Say Y to this option if you want generic HDLC driver to support
+	  raw HDLC over WAN (Wide Area Network) connections.
+
+	  If unsure, say N here.
+
+config HDLC_CISCO
+	bool "Cisco HDLC support"
+	depends on HDLC
+	help
+	  Say Y to this option if you want generic HDLC driver to support
+	  Cisco HDLC over WAN (Wide Area Network) connections.
+
+	  If unsure, say N here.
+
+config HDLC_FR
+	bool "Frame Relay support"
+	depends on HDLC
+	help
+	  Say Y to this option if you want generic HDLC driver to support
+	  Frame-Relay protocol over WAN (Wide Area Network) connections.
+
+	  If unsure, say N here.
+
+config HDLC_PPP
+	bool "Synchronous Point-to-Point Protocol (PPP) support"
+	depends on HDLC
+	help
+	  Say Y to this option if you want generic HDLC driver to support
+	  PPP over WAN (Wide Area Network) connections.
+
+	  If unsure, say N here.
+
+config HDLC_X25
+	bool "X.25 protocol support"
+	depends on HDLC && (LAPB=m && HDLC=m || LAPB=y)
+	help
+	  Say Y to this option if you want generic HDLC driver to support
+	  X.25 protocol over WAN (Wide Area Network) connections.
+
+	  If unsure, say N here.
+
+comment "X.25/LAPB support is disabled"
+	depends on WAN && HDLC && (LAPB!=m || HDLC!=m) && LAPB!=y
+
+config PC300
+	tristate "Cyclades-PC300 support (RS-232/V.35, X.21, T1/E1 boards)"
+	depends on HDLC && PCI
+	---help---
+	  This is a driver for the Cyclades-PC300 synchronous communication
+	  boards. These boards provide synchronous serial interfaces to your
+	  Linux box (interfaces currently available are RS-232/V.35, X.21 and
+	  T1/E1). If you wish to support Multilink PPP, please select the
+	  option below this one and read the file README.mlppp provided by PC300
+	  package.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read Documentation/modules.txt. The module will be
+	  called pc300.o.
+
+	  If you haven't heard about it, it's safe to say N.
+
+config PC300_MLPPP
+	bool "Cyclades-PC300 MLPPP support"
+	depends on PC300 && PPP_MULTILINK && PPP_SYNC_TTY && HDLC_PPP
+	help
+	  Say 'Y' to this option if you are planning to use Multilink PPP over the
+	  PC300 synchronous communication boards.
+
+comment "Cyclades-PC300 MLPPP support is disabled."
+	depends on WAN && HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP)
+
+comment "Refer to the file README.mlppp, provided by PC300 package."
+	depends on WAN && HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP)
+
+config N2
+	tristate "SDL RISCom/N2 support"
+	depends on HDLC
+	help
+	  This driver is for RISCom/N2 single or dual channel ISA cards
+	  made by SDL Communications Inc.  If you have such a card,
+	  say Y here and see <http://hq.pm.waw.pl/pub/hdlc/>.
+
+	  Note that N2csu and N2dds cards are not supported by this driver.
+
+	  If unsure, say N here.
+
+config C101
+	tristate "Moxa C101 support"
+	depends on HDLC
+	help
+	  This driver is for C101 SuperSync ISA cards made by Moxa
+	  Technologies Co., Ltd. If you have such a card,
+	  say Y here and see <http://hq.pm.waw.pl/pub/hdlc/>
+
+	  If unsure, say N here.
+
+config FARSYNC
+	tristate "FarSync T-Series support"
+	depends on HDLC
+	---help---
+	  This driver supports the FarSync T-Series X.21 (and V.35/V.24) cards
+	  from FarSite Communications Ltd.
+	  Synchronous communication is supported on all ports at speeds up to
+	  8Mb/s (128K on V.24) using synchronous PPP, Cisco HDLC, raw HDLC,
+	  Frame Relay or X.25/LAPB.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want)
+	  say M here and read <file:Documentation/modules.txt>.
+	  The module will be called farsync.o and if you want the module to be
+	  automatically loaded when the interface is referenced then you
+	  should add "alias hdlcX farsync" to /etc/modules.conf for each
+	  interface, where X is 0, 1, 2, ...
+
+config HDLC_DEBUG_PKT
+	bool "Debug received/transmitted packets"
+	depends on HDLC
+
+config HDLC_DEBUG_HARD_HEADER
+	bool "Debug hard_header routines"
+	depends on HDLC
+
+config HDLC_DEBUG_ECN
+	bool "Debug FECN/BECN conditions"
+	depends on HDLC
+
+config HDLC_DEBUG_RINGS
+	bool "Debug RX/TX packet rings"
+	depends on HDLC
+
+config DLCI
+	tristate "Frame relay DLCI support"
+	depends on WAN
+	---help---
+	  This is support for the frame relay protocol; frame relay is a fast
+	  low-cost way to connect to a remote Internet access provider or to
+	  form a private wide area network. The one physical line from your
+	  box to the local "switch" (i.e. the entry point to the frame relay
+	  network, usually at the phone company) can carry several logical
+	  point-to-point connections to other computers connected to the frame
+	  relay network. For a general explanation of the protocol, check out
+	  <http://www.frforum.com/> on the WWW. To use frame relay, you need
+	  supporting hardware (called FRAD) and certain programs from the
+	  net-tools package as explained in
+	  <file:Documentation/networking/framerelay.txt>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called dlci.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config DLCI_COUNT
+	int "Max open DLCI"
+	depends on DLCI
+	default "24"
+	help
+	  This is the maximal number of logical point-to-point frame relay
+	  connections (the identifiers of which are called DCLIs) that
+	  the driver can handle. The default is probably fine.
+
+config DLCI_MAX
+	int "Max DLCI per device"
+	depends on DLCI
+	default "8"
+	help
+	  You can specify here how many logical point-to-point frame relay
+	  connections (the identifiers of which are called DCLIs) should be
+	  handled by each of your hardware frame relay access devices. Go with
+	  the default.
+
+config SDLA
+	tristate "SDLA (Sangoma S502/S508) support"
+	depends on DLCI
+	help
+	  Say Y here if you need a driver for the Sangoma S502A, S502E, and
+	  S508 Frame Relay Access Devices. These are multi-protocol cards, but
+	  only frame relay is supported by the driver at this time. Please
+	  read <file:Documentation/framerelay.txt>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called sdla.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+# Wan router core.
+config WAN_ROUTER_DRIVERS
+	bool "WAN router drivers"
+	depends on WAN && WAN_ROUTER
+	---help---
+	  If you have a WAN interface card and you want your Linux box to act
+	  as a WAN router, thereby connecting you Local Area Network to the
+	  outside world over the WAN connection, say Y here and then to the
+	  driver for your card below. In addition, you need to say Y to "Wan
+	  Router".
+
+	  You will need the wan-tools package which is available from
+	  <ftp://ftp.sangoma.com/>. Read
+	  <file:Documentation/networking/wan-router.txt> for more information.
+
+	  Note that the answer to this question won't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions about WAN router drivers. If unsure, say N.
+
+config VENDOR_SANGOMA
+	tristate "Sangoma WANPIPE(tm) multiprotocol cards"
+	depends on WAN_ROUTER_DRIVERS && WAN_ROUTER
+	---help---
+	  WANPIPE from Sangoma Technologies Inc. (<http://www.sangoma.com/>)
+	  is a family of intelligent multiprotocol WAN adapters with data
+	  transfer rates up to 4Mbps. They are also known as Synchronous
+	  Data Link Adapters (SDLA) and are designated as S514-PCI or
+	  S508-ISA.  These cards support
+
+	  - X.25, Frame Relay, PPP, Cisco HDLC protocols.
+
+	  - API support for protocols like HDLC (LAPB),
+	  HDLC Streaming, X.25, Frame Relay and BiSync.
+
+	  - Ethernet Bridging over Frame Relay protocol.
+
+	  - MULTILINK PPP
+
+	  - Async PPP (Modem Dialup)
+
+	  If you have one or more of these cards, say M to this option; you
+	  may then also want to read the file
+	  <file:Documentation/networking/wanpipe.txt>.  The next questions
+	  will ask you about the protocols you want the driver to support.
+
+	  The driver will be compiled as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called wanpipe.o.  For general information about
+	  modules read <file:Documentation/modules.txt>.
+
+config WANPIPE_CHDLC
+	bool "WANPIPE Cisco HDLC support"
+	depends on VENDOR_SANGOMA
+	---help---
+	  Say Y to this option if you are planning to connect a WANPIPE card
+	  to a leased line using the Cisco HDLC protocol. This now supports
+	  Dual Port Cisco HDLC on the S514-PCI/S508-ISA cards.
+	  This support also allows user to build applications using the
+	  HDLC streaming API.
+
+	  CHDLC Streaming driver also supports MULTILINK PPP
+	  support that can bind multiple WANPIPE T1 cards into
+	  a single logical channel.
+
+	  If you say  N, the Cisco HDLC support and
+	  HDLC streaming API and MULTILINK PPP will not be
+	  included in the driver.
+
+config WANPIPE_FR
+	bool "WANPIPE Frame Relay support"
+	depends on VENDOR_SANGOMA
+	help
+	  Say Y to this option if you are planning to connect a WANPIPE card
+	  to a frame relay network, or use frame relay API to develope
+	  custom applications over the Frame  Relay protocol.
+	  This feature also contains the Ethernet Bridging over Frame Relay,
+	  where a WANPIPE frame relay link can be directly connected to the
+	  Linux kernel bridge.  If you say N, the frame relay support will
+	  not be included in the driver. The Frame Relay option is
+	  supported on S514-PCI and S508-ISA cards.
+
+config WANPIPE_X25
+	bool "WANPIPE X.25 support"
+	depends on VENDOR_SANGOMA
+	help
+	  Say Y to this option if you are planning to connect a WANPIPE card
+	  to an X.25 network.  Note, this feature also includes the X.25 API
+	  support used to develope custom applications over the X.25 protocol.
+	  If you say N, the X.25 support will not be included in the driver.
+	  The X.25 option is supported on S514-PCI and S508-ISA cards.
+
+config WANPIPE_PPP
+	bool "WANPIPE PPP support"
+	depends on VENDOR_SANGOMA
+	help
+	  Say Y to this option if you are planning to connect a WANPIPE card
+	  to a leased line using Point-to-Point protocol (PPP). If you say N,
+	  the PPP support will not be included in the driver. The PPP option
+	  is supported on S514-PCI/S508-ISA cards.
+
+config WANPIPE_MULTPPP
+	bool "WANPIPE Multi-Port PPP support"
+	depends on VENDOR_SANGOMA
+	help
+	  Say Y to this option if you are planning to connect a WANPIPE card
+	  to a leased line using Point-to-Point protocol (PPP).  Note, the
+	  MultiPort PPP uses the Linux Kernel SyncPPP protocol over the
+	  Sangoma HDLC Streaming adapter.  In this case each Sangoma adapter
+	  port can support an independent PPP connection.  For example, a
+	  single Quad-Port PCI adapter can support up to four independent
+	  PPP links. If you say N,the PPP support will not be included in the
+	  driver.  The PPP option is supported on S514-PCI/S508-ISA cards.
+
+config CYCLADES_SYNC
+	tristate "Cyclom 2X(tm) cards (EXPERIMENTAL)"
+	depends on WAN_ROUTER_DRIVERS
+	---help---
+	  Cyclom 2X from Cyclades Corporation (<http://www.cyclades.com/> and
+	  <http://www.cyclades.com.br/>) is an intelligent multiprotocol WAN
+	  adapter with data transfer rates up to 512 Kbps. These cards support
+	  the X.25 and SNA related protocols. If you have one or more of these
+	  cards, say Y to this option. The next questions will ask you about
+	  the protocols you want the driver to support (for now only X.25 is
+	  supported).
+
+	  While no documentation is available at this time please grab the
+	  wanconfig tarball in
+	  <http://www.conectiva.com.br/~acme/cycsyn-devel/> (with minor changes
+	  to make it compile with the current wanrouter include files; efforts
+	  are being made to use the original package available at
+	  <ftp://ftp.sangoma.com/>).
+
+	  Feel free to contact me or the cycsyn-devel mailing list at
+	  acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
+	  additional details, I hope to have documentation available as soon
+	  as possible. (Cyclades Brazil is writing the Documentation).
+
+	  The driver will be compiled as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called cyclomx.o. For general information about
+	  modules read <file:Documentation/modules.txt>.
+
+config CYCLOMX_X25
+	bool "Cyclom 2X X.25 support (EXPERIMENTAL)"
+	depends on CYCLADES_SYNC
+	help
+	  Say Y to this option if you are planning to connect a Cyclom 2X card
+	  to an X.25 network.
+
+	  If you say N, the X.25 support will not be included in the driver
+	  (saves about 11 KB of kernel memory).
+
+# X.25 network drivers
+config LAPBETHER
+	tristate "LAPB over Ethernet driver (EXPERIMENTAL)"
+	depends on WAN && LAPB && X25
+	---help---
+	  This is a driver for a pseudo device (typically called /dev/lapb0)
+	  which allows you to open an LAPB point-to-point connection to some
+	  other computer on your Ethernet network.  In order to do this, you
+	  need to say Y or M to the driver for your Ethernet card as well as
+	  to "LAPB Data Link Driver".
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called lapbether.o.  If unsure, say N.
+
+config X25_ASY
+	tristate "X.25 async driver (EXPERIMENTAL)"
+	depends on WAN && LAPB && X25
+	---help---
+	  This is a driver for sending and receiving X.25 frames over regular
+	  asynchronous serial lines such as telephone lines equipped with
+	  ordinary modems.  Experts should note that this driver doesn't
+	  currently comply with the asynchronous HDLS framing protocols in
+	  CCITT recommendation X.25.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called x25_asy.o.  If unsure, say N.
+
+config SBNI
+	tristate "Granch SBNI12 Leased Line adapter support"
+	depends on WAN && X86
+	---help---
+	  This is a driver for ISA SBNI12-xx cards which are low cost
+	  alternatives to leased line modems. Say Y if you want to insert
+	  the driver into the kernel or say M to compile it as a module (the
+	  module will be called sbni.o).
+
+	  You can find more information and last versions of drivers and
+	  utilities at <http://www.granch.ru/>. If you have any question you
+	  can send email to sbni@granch.ru.
+
+	  Say N if unsure.
+
+config SBNI_MULTILINE
+	bool "Multiple line feature support"
+	depends on SBNI
+	help
+	  Schedule traffic for some parallel lines, via SBNI12 adapters.
+	  If you have two computers connected with two parallel lines it's
+	  possible to increase transfer rate nearly twice. You should have
+	  a program named 'sbniconfig' to configure adapters.
+
+	  Say N if unsure.
+
+endmenu
+

drivers/net/wireless/Kconfig

+#
+# Wireless LAN device configuration
+#
+comment "Wireless ISA/PCI cards support"
+	depends on NET_RADIO
+
+# Good old obsolete Wavelan.
+config WAVELAN
+	tristate "AT&T/Lucent old WaveLAN & DEC RoamAbout DS ISA support"
+	depends on NET_RADIO
+	---help---
+	  The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
+	  a Radio LAN (wireless Ethernet-like Local Area Network) using the
+	  radio frequencies 900 MHz and 2.4 GHz.
+
+	  This driver support the ISA version of the WaveLAN card.  A separate
+	  driver for the PCMCIA (PC-card) hardware is available in David
+	  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+	  for location).
+
+	  If you want to use an ISA WaveLAN card under Linux, say Y and read
+	  the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>. Some more specific
+	  information is contained in
+	  <file:Documentation/networking/wavelan.txt> and in the source code
+	  <file:drivers/net/wavelan.p.h>.
+
+	  You will also need the wireless tools package available from
+	  <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
+	  Please read the man pages contained therein.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called wavelan.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> as well
+	  as <file:Documentation/networking/net-modules.txt>.
+
+# 802.11b cards
+config AIRO
+	tristate "Cisco/Aironet 34X/35X/4500/4800 ISA and PCI cards"
+	depends on NET_RADIO && (ISA || PCI)
+	---help---
+	  This is the standard Linux driver to support Cisco/Aironet ISA and
+	  PCI 802.11 wireless cards.
+	  It supports the new 802.11b cards from Cisco (Cisco 34X, Cisco 35X
+	  - with or without encryption) as well as card before the Cisco
+	  aquisition (Aironet 4500, Aironet 4800, Aironet 4800B).
+
+	  This driver support both the standard Linux Wireless Extensions
+	  and Cisco proprietary API, so both the Linux Wireless Tools and the
+	  Cisco Linux utilities can be used to configure the card.
+
+	  The driver can be compiled as a module and will be named "airo.o".
+
+config HERMES
+	tristate "Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)"
+	depends on NET_RADIO
+	---help---
+	  A driver for 802.11b wireless cards based based on the "Hermes" or
+	  Intersil HFA384x (Prism 2) MAC controller.  This includes the vast
+	  majority of the PCMCIA 802.11b cards (which are nearly all rebadges)
+	  - except for the Cisco/Aironet cards.  Cards supported include the
+	  Apple Airport (not a PCMCIA card), WavelanIEEE/Orinoco,
+	  Cabletron/EnteraSys Roamabout, ELSA AirLancer, MELCO Buffalo, Avaya,
+	  IBM High Rate Wireless, Farralon Syyline, Samsung MagicLAN, Netgear
+	  MA401, LinkSys WPC-11, D-Link DWL-650, 3Com AirConnect, Intel
+	  PRO/Wireless, and Symbol Spectrum24 High Rate amongst others.
+
+	  This option includes the guts of the driver, but in order to
+	  actually use a card you will also need to enable support for PCMCIA
+	  Hermes cards, PLX9052 based PCI adaptors or the Apple Airport below.
+
+	  You will also very likely also need the Wireless Tools in order to
+	  configure your card and that /etc/pcmcia/wireless.opts works :
+	  <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>
+
+config APPLE_AIRPORT
+	tristate "Apple Airport support (built-in)"
+	depends on ALL_PPC && HERMES
+	help
+	  Say Y here to support the Airport 802.11b wireless Ethernet hardware
+	  built into the Macintosh iBook and other recent PowerPC-based
+	  Macintosh machines. This is essentially a Lucent Orinoco card with 
+	  a non-standard interface
+
+config PLX_HERMES
+	tristate "Hermes in PLX9052 based PCI adaptor support (Netgear MA301 etc.) (EXPERIMENTAL)"
+	depends on PCI && HERMES && EXPERIMENTAL
+	help
+	  Enable support for PCMCIA cards supported by the "Hermes" (aka
+	  orinoco_cs) driver when used in PLX9052 based PCI adaptors.  These
+	  adaptors are not a full PCMCIA controller but act as a more limited
+	  PCI <-> PCMCIA bridge.  Several vendors sell such adaptors so that
+	  802.11b PCMCIA cards can be used in desktop machines.  The Netgear
+	  MA301 is such an adaptor.
+
+	  Support for these adaptors is so far still incomplete and buggy.
+	  You have been warned.
+
+config PCI_HERMES
+	tristate "Prism 2.5 PCI 802.11b adaptor support (EXPERIMENTAL)"
+	depends on PCI && HERMES && EXPERIMENTAL
+	help
+	  Enable support for PCI and mini-PCI 802.11b wireless NICs based on
+	  the Prism 2.5 chipset.  These are true PCI cards, not the 802.11b
+	  PCMCIA cards bundled with PCI<->PCMCIA adaptors which are also
+	  common.  Some of the built-in wireless adaptors in laptops are of
+	  this variety.
+
+# If Pcmcia is compiled in, offer Pcmcia cards...
+comment "Wireless Pcmcia/Cardbus cards support"
+	depends on NET_RADIO && PCMCIA
+
+# Obsolete cards
+config PCMCIA_NETWAVE
+	tristate "Xircom Netwave AirSurfer Pcmcia wireless support"
+	depends on NET_RADIO && PCMCIA
+	help
+	  Say Y here if you intend to attach this type of PCMCIA (PC-card)
+	  wireless Ethernet networking card to your computer.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called netwave_cs.o.  If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+	  If unsure, say N.
+
+config PCMCIA_WAVELAN
+	tristate "AT&T/Lucent old Wavelan Pcmcia wireless support"
+	depends on NET_RADIO && PCMCIA
+	help
+	  Say Y here if you intend to attach an AT&T/Lucent Wavelan PCMCIA
+	  (PC-card) wireless Ethernet networking card to your computer.  This
+	  driver is for the non-IEEE-802.11 Wavelan cards.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called wavelan_cs.o.  If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+	  If unsure, say N.
+
+# 802.11b cards
+config PCMCIA_HERMES
+	tristate "Hermes PCMCIA card support"
+	depends on PCMCIA!=n && HERMES
+	---help---
+	  A driver for "Hermes" chipset based PCMCIA wireless adaptors, such
+	  as the Lucent WavelanIEEE/Orinoco cards and their OEM (Cabletron/
+	  EnteraSys RoamAbout 802.11, ELSA Airlancer, Melco Buffalo and
+	  others).  It should also be usable on various Prism II based cards
+	  such as the Linksys, D-Link and Farallon Skyline.  It should also
+	  work on Symbol cards such as the 3Com AirConnect and Ericsson WLAN.
+
+	  To use your PC-cards, you will need supporting software from David
+	  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+	  for location).  You also want to check out the PCMCIA-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  You will also very likely also need the Wireless Tools in order to
+	  configure your card and that /etc/pcmcia/wireless.opts works:
+	  <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
+
+config AIRO_CS
+	tristate "Cisco/Aironet 34X/35X/4500/4800 PCMCIA cards"
+	depends on NET_RADIO && PCMCIA
+	---help---
+	  This is the standard Linux driver to support Cisco/Aironet PCMCIA
+	  802.11 wireless cards.  This driver is the same as the Aironet
+	  driver part of the Linux Pcmcia package.
+	  It supports the new 802.11b cards from Cisco (Cisco 34X, Cisco 35X
+	  - with or without encryption) as well as card before the Cisco
+	  aquisition (Aironet 4500, Aironet 4800, Aironet 4800B). It also
+	  supports OEM of Cisco such as the DELL TrueMobile 4800 and Xircom
+	  802.11b cards.
+
+	  This driver support both the standard Linux Wireless Extensions
+	  and Cisco proprietary API, so both the Linux Wireless Tools and the
+	  Cisco Linux utilities can be used to configure the card.
+
+	  To use your PC-cards, you will need supporting software from David
+	  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+	  for location).  You also want to check out the PCMCIA-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+# yes, this works even when no drivers are selected
+config NET_WIRELESS
+	bool
+	depends on NET_RADIO && (ISA || PCI || ALL_PPC || PCMCIA)
+	default y
+

drivers/parport/Kconfig

+#
+# For a description of the syntax of this configuration file,
+# see Documentation/kbuild/config-language.txt.
+#
+# Parport configuration.
+#
+
+menu "Parallel port support"
+
+config PARPORT
+	tristate "Parallel port support"
+	---help---
+	  If you want to use devices connected to your machine's parallel port
+	  (the connector at the computer with 25 holes), e.g. printer, ZIP
+	  drive, PLIP link (Parallel Line Internet Protocol is mainly used to
+	  create a mini network by connecting the parallel ports of two local
+	  machines) etc., then you need to say Y here; please read
+	  <file:Documentation/parport.txt> and
+	  <file:drivers/parport/BUGS-parport>.
+
+	  For extensive information about drivers for many devices attaching
+	  to the parallel port see <http://www.torque.net/linux-pp.html> on
+	  the WWW.
+
+	  It is possible to share a single parallel port among several devices
+	  and it is safe to compile all the corresponding drivers into the
+	  kernel.  If you want to compile parallel port support as a module
+	  ( = code which can be inserted in and removed from the running
+	  kernel whenever you want), say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  parport.o.  If you have more than one parallel port and want to
+	  specify which port and IRQ to be used by this driver at module load
+	  time, take a look at <file:Documentation/parport.txt>.
+
+	  If unsure, say Y.
+
+config PARPORT_PC
+	tristate "PC-style hardware"
+	depends on PARPORT
+	---help---
+	  You should say Y here if you have a PC-style parallel port. All IBM
+	  PC compatible computers and some Alphas have PC-style parallel
+	  ports.
+
+	  This code is also available as a module.  If you want to compile it
+	  as a module ( = code which can be inserted in and removed from the
+	  running kernel whenever you want), say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  parport_pc.o.
+
+	  If unsure, say Y.
+
+config PARPORT_PC_CML1
+	tristate
+	depends on PARPORT!=n && PARPORT_PC!=n
+	default PARPORT_PC if SERIAL_8250=y
+	default m if SERIAL_8250=m
+
+config PARPORT_SERIAL
+	tristate "Multi-IO cards (parallel and serial)"
+	depends on SERIAL_8250!=n && PARPORT_PC_CML1
+	help
+	  This adds support for multi-IO PCI cards that have parallel and
+	  serial ports.  You should say Y or M here.  If you say M, the module
+	  will be called parport_serial.o.
+
+config PARPORT_PC_FIFO
+	bool "Use FIFO/DMA if available (EXPERIMENTAL)"
+	depends on PARPORT_PC && EXPERIMENTAL
+	help
+	  Many parallel port chipsets provide hardware that can speed up
+	  printing. Say Y here if you want to take advantage of that.
+
+	  As well as actually having a FIFO, or DMA capability, the kernel
+	  will need to know which IRQ the parallel port has.  By default,
+	  parallel port interrupts will not be used, and so neither will the
+	  FIFO.  See <file:Documentation/parport.txt> to find out how to
+	  specify which IRQ/DMA to use.
+
+config PARPORT_PC_SUPERIO
+	bool "SuperIO chipset support (EXPERIMENTAL)"
+	depends on PARPORT_PC && EXPERIMENTAL
+	help
+	  Saying Y here enables some probes for Super-IO chipsets in order to
+	  find out things like base addresses, IRQ lines and DMA channels.  It
+	  is safe to say N.
+
+config PARPORT_PC_PCMCIA
+	tristate "Support for PCMCIA management for PC-style ports"
+	depends on PARPORT!=n && HOTPLUG && (PCMCIA!=n && PARPORT_PC=m && PARPORT_PC || PARPORT_PC=y && PCMCIA)
+	help
+	  Say Y here if you need PCMCIA support for your PC-style parallel
+	  ports. If unsure, say N.
+
+config PARPORT_ARC
+	tristate "Archimedes hardware"
+	depends on ARM && PARPORT
+
+config PARPORT_AMIGA
+	tristate "Amiga builtin port"
+	depends on AMIGA && PARPORT
+	help
+	  Say Y here if you need support for the parallel port hardware on
+	  Amiga machines. This code is also available as a module (say M),
+	  called parport_amiga.o. If in doubt, saying N is the safe plan.
+
+config PARPORT_MFC3
+	tristate "Multiface III parallel port"
+	depends on AMIGA && ZORRO && PARPORT
+	help
+	  Say Y here if you need parallel port support for the MFC3 card.
+	  This code is also available as a module (say M), called
+	  parport_mfc3.o. If in doubt, saying N is the safe plan.
+
+config PARPORT_ATARI
+	tristate "Atari hardware"
+	depends on ATARI && PARPORT
+	help
+	  Say Y here if you need support for the parallel port hardware on
+	  Atari machines. This code is also available as a module (say M),
+	  called parport_atari.o. If in doubt, saying N is the safe plan.
+
+config PARPORT_GSC
+	tristate "LASI/ASP builtin parallel-port"
+	depends on GSC_LASI && PARPORT
+	help
+	  Say Y here to build in low-level parallel-support for PC-style
+	  hardware integrated in the LASI-Controller (on the GSC Bus) for
+	  HP-PARISC workstations.
+
+config PARPORT_SUNBPP
+	tristate "Sparc hardware (EXPERIMENTAL)"
+	depends on SBUS && EXPERIMENTAL && PARPORT
+	help
+	  This driver provides support for the bidirectional parallel port
+	  found on many Sun machines. Note that many of the newer Ultras
+	  actually have pc style hardware instead.
+
+# If exactly one hardware type is selected then parport will optimise away
+# support for loading any others.  Defeat this if the user is keen.
+config PARPORT_OTHER
+	bool "Support foreign hardware"
+	depends on PARPORT
+	help
+	  Say Y here if you want to be able to load driver modules to support
+	  other non-standard types of parallel ports. This causes a
+	  performance loss, so most people say N.
+
+config PARPORT_1284
+	bool "IEEE 1284 transfer modes"
+	depends on PARPORT
+	help
+	  If you have a printer that supports status readback or device ID, or
+	  want to use a device that uses enhanced parallel port transfer modes
+	  such as EPP and ECP, say Y here to enable advanced IEEE 1284
+	  transfer modes. Also say Y if you want device ID information to
+	  appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
+
+endmenu
+

drivers/pci/Kconfig

+#
+# PCI configuration
+#
+config PCI_NAMES
+	bool "PCI device name database"
+	depends on PCI
+	---help---
+	  By default, the kernel contains a database of all known PCI device
+	  names to make the information in /proc/pci, /proc/ioports and
+	  similar files comprehensible to the user. This database increases
+	  size of the kernel image by about 80KB, but it gets freed after the
+	  system boots up, so it doesn't take up kernel memory. Anyway, if you
+	  are building an installation floppy or kernel for an embedded system
+	  where kernel image size really matters, you can disable this feature
+	  and you'll get device ID numbers instead of names.
+
+	  When in doubt, say Y.
+

drivers/pcmcia/Kconfig

+#
+# PCMCIA bus subsystem configuration
+#
+# Right now the non-CardBus choices are not supported
+# by the integrated kernel driver.
+#
+
+menu "PCMCIA/CardBus support"
+	depends on HOTPLUG
+
+config PCMCIA
+	tristate "PCMCIA/CardBus support"
+	---help---
+	  Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
+	  computer.  These are credit-card size devices such as network cards,
+	  modems or hard drives often used with laptops computers.  There are
+	  actually two varieties of these cards: the older 16 bit PCMCIA cards
+	  and the newer 32 bit CardBus cards.  If you want to use CardBus
+	  cards, you need to say Y here and also to "CardBus support" below.
+
+	  To use your PC-cards, you will need supporting software from David
+	  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+	  for location).  Please also read the PCMCIA-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  When compiled this way, there will be modules called pcmcia_core.o
+	  and ds.o.  If you want to compile it as a module, say M here and
+	  read <file:Documentation/modules.txt>.
+
+config CARDBUS
+	bool "CardBus support"
+	depends on PCMCIA && PCI
+	---help---
+	  CardBus is a bus mastering architecture for PC-cards, which allows
+	  for 32 bit PC-cards (the original PCMCIA standard specifies only
+	  a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
+
+	  This option enables support for CardBus PC Cards, as well as support
+	  for CardBus host bridges.  Virtually all modern PCMCIA bridges are
+	  CardBus compatible.  A "bridge" is the hardware inside your computer
+	  that PCMCIA cards are plugged into.
+
+	  To use your PC-cards, you will need supporting software from David
+	  Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
+	  for location).
+
+	  If unsure, say Y.
+
+config I82092
+	tristate "i82092 compatible bridge support"
+	depends on PCMCIA && PCI
+	help
+	  This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
+	  found in some older laptops and more commonly in evaluation boards for the
+	  chip.
+
+config I82365
+	tristate "i82365 compatible bridge support"
+	depends on PCMCIA
+	help
+	  Say Y here to include support for ISA-bus PCMCIA host bridges that
+	  are register compatible with the Intel i82365.  These are found on
+	  older laptops and ISA-bus card readers for desktop systems.  A
+	  "bridge" is the hardware inside your computer that PCMCIA cards are
+	  plugged into. If unsure, say N.
+
+config TCIC
+	tristate "Databook TCIC host bridge support"
+	depends on PCMCIA
+	help
+	  Say Y here to include support for the Databook TCIC family of PCMCIA
+	  host bridges. These are only found on a handful of old systems.
+	  "Bridge" is the name used for the hardware inside your computer that
+	  PCMCIA cards are plugged into. If unsure, say N.
+
+config HD64465_PCMCIA
+	tristate "HD64465 host bridge support"
+	depends on HD64465 && PCMCIA
+
+config PCMCIA_SA1100
+	tristate "SA1100 support"
+	depends on ARM && ARCH_SA1100 && PCMCIA
+
+config PCMCIA_SA1111
+	tristate "SA1111 support"
+	depends on PCMCIA_SA1100 && SA1111
+
+endmenu
+

drivers/pnp/Kconfig

+#
+# Plug and Play configuration
+#
+
+menu "Plug and Play configuration"
+
+config PNP
+	bool "Plug and Play support"
+	---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.
+
+config PNP_NAMES
+	bool "Plug and Play device name database"
+	depends on PNP
+	help
+	  Select Y if you want the Plug and Play Layer to keep a database of
+	  human readable names for your PnP devices.  It will increase the size
+	  of the kernel image by around 5 KB and use 16 KB of system memory.
+
+	  If unsure, say Y.
+
+config PNP_DEBUG
+	bool "PnP Debug Messages"
+	depends on PNP
+	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"
+	depends on PNP
+
+config ISAPNP
+	bool "ISA Plug and Play support (EXPERIMENTAL)"
+	depends on PNP && EXPERIMENTAL
+	help
+	  Say Y here if you would like support for ISA Plug and Play devices.
+	  Some information is in <file:Documentation/isapnp.txt>.
+
+	  This support is also available as a module called isapnp.o ( =
+	  code which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+	  If unsure, say Y.
+
+config PNPBIOS
+	bool "Plug and Play BIOS support (EXPERIMENTAL)"
+	depends on PNP && EXPERIMENTAL
+	---help---
+	  Linux uses the PNPBIOS as defined in "Plug and Play BIOS
+	  Specification Version 1.0A May 5, 1994" to autodetect built-in
+	  mainboard resources (e.g. parallel port resources).
+
+	  Some features (e.g. event notification, docking station information,
+	  ISAPNP services) are not used.
+
+	  Note: ACPI is expected to supersede PNPBIOS some day, currently it
+	  co-exists nicely.
+
+	  See latest pcmcia-cs (stand-alone package) for a nice "lspnp" tools,
+	  or have a look at /proc/bus/pnp.
+
+	  If unsure, say Y.
+
+endmenu
+

drivers/s390/Kconfig

+
+menu "Block device drivers"
+
+config BLK_DEV_LOOP
+	tristate "Loopback device support"
+	---help---
+	  Saying Y here will allow you to use a regular file as a block
+	  device; you can then create a file system on that block device and
+	  mount it just as you would mount other block devices such as hard
+	  drive partitions, CD-ROM drives or floppy drives. The loop devices
+	  are block special device files with major number 7 and typically
+	  called /dev/loop0, /dev/loop1 etc.
+
+	  This is useful if you want to check an ISO 9660 file system before
+	  burning the CD, or if you want to use floppy images without first
+	  writing them to floppy. Furthermore, some Linux distributions avoid
+	  the need for a dedicated Linux partition by keeping their complete
+	  root file system inside a DOS FAT file using this loop device
+	  driver.
+
+	  The loop device driver can also be used to "hide" a file system in a
+	  disk partition, floppy, or regular file, either using encryption
+	  (scrambling the data) or steganography (hiding the data in the low
+	  bits of, say, a sound file). This is also safe if the file resides
+	  on a remote file server. If you want to do this, you will first have
+	  to acquire and install a kernel patch from
+	  <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to
+	  say Y to this option.
+
+	  Note that alternative ways to use encrypted file systems are
+	  provided by the cfs package, which can be gotten from
+	  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs
+	  package, available at <http://tcfs.dia.unisa.it/>. You do not need
+	  to say Y here if you want to use one of these. However, using cfs
+	  requires saying Y to "NFS file system support" below while using
+	  tcfs requires applying a kernel patch. An alternative steganography
+	  solution is provided by StegFS, also available from
+	  <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
+
+	  To use the loop device, you need the losetup utility and a recent
+	  version of the mount program, both contained in the util-linux
+	  package. The location and current version number of util-linux is
+	  contained in the file <file:Documentation/Changes>.
+
+	  Note that this loop device has nothing to do with the loopback
+	  device used for network connections from the machine to itself.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>. The module
+	  will be called loop.o.
+
+	  Most users will answer N here.
+
+config BLK_DEV_NBD
+	tristate "Network block device support"
+	depends on NET
+	---help---
+	  Saying Y here will allow your computer to be a client for network
+	  block devices, i.e. it will be able to use block devices exported by
+	  servers (mount file systems on them etc.). Communication between
+	  client and server works over TCP/IP networking, but to the client
+	  program this is hidden: it looks like a regular local file access to
+	  a block device special file such as /dev/nd0.
+
+	  Network block devices also allows you to run a block-device in
+	  userland (making server and client physically the same computer,
+	  communicating using the loopback network device).
+
+	  Read <file:Documentation/nbd.txt> for more information, especially
+	  about where to find the server code, which runs in user space and
+	  does not need special kernel support.
+
+	  Note that this has nothing to do with the network file systems NFS
+	  or Coda; you can say N here even if you intend to use NFS or Coda.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>. The module
+	  will be called nbd.o.
+
+	  If unsure, say N.
+
+config BLK_DEV_RAM
+	tristate "RAM disk support"
+	---help---
+	  Saying Y here will allow you to use a portion of your RAM memory as
+	  a block device, so that you can make file systems on it, read and
+	  write to it and do all the other things that you can do with normal
+	  block devices (such as hard drives). It is usually used to load and
+	  store a copy of a minimal root file system off of a floppy into RAM
+	  during the initial install of Linux.
+
+	  Note that the kernel command line option "ramdisk=XX" is now
+	  obsolete. For details, read <file:Documentation/ramdisk.txt>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M and read <file:Documentation/modules.txt>. The module will be
+	  called rd.o.
+
+	  Most normal users won't need the RAM disk functionality, and can
+	  thus say N here.
+
+config BLK_DEV_RAM_SIZE
+	int "Default RAM disk size"
+	depends on BLK_DEV_RAM
+	default "24576"
+	help
+	  The default value is 4096. Only change this if you know what are
+	  you doing. If you are using IBM S/390, then set this to 8192.
+
+config BLK_DEV_INITRD
+	bool "Initial RAM disk (initrd) support"
+	depends on BLK_DEV_RAM=y
+	help
+	  The initial RAM disk is a RAM disk that is loaded by the boot loader
+	  (loadlin or lilo) and that is mounted as root before the normal boot
+	  procedure. It is typically used to load modules needed to mount the
+	  "real" root file system, etc. See <file:Documentation/initrd.txt>
+	  for details.
+
+config BLK_DEV_XPRAM
+	tristate "XPRAM disk support"
+	help
+	  Select this option if you want to use your expanded storage on S/390
+	  or zSeries as a disk.  This is useful as a _fast_ swap device if you
+	  want to access more than 2G of memory when running in 31 bit mode.
+	  This option is also available as a module which will be called
+	  xpram.o.  If unsure, say "N".
+
+comment "S/390 block device drivers"
+
+config DASD
+	tristate "Support for DASD devices"
+	help
+	  Enable this option if you want to access DASDs directly utilizing
+	  S/390s channel subsystem commands. This is necessary for running
+	  natively on a single image or an LPAR.
+
+config DASD_ECKD
+	tristate "Support for ECKD Disks"
+	depends on DASD
+	help
+	  ECKD devices are the most commonly used devices. you should enable
+	  this option unless you are very sure to have no ECKD device.
+
+config DASD_AUTO_ECKD
+	bool "Automatic activation of ECKD module"
+	depends on DASD && DASD_ECKD=m
+	help
+	  Enable this option if you want your ECKD discipline module loaded
+	  on DASD driver startup.
+
+config DASD_FBA
+	tristate "Support for FBA  Disks"
+	depends on DASD
+	help
+	  FBA devices are currently unsupported.
+
+config DASD_AUTO_FBA
+	bool "Automatic activation of FBA  module"
+	depends on DASD && DASD_FBA=m
+	help
+	  Enable this option if you want your FBA discipline module loaded
+	  on DASD driver startup.
+
+#  dep_tristate '   Support for CKD  Disks' CONFIG_DASD_CKD $CONFIG_DASD
+config DASD_DIAG
+	tristate "Support for DIAG access to CMS reserved Disks"
+	depends on !ARCH_S390X && DASD
+	help
+	  Select this option if you want to use CMS reserved Disks under VM
+	  with the Diagnose250 command.  If you are not running under VM or
+	  unsure what it is, say "N".
+
+config DASD_AUTO_DIAG
+	bool "Automatic activation of DIAG module"
+	depends on DASD && !ARCH_S390X && DASD_DIAG=m
+	help
+	  Enable this option if you want your DIAG discipline module loaded
+	  on DASD driver startup.
+
+endmenu
+
+source "drivers/md/Kconfig"
+
+
+menu "Character device drivers"
+
+config UNIX98_PTYS
+	bool "Unix98 PTY support"
+	---help---
+	  A pseudo terminal (PTY) is a software device consisting of two
+	  halves: a master and a slave. The slave device behaves identical to
+	  a physical terminal; the master device is used by a process to
+	  read data from and write data to the slave, thereby emulating a
+	  terminal. Typical programs for the master side are telnet servers
+	  and xterms.
+
+	  Linux has traditionally used the BSD-like names /dev/ptyxx for
+	  masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
+	  has a number of problems. The GNU C library glibc 2.1 and later,
+	  however, supports the Unix98 naming standard: in order to acquire a
+	  pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
+	  terminal is then made available to the process and the pseudo
+	  terminal slave can be accessed as /dev/pts/<number>. What was
+	  traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
+
+	  The entries in /dev/pts/ are created on the fly by a virtual
+	  file system; therefore, if you say Y here you should say Y to
+	  "/dev/pts file system for Unix98 PTYs" as well.
+
+	  If you want to say Y here, you need to have the C library glibc 2.1
+	  or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
+	  Read the instructions in <file:Documentation/Changes> pertaining to
+	  pseudo terminals. It's safe to say N.
+
+config UNIX98_PTY_COUNT
+	int "Maximum number of Unix98 PTYs in use (0-2048)"
+	depends on UNIX98_PTYS
+	default "256"
+	help
+	  The maximum number of Unix98 PTYs that can be used at any one time.
+	  The default is 256, and should be enough for desktop systems. Server
+	  machines which support incoming telnet/rlogin/ssh connections and/or
+	  serve several X terminals may want to increase this: every incoming
+	  connection and every xterm uses up one PTY.
+
+	  When not in use, each additional set of 256 PTYs occupy
+	  approximately 8 KB of kernel memory on 32-bit architectures.
+
+comment "S/390 character device drivers"
+
+config TN3270
+	tristate "Support for locally attached 3270 tubes"
+	help
+	  Include support for IBM 3270 line-mode terminals.
+
+config TN3270_CONSOLE
+	bool "Support for console on 3270 line mode terminal"
+	depends on TN3270=y
+	help
+	  Include support for using an IBM 3270 line-mode terminal as a Linux
+	  system console.  Available only if 3270 support is compiled in
+	  statically.
+
+config TN3215
+	bool "Support for 3215 line mode terminal"
+	help
+	  Include support for IBM 3215 line-mode terminals.
+
+config TN3215_CONSOLE
+	bool "Support for console on 3215 line mode terminal"
+	depends on TN3215
+	help
+	  Include support for using an IBM 3215 line-mode terminal as a
+	  Linux system console.
+
+config HWC
+	bool "Support for HWC line mode terminal"
+	help
+	  Include support for IBM HWC line-mode terminals.
+
+config HWC_CONSOLE
+	bool "console on HWC line mode terminal"
+	depends on HWC
+	help
+	  Include support for using an IBM HWC line-mode terminal as the Linux
+	  system console.
+
+config HWC_CPI
+	tristate "Control-Program Identification"
+	depends on HWC
+	help
+	  This option enables the hardware console interface for system
+	  identification This is commonly used for workload management and
+	  gives you a nice name for the system on the service element.
+	  Please select this option as a module since built-in operation is
+	  completely untested.
+	  You should only select this option if you know what you are doing,
+	  need this feature and intend to run your kernel in LPAR.
+
+config S390_TAPE
+	tristate "S/390 tape device support"
+	help
+	  Select this option if you want to access channel-attached tape
+	  devices on IBM S/390 or zSeries.
+	  If you select this option you will also want to select at
+	  least one of the tape interface options and one of the tape
+	  hardware options in order to access a tape device.
+	  This option is also available as a module. The module will be
+	  called tape390.o and include all selected interfaces and
+	  hardware drivers.
+
+comment "S/390 tape interface support"
+	depends on S390_TAPE
+
+config S390_TAPE_CHAR
+	bool "Support for tape character devices"
+	depends on S390_TAPE
+	help
+	  Select this option if you want to access your channel-attached
+	  tape devices using the character device interface.
+	  This interface is similar to other Linux tape devices like
+	  SCSI-Tapes (st) and the floppy tape device (ftape).
+	  If unsure, say "Y".
+
+config S390_TAPE_BLOCK
+	bool "Support for tape block devices"
+	depends on S390_TAPE
+	help
+	  Select this option if you want to access your channel-attached tape
+	  devices using the block device interface.  This interface is similar
+	  to CD-ROM devices on other platforms.  The tapes can only be
+	  accessed read-only when using this interface.  Have a look at
+	  Documentation/s390/TAPE for further information about creating
+	  volumes for and using this interface.  It is safe to say "Y" here.
+
+comment "S/390 tape hardware support"
+	depends on S390_TAPE
+
+config S390_TAPE_3490
+	tristate "Support for 3490 tape hardware"
+	depends on S390_TAPE
+	help
+	  Select this option if you want to access IBM 3480 magnetic
+	  tape subsystems and 100% compatibles.
+	  It is safe to say "Y" here.
+
+config S390_TAPE_3480
+	tristate "Support for 3480 tape hardware"
+	depends on S390_TAPE
+	help
+	  Select this option if you want to access IBM 3490 magnetic
+	  tape subsystems and 100% compatibles.
+
+endmenu
+
+
+menu "Network device drivers"
+	depends on NET
+
+config NETDEVICES
+	bool "Network device support"
+	---help---
+	  You can say N here if you don't intend to connect your Linux box to
+	  any other computer at all or if all your connections will be over a
+	  telephone line with a modem either via UUCP (UUCP is a protocol to
+	  forward mail and news between unix hosts over telephone lines; read
+	  the UUCP-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>) or dialing up a shell
+	  account or a BBS, even using term (term is a program which gives you
+	  almost full Internet connectivity if you have a regular dial up
+	  shell account on some Internet connected Unix computer. Read
+	  <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
+
+	  You'll have to say Y if your computer contains a network card that
+	  you want to use under Linux (make sure you know its name because you
+	  will be asked for it and read the Ethernet-HOWTO (especially if you
+	  plan to use more than one network card under Linux)) or if you want
+	  to use SLIP (Serial Line Internet Protocol is the protocol used to
+	  send Internet traffic over telephone lines or null modem cables) or
+	  CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better
+	  and newer replacement for SLIP) or PLIP (Parallel Line Internet
+	  Protocol is mainly used to create a mini network by connecting the
+	  parallel ports of two local machines) or AX.25/KISS (protocol for
+	  sending Internet traffic over amateur radio links).
+
+	  Make sure to read the NET-3-HOWTO. Eventually, you will have to read
+	  Olaf Kirch's excellent and free book "Network Administrator's
+	  Guide", to be found in <http://www.linuxdoc.org/docs.html#guide>. If
+	  unsure, say Y.
+
+config DUMMY
+	tristate "Dummy net driver support"
+	depends on NETDEVICES
+	---help---
+	  This is essentially a bit-bucket device (i.e. traffic you send to
+	  this device is consigned into oblivion) with a configurable IP
+	  address. It is most commonly used in order to make your currently
+	  inactive SLIP address seem like a real address for local programs.
+	  If you use SLIP or PPP, you might want to say Y here. Since this
+	  thing often comes in handy, the default is Y. It won't enlarge your
+	  kernel either. What a deal. Read about it in the Network
+	  Administrator's Guide, available from
+	  <http://www.linuxdoc.org/docs.html#guide>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called dummy.o.  If you want to use more than one dummy
+	  device at a time, you need to compile this driver as a module.
+	  Instead of 'dummy', the devices will then be called 'dummy0',
+	  'dummy1' etc.
+
+config BONDING
+	tristate "Bonding driver support"
+	depends on NETDEVICES
+	---help---
+	  Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
+	  Channels together. This is called 'Etherchannel' by Cisco,
+	  'Trunking' by Sun, and 'Bonding' in Linux.
+
+	  If you have two Ethernet connections to some other computer, you can
+	  make them behave like one double speed connection using this driver.
+	  Naturally, this has to be supported at the other end as well, either
+	  with a similar Bonding Linux driver, a Cisco 5500 switch or a
+	  SunTrunking SunSoft driver.
+
+	  This is similar to the EQL driver, but it merges Ethernet segments
+	  instead of serial lines.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called bonding.o.
+
+config EQUALIZER
+	tristate "EQL (serial line load balancing) support"
+	depends on NETDEVICES
+	---help---
+	  If you have two serial connections to some other computer (this
+	  usually requires two modems and two telephone lines) and you use
+	  SLIP (the protocol for sending Internet traffic over telephone
+	  lines) or PPP (a better SLIP) on them, you can make them behave like
+	  one double speed connection using this driver.  Naturally, this has
+	  to be supported at the other end as well, either with a similar EQL
+	  Linux driver or with a Livingston Portmaster 2e.
+
+	  Say Y if you want this and read
+	  <file:Documentation/networking/eql.txt>.  You may also want to read
+	  section 6.2 of the NET-3-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called eql.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.  If
+	  unsure, say N.
+
+config TUN
+	tristate "Universal TUN/TAP device driver support"
+	depends on NETDEVICES
+	---help---
+	  TUN/TAP provides packet reception and transmission for user space
+	  programs.  It can be viewed as a simple Point-to-Point or Ethernet
+	  device, which instead of receiving packets from a physical media,
+	  receives them from user space program and instead of sending packets
+	  via physical media writes them to the user space program.
+
+	  When a program opens /dev/net/tun, driver creates and registers
+	  corresponding net device tunX or tapX.  After a program closed above
+	  devices, driver will automatically delete tunXX or tapXX device and
+	  all routes corresponding to it.
+
+	  Please read <file:Documentation/networking/tuntap.txt> for more
+	  information.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called tun.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+	  If you don't know what to use this for, you don't need it.
+
+config NET_ETHERNET
+	bool "Ethernet (10 or 100Mbit)"
+	depends on NETDEVICES
+	---help---
+	  Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
+	  type of Local Area Network (LAN) in universities and companies.
+
+	  Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
+	  coaxial cable, linking computers in a chain), 10BASE-T or twisted
+	  pair (10 Mbps over twisted pair cable, linking computers to central
+	  hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
+	  100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
+	  100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
+	  cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
+	  [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
+	  Ethernet (1 Gbps over optical fiber or short copper links).
+
+	  If your Linux machine will be connected to an Ethernet and you have
+	  an Ethernet network interface card (NIC) installed in your computer,
+	  say Y here and read the Ethernet-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>. You will then also have
+	  to say Y to the driver for your particular NIC.
+
+	  Note that the answer to this question won't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions about Ethernet network cards. If unsure, say N.
+
+config TR
+	bool "Token Ring driver support"
+	depends on NETDEVICES
+	help
+	  Token Ring is IBM's way of communication on a local network; the
+	  rest of the world uses Ethernet. To participate on a Token Ring
+	  network, you need a special Token ring network card. If you are
+	  connected to such a Token Ring network and want to use your Token
+	  Ring card under Linux, say Y here and to the driver for your
+	  particular card below and read the Token-Ring mini-HOWTO, available
+	  from <http://www.linuxdoc.org/docs.html#howto>. Most people can
+	  say N here.
+
+config FDDI
+	bool "FDDI driver support"
+	depends on NETDEVICES
+	help
+	  Fiber Distributed Data Interface is a high speed local area network
+	  design; essentially a replacement for high speed Ethernet. FDDI can
+	  run over copper or fiber. If you are connected to such a network and
+	  want a driver for the FDDI card in your computer, say Y here (and
+	  then also Y to the driver for your FDDI card, below). Most people
+	  will say N.
+
+comment "S/390 network device drivers"
+	depends on NETDEVICES
+
+config CHANDEV
+	bool "Channel Device Configuration"
+	depends on NETDEVICES
+	---help---
+	  The channel device layer is a layer to provide a consistent
+	  interface for configuration & default machine check (devices
+	  appearing & disappearing) handling on Linux for s/390 & z/Series
+	  channel devices.
+
+	  s/390 & z/Series channel devices include among others
+
+	  lcs (the most common ethernet/token ring/fddi standard on
+	  zSeries)
+	  ctc/escon hi speed like serial link standard on zSeries
+	  claw used to talk to cisco routers.
+	  qeth gigabit ethernet.
+
+	  These devices use two channels one read & one write for
+	  configuration & communication (& a third channel, the data
+	  channel the case of gigabit ethernet). The motivation
+	  behind developing this layer was that there was a lot of
+	  duplicate code among the channel device drivers for
+	  configuration.
+
+	  Also the lcs & ctc drivers tended to fight over
+	  3088/08's & 3088/1F's which could be either 2216/3172
+	  channel attached lcs compatible devices or escon/ctc pipes
+	  had to be configured separately as they couldn't autodetect,
+	  this is now simplified by doing the configuration in a single
+	  place (the channel device layer).
+
+	  This layer isn't invasive & it is quite okay to use channel
+	  drivers which don't use the channel device layer in
+	  conjunction with drivers which do.
+
+	  For more info see the chandev manpage usually distributed in
+	  <file:Documentation/s390/chandev.8> in the Linux source tree.
+
+config HOTPLUG
+	bool
+	depends on CHANDEV
+	default y
+	---help---
+	  Say Y here if you want to plug devices into your computer while
+	  the system is running, and be able to use them quickly.  In many
+	  cases, the devices can likewise be unplugged at any time too.
+
+	  One well known example of this is PCMCIA- or PC-cards, credit-card
+	  size devices such as network cards, modems or hard drives which are
+	  plugged into slots found on all modern laptop computers.  Another
+	  example, used on modern desktops as well as laptops, is USB.
+
+	  Enable HOTPLUG and KMOD, and build a modular kernel.  Get agent
+	  software (at <http://linux-hotplug.sourceforge.net/>) and install it.
+	  Then your kernel will automatically call out to a user mode "policy
+	  agent" (/sbin/hotplug) to load modules and set up software needed
+	  to use devices as you hotplug them.
+
+config LCS
+	tristate "Lan Channel Station Interface"
+	depends on NETDEVICES && (NET_ETHERNET || TR)
+
+config CTC
+	tristate "CTC device support"
+	depends on NETDEVICES
+	help
+	  Select this option if you want to use channel-to-channel networking
+	  on IBM S/390 or zSeries. This device driver supports real CTC
+	  coupling using ESCON. It also supports virtual CTCs when running
+	  under VM. It will use the channel device configuration if this is
+	  available.  This option is also available as a module which will be
+	  called ctc.o.  If you do not know what it is, it's safe to say "Y".
+
+config IUCV
+	tristate "IUCV device support (VM only)"
+	depends on NETDEVICES
+	help
+	  Select this option if you want to use inter-user communication
+	  vehicle networking under VM or VIF.  This option is also available
+	  as a module which will be called iucv.o. If unsure, say "Y".
+
+endmenu
+

drivers/sbus/char/Kconfig

+
+menu "Misc Linux/SPARC drivers"
+
+config SUN_OPENPROMIO
+	tristate "/dev/openprom device support"
+	help
+	  This driver provides user programs with an interface to the SPARC
+	  PROM device tree. The driver implements a SunOS-compatible
+	  interface and a NetBSD-compatible interface.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M and read <file:Documentation/modules.txt>. If unsure, say Y.
+
+config SUN_MOSTEK_RTC
+	tristate "Mostek real time clock support"
+	help
+	  The Mostek RTC chip is used on all known Sun computers except
+	  some JavaStations. For a JavaStation you need to say Y both here
+	  and to "Enhanced Real Time Clock Support".
+
+	  Say Y here unless you are building a special purpose kernel.
+
+config OBP_FLASH
+	tristate "OBP Flash Device support"
+	depends on SPARC64
+	help
+	  The OpenBoot PROM on Ultra systems is flashable. If you want to be
+	  able to upgrade the OBP firmware, say Y here.
+
+config SUN_BPP
+	tristate "Bidirectional parallel port support (OBSOLETE)"
+	depends on EXPERIMENTAL
+	help
+	  Say Y here to support Sun's obsolete variant of IEEE1284
+	  bidirectional parallel port protocol as /dev/bppX.  Can be built on
+	  x86 machines.
+
+config SUN_VIDEOPIX
+	tristate "Videopix Frame Grabber (EXPERIMENTAL)"
+	depends on EXPERIMENTAL
+	help
+	  Say Y here to support the Videopix Frame Grabber from Sun
+	  Microsystems, commonly found on SPARCstations.  This card, which is
+	  based on the Phillips SAA9051, can handle NTSC and PAL/SECAM and
+	  SVIDEO signals.
+
+config SUN_AURORA
+	tristate "Aurora Multiboard 1600se (EXPERIMENTAL)"
+	depends on EXPERIMENTAL
+	help
+	  The Aurora Multiboard is a multi-port high-speed serial controller.
+	  If you have one of these, say Y.
+
+config TADPOLE_TS102_UCTRL
+	tristate "Tadpole TS102 Microcontroller support (EXPERIMENTAL)"
+	depends on EXPERIMENTAL && SPARC32
+	help
+	  Say Y here to directly support the TS102 Microcontroller interface
+	  on the Tadpole Sparcbook 3.  This device handles power-management
+	  events, and can also notice the attachment/detachment of external
+	  monitors and mice.
+
+config SUN_JSFLASH
+	tristate "JavaStation OS Flash SIMM (EXPERIMENTAL)"
+	depends on EXPERIMENTAL && SPARC32
+	help
+	  If you say Y here, you will be able to boot from your JavaStation's
+	  Flash memory.
+
+# XXX Why don't we do "source drivers/char/Config.in" somewhere?
+# no shit
+config APM_RTC_IS_GMT
+	bool
+	depends on EXPERIMENTAL && SPARC32 && PCI
+	default y
+	help
+	  Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
+	  stores the time in GMT (Greenwich Mean Time). Say N if your RTC
+	  stores localtime.
+
+	  It is in fact recommended to store GMT in your RTC, because then you
+	  don't have to worry about daylight savings time changes. The only
+	  reason not to use GMT in your RTC is if you also run a broken OS
+	  that doesn't understand GMT.
+
+config RTC
+	tristate "PC-style Real Time Clock Support"
+	depends on PCI && EXPERIMENTAL && SPARC32
+
+endmenu
+

drivers/scsi/Kconfig

+comment "SCSI support type (disk, tape, CD-ROM)"
+	depends on SCSI
+
+config BLK_DEV_SD
+	tristate "SCSI disk support"
+	depends on SCSI
+	---help---
+	  If you want to use a SCSI hard disk or the SCSI or parallel port
+	  version of the IOMEGA ZIP drive under Linux, say Y and read the
+	  SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>. This is NOT for SCSI
+	  CD-ROMs.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called sd_mod.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> and
+	  <file:Documentation/scsi.txt>.  Do not compile this driver as a
+	  module if your root file system (the one containing the directory /)
+	  is located on a SCSI disk. In this case, do not compile the driver
+	  for your SCSI host adapter (below) as a module either.
+
+config CHR_DEV_ST
+	tristate "SCSI tape support"
+	depends on SCSI
+	---help---
+	  If you want to use a SCSI tape drive under Linux, say Y and read the
+	  SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>, and
+	  <file:drivers/scsi/README.st> in the kernel source.  This is NOT for
+	  SCSI CD-ROMs.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called st.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> and
+	  <file:Documentation/scsi.txt>.
+
+config CHR_DEV_OSST
+	tristate "SCSI OnStream SC-x0 tape support"
+	depends on SCSI
+	---help---
+	  The OnStream SC-x0 SCSI tape drives can not be driven by the
+	  standard st driver, but instead need this special osst driver and
+	  use the  /dev/osstX char device nodes (major 206).  Via usb-storage
+	  and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
+	  as well.  Note that there is also a second generation of OnStream
+	  tape drives (ADR-x0) that supports the standard SCSI-2 commands for
+	  tapes (QIC-157) and can be driven by the standard driver st.
+	  For more information, you may have a look at the SCSI-HOWTO
+	  <http://www.linuxdoc.org/docs.html#howto>  and
+	  <file:drivers/scsi/README.osst>  in the kernel source.
+	  More info on the OnStream driver may be found on
+	  <http://linux1.onstream.nl/test/>
+	  Please also have a look at the standard st docu, as most of it
+	  applies to osst as well.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called osst.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> and
+	  <file:Documentation/scsi.txt>.
+
+config BLK_DEV_SR
+	tristate "SCSI CDROM support"
+	depends on SCSI
+	---help---
+	  If you want to use a SCSI CD-ROM under Linux, say Y and read the
+	  SCSI-HOWTO and the CD-ROM-HOWTO at
+	  <http://www.linuxdoc.org/docs.html#howto>. Also make sure to say Y
+	  or M to "ISO 9660 CD-ROM file system support" later.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called sr_mod.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt> and
+	  <file:Documentation/scsi.txt>.
+
+config BLK_DEV_SR_VENDOR
+	bool "Enable vendor-specific extensions (for SCSI CDROM)"
+	depends on BLK_DEV_SR
+	help
+	  This enables the usage of vendor specific SCSI commands. This is
+	  required to support multisession CDs with old NEC/TOSHIBA cdrom
+	  drives (and HP Writers). If you have such a drive and get the first
+	  session only, try saying Y here; everybody else says N.
+
+config SR_EXTRA_DEVS
+	int "Maximum number of CDROM devices that can be loaded as modules"
+	depends on BLK_DEV_SR
+	default "2"
+	---help---
+	  This controls the amount of additional space allocated in tables for
+	  drivers that are loaded as modules after the kernel is booted. In
+	  the event that the SCSI core itself was loaded as a module, this
+	  value is the number of additional CD-ROMs that can be loaded after
+	  the first host driver is loaded.
+
+	  Admittedly this isn't pretty, but there are tons of race conditions
+	  involved with resizing the internal arrays on the fly.  Someday this
+	  flag will go away, and everything will work automatically.
+
+	  If you don't understand what's going on, go with the default.
+
+config CHR_DEV_SG
+	tristate "SCSI generic support"
+	depends on SCSI
+	---help---
+	  If you want to use SCSI scanners, synthesizers or CD-writers or just
+	  about anything having "SCSI" in its name other than hard disks,
+	  CD-ROMs or tapes, say Y here. These won't be supported by the kernel
+	  directly, so you need some additional software which knows how to
+	  talk to these devices using the SCSI protocol:
+
+	  For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
+	  writer software look at Cdrtools
+	  (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
+	  and for burning a "disk at once": CDRDAO
+	  (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
+	  quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
+	  For other devices, it's possible that you'll have to write the
+	  driver software yourself. Please read the file
+	  <file:Documentation/scsi-generic.txt> for more information.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt> and
+	  <file:Documentation/scsi.txt>. The module will be called sg.o. If unsure,
+	  say N.
+
+comment "Some SCSI devices (e.g. CD jukebox) support multiple LUNs"
+	depends on SCSI
+
+config SCSI_MULTI_LUN
+	bool "Probe all LUNs on each SCSI device"
+	depends on SCSI
+	help
+	  If you have a SCSI device that supports more than one LUN (Logical
+	  Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
+	  can say Y here to force the SCSI driver to probe for multiple LUNs.
+	  A SCSI device with multiple LUNs acts logically like multiple SCSI
+	  devices. The vast majority of SCSI devices have only one LUN, and
+	  so most people can say N here and should in fact do so, because it
+	  is safer.
+
+config SCSI_REPORT_LUNS
+	bool "Build with SCSI REPORT LUNS support"
+	depends on SCSI
+	help
+	  If you want to build with SCSI REPORT LUNS support in the kernel, say Y here.
+	  The REPORT LUNS command is useful for devices (such as disk arrays) with
+	  large numbers of LUNs where the LUN values are not contiguous (sparse LUN).
+	  REPORT LUNS scanning is done only for SCSI-3 devices. Most users can safely
+	  answer N here.
+
+config SCSI_CONSTANTS
+	bool "Verbose SCSI error reporting (kernel size +=12K)"
+	depends on SCSI
+	help
+	  The error messages regarding your SCSI hardware will be easier to
+	  understand if you say Y here; it will enlarge your kernel by about
+	  12 KB. If in doubt, say Y.
+
+config SCSI_LOGGING
+	bool "SCSI logging facility"
+	depends on SCSI
+	---help---
+	  This turns on a logging facility that can be used to debug a number
+	  of SCSI related problems.
+
+	  If you say Y here, no logging output will appear by default, but you
+	  can enable logging by saying Y to "/proc file system support" and
+	  "Sysctl support" below and executing the command
+
+	  echo "scsi log token [level]" > /proc/scsi/scsi
+
+	  at boot time after the /proc file system has been mounted.
+
+	  There are a number of things that can be used for 'token' (you can
+	  find them in the source: <file:drivers/scsi/scsi.c>), and this
+	  allows you to select the types of information you want, and the
+	  level allows you to select the level of verbosity.
+
+	  If you say N here, it may be harder to track down some types of SCSI
+	  problems. If you say Y here your kernel will be somewhat larger, but
+	  there should be no noticeable performance impact as long as you have
+	  logging turned off.
+
+
+menu "SCSI low-level drivers"
+	depends on SCSI!=n
+
+config SGIWD93_SCSI
+	tristate "SGI WD93C93 SCSI Driver"
+	depends on SGI_IP22 && SCSI
+
+config SCSI_DECNCR
+	tristate "DEC NCR53C94 Scsi Driver"
+	depends on DECSTATION && TC && SCSI
+	help
+	  Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
+	  based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
+
+config SCSI_DECSII
+	tristate "DEC SII Scsi Driver"
+	depends on DECSTATION && SCSI
+
+config BLK_DEV_3W_XXXX_RAID
+	tristate "3ware Hardware ATA-RAID support"
+	depends on PCI && SCSI
+	help
+	  3ware is the only hardware ATA-Raid product in Linux to date.
+	  This card is 2,4, or 8 channel master mode support only.
+	  SCSI support required!!!
+
+	  <http://www.3ware.com/>
+
+	  Please read the comments at the top of
+	  <file:drivers/scsi/3w-xxxx.c>.
+
+config SCSI_7000FASST
+	tristate "7000FASST SCSI support"
+	depends on SCSI && ISA
+	help
+	  This driver supports the Western Digital 7000 SCSI host adapter
+	  family.  Some information is in the source:
+	  <file:drivers/scsi/wd7000.c>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called wd7000.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_ACARD
+	tristate "ACARD SCSI support"
+	depends on SCSI
+	help
+	  This driver supports the ACARD 870U/W SCSI host adapter.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called atp870u.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_AHA152X
+	tristate "Adaptec AHA152X/2825 support"
+	depends on ISA && SCSI
+	---help---
+	  This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
+	  SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
+	  must be manually specified in this case.
+
+	  It is explained in section 3.3 of the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>. You might also want to
+	  read the file <file:drivers/scsi/README.aha152x>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called aha152x.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_AHA1542
+	tristate "Adaptec AHA1542 support"
+	depends on ISA && SCSI
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.4 of the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  Note that Trantor was
+	  purchased by Adaptec, and some former Trantor products are being
+	  sold under the Adaptec name.  If it doesn't work out of the box, you
+	  may have to change some settings in <file:drivers/scsi/aha1542.h>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called aha1542.o.
+
+config SCSI_AHA1740
+	tristate "Adaptec AHA1740 support"
+	depends on EISA && SCSI
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.5 of the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/aha1740.h>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called aha1740.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_AACRAID
+	tristate "Adaptec AACRAID support (EXPERIMENTAL)"
+	depends on EXPERIMENTAL && SCSI && PCI
+
+choice
+	prompt "Adaptec AIC7xxx support"
+	optional
+	depends on SCSI
+
+source "drivers/scsi/aic7xxx/Kconfig"
+
+config SCSI_AIC7XXX_OLD
+	tristate "Old driver"
+	help
+	  WARNING This driver is an older aic7xxx driver and is no longer
+	  under active development.  Adaptec, Inc. is writing a new driver to
+	  take the place of this one, and it is recommended that whenever
+	  possible, people should use the new Adaptec written driver instead
+	  of this one.  This driver will eventually be phased out entirely.
+
+	  This is support for the various aic7xxx based Adaptec SCSI
+	  controllers. These include the 274x EISA cards; 284x VLB cards;
+	  2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
+	  motherboard based SCSI controllers from Adaptec. It does not support
+	  the AAA-13x RAID controllers from Adaptec, nor will it likely ever
+	  support them. It does not support the 2920 cards from Adaptec that
+	  use the Future Domain SCSI controller chip. For those cards, you
+	  need the "Future Domain 16xx SCSI support" driver.
+
+	  In general, if the controller is based on an Adaptec SCSI controller
+	  chip from the aic777x series or the aic78xx series, this driver
+	  should work. The only exception is the 7810 which is specifically
+	  not supported (that's the RAID controller chip on the AAA-13x
+	  cards).
+
+	  Note that the AHA2920 SCSI host adapter is *not* supported by this
+	  driver; choose "Future Domain 16xx SCSI support" instead if you have
+	  one of those.
+
+	  Information on the configuration options for this controller can be
+	  found by checking the help file for each of the available
+	  configuration options. You should read
+	  <file:drivers/scsi/aic7xxx_old/README.aic7xxx> at a minimum before
+	  contacting the maintainer with any questions.  The SCSI-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>, can also
+	  be of great help.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called aic7xxx_old.o.
+
+endchoice
+
+
+# All the I2O code and drivers do not seem to be 64bit safe.
+config SCSI_DPT_I2O
+	tristate "Adaptec I2O RAID support "
+	depends on !X86_64 && SCSI
+	help
+	  This driver supports all of Adaptec's I2O based RAID controllers as 
+	  well as the DPT SmartRaid V cards.  This is an Adaptec maintained
+	  driver by Deanna Bonds.  See <file:drivers/scsi/README.dpti>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  dpt_i2o.o.
+
+config SCSI_ADVANSYS
+	tristate "AdvanSys SCSI support"
+	depends on SCSI
+	help
+	  This is a driver for all SCSI host adapters manufactured by
+	  AdvanSys. It is documented in the kernel source in
+	  <file:drivers/scsi/advansys.c>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  advansys.o.
+
+config SCSI_IN2000
+	tristate "Always IN2000 SCSI support"
+	depends on SCSI
+	help
+	  This is support for an ISA bus SCSI host adapter.  You'll find more
+	  information in <file:drivers/scsi/README.in2000>. If it doesn't work
+	  out of the box, you may have to change the jumpers for IRQ or
+	  address selection.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called in2000.o.
+
+# does not use pci dma and seems to be isa/onboard only for old machines
+config SCSI_AM53C974
+	tristate "AM53/79C974 PCI SCSI support"
+	depends on !X86_64 && SCSI && PCI
+	---help---
+	  This is support for the AM53/79C974 SCSI host adapters.  Please read
+	  <file:drivers/scsi/README.AM53C974> for details.  Also, the
+	  SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>, is for you.
+
+	  Note that there is another driver for AM53C974 based adapters:
+	  "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above.  You
+	  can pick either one.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called AM53C974.o.
+
+config SCSI_MEGARAID
+	tristate "AMI MegaRAID support"
+	depends on SCSI
+	help
+	  This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
+	  and 467 SCSI host adapters.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called megaraid.o.
+
+config SCSI_BUSLOGIC
+	tristate "BusLogic SCSI support"
+	depends on SCSI
+	---help---
+	  This is support for BusLogic MultiMaster and FlashPoint SCSI Host
+	  Adapters. Consult the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>, and the files
+	  <file:drivers/scsi/README.BusLogic> and
+	  <file:drivers/scsi/README.FlashPoint> for more information. If this
+	  driver does not work correctly without modification, please contact
+	  the author, Leonard N. Zubkoff, by email to lnz@dandelion.com.
+
+	  You can also build this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  but only a single instance may be loaded. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+	  The module will be called BusLogic.o.
+
+config SCSI_OMIT_FLASHPOINT
+	bool "Omit FlashPoint support"
+	depends on SCSI_BUSLOGIC
+	help
+	  This option allows you to omit the FlashPoint support from the
+	  BusLogic SCSI driver. The FlashPoint SCCB Manager code is
+	  substantial, so users of MultiMaster Host Adapters may wish to omit
+	  it.
+
+config SCSI_CPQFCTS
+	tristate "Compaq Fibre Channel 64-bit/66Mhz HBA support"
+	depends on PCI && SCSI
+	help
+	  Say Y here to compile in support for the Compaq StorageWorks Fibre
+	  Channel 64-bit/66Mhz Host Bus Adapter.
+
+config SCSI_DMX3191D
+	tristate "DMX3191D SCSI support"
+	depends on SCSI && PCI
+	help
+	  This is support for Domex DMX3191D SCSI Host Adapters.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called dmx3191d.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_DTC3280
+	tristate "DTC3180/3280 SCSI support"
+	depends on SCSI && ISA
+	help
+	  This is support for DTC 3180/3280 SCSI Host Adapters.  Please read
+	  the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>, and the file
+	  <file:drivers/scsi/README.dtc3x80>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called dtc.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_EATA
+	tristate "EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support"
+	depends on SCSI
+	---help---
+	  This driver supports all EATA/DMA-compliant SCSI host adapters.  DPT
+	  ISA and all EISA I/O addresses are probed looking for the "EATA"
+	  signature.  If you chose "BIOS" at the question "PCI access mode",
+	  the addresses of all the PCI SCSI controllers reported by the PCI
+	  subsystem are probed as well.
+
+	  You want to read the start of <file:drivers/scsi/eata.c> and the
+	  SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  Note that there is also another driver for the same hardware
+	  available: "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti,
+	  Alphatronix) support". You should say Y to only one of them.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called eata.o.
+
+config SCSI_EATA_TAGGED_QUEUE
+	bool "enable tagged command queueing"
+	depends on SCSI_EATA
+	help
+	  This is a feature of SCSI-2 which improves performance: the host
+	  adapter can send several SCSI commands to a device's queue even if
+	  previous commands haven't finished yet. Most EATA adapters negotiate
+	  this feature automatically with the device, even if your answer is
+	  N. The safe answer is N.
+
+config SCSI_EATA_LINKED_COMMANDS
+	bool "enable elevator sorting"
+	depends on SCSI_EATA
+	help
+	  This option enables elevator sorting for all probed SCSI disks and
+	  CD-ROMs. It definitely reduces the average seek distance when doing
+	  random seeks, but this does not necessarily result in a noticeable
+	  performance improvement: your mileage may vary...
+	  The safe answer is N.
+
+config SCSI_EATA_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_EATA
+	default "16"
+	help
+	  This specifies how many SCSI commands can be maximally queued for
+	  each probed SCSI device. You should reduce the default value of 16
+	  only if you have disks with buggy or limited tagged command support.
+	  Minimum is 2 and maximum is 62. This value is also the window size
+	  used by the elevator sorting option above. The effective value used
+	  by the driver for each probed SCSI device is reported at boot time.
+
+config SCSI_EATA_DMA
+	tristate "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support"
+	depends on SCSI
+	---help---
+	  This is support for the EATA-DMA protocol compliant SCSI Host
+	  Adapters like the SmartCache III/IV, SmartRAID controller families
+	  and the DPT PM2011B and PM2012B controllers.
+
+	  Note that this driver is obsolete; if you have one of the above
+	  SCSI Host Adapters, you should normally say N here and Y to "EATA
+	  ISA/EISA/PCI support", below.  Please read the SCSI-HOWTO, available
+	  from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called eata_dma.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_EATA_PIO
+	tristate "EATA-PIO (old DPT PM2001, PM2012A) support"
+	depends on SCSI
+	---help---
+	  This driver supports all EATA-PIO protocol compliant SCSI Host
+	  Adapters like the DPT PM2001 and the PM2012A.  EATA-DMA compliant
+	  host adapters could also use this driver but are discouraged from
+	  doing so, since this driver only supports hard disks and lacks
+	  numerous features.  You might want to have a look at the SCSI-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called eata_pio.o.
+
+config SCSI_FUTURE_DOMAIN
+	tristate "Future Domain 16xx SCSI/AHA-2920A support"
+	depends on SCSI
+	---help---
+	  This is support for Future Domain's 16-bit SCSI host adapters
+	  (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
+	  other adapters based on the Future Domain chipsets (Quantum
+	  ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
+	  It is explained in section 3.7 of the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
+	  and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
+	  controller support"). This Future Domain driver works with the older
+	  Adaptec AHA-2920A boards with a Future Domain chip on them.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called fdomain.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_FD_MCS
+	tristate "Future Domain MCS-600/700 SCSI support"
+	depends on MCA && SCSI
+	---help---
+	  This is support for Future Domain MCS 600/700 MCA SCSI adapters.
+	  Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
+	  is identical to the MCS 700 and hence also supported by this driver.
+	  This driver also supports the Reply SB16/SCSI card (the SCSI part).
+	  It supports multiple adapters in the same system.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called fd_mcs.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_GDTH
+	tristate "Intel/ICP (former GDT SCSI Disk Array) RAID Controller support"
+	depends on SCSI
+	---help---
+	  Formerly called GDT SCSI Disk Array Controller Support.
+
+	  This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI) 
+	  manufactured by Intel/ICP vortex (an Intel Company). It is documented
+	  in the kernel source in <file:drivers/scsi/gdth.c> and
+	  <file:drivers/scsi/gdth.h.>
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  If you want to compile it as a module, say M here and read
+	  <file:Documentation/modules.txt>.
+
+config SCSI_GENERIC_NCR5380
+	tristate "Generic NCR5380/53c400 SCSI PIO support"
+	depends on SCSI
+	---help---
+	  This is a driver for the old NCR 53c80 series of SCSI controllers
+	  on boards using PIO. Most boards such as the Trantor T130 fit this
+	  category, along with a large number of ISA 8bit controllers shipped
+	  for free with SCSI scanners. If you have a PAS16, T128 or DMX3191
+	  you should select the specific driver for that card rather than
+	  generic 5380 support.
+
+	  It is explained in section 3.8 of the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/g_NCR5380.h>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called g_NCR5380.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_GENERIC_NCR5380_MMIO
+	tristate "Generic NCR5380/53c400 SCSI MMIO support"
+	depends on SCSI
+	---help---
+	  This is a driver for the old NCR 53c80 series of SCSI controllers
+	  on boards using memory mapped I/O. 
+	  It is explained in section 3.8 of the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/g_NCR5380.h>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called g_NCR5380.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_GENERIC_NCR53C400
+	bool "Enable NCR53c400 extensions"
+	depends on SCSI_GENERIC_NCR5380
+	help
+	  This enables certain optimizations for the NCR53c400 SCSI cards.
+	  You might as well try it out.  Note that this driver will only probe
+	  for the Trantor T130B in its default configuration; you might have
+	  to pass a command line option to the kernel at boot time if it does
+	  not detect your card.  See the file
+	  <file:drivers/scsi/README.g_NCR5380> for details.
+
+config SCSI_IBMMCA
+	tristate "IBMMCA SCSI support"
+	depends on MCA && SCSI
+	---help---
+	  This is support for the IBM SCSI adapter found in many of the PS/2
+	  series computers.  These machines have an MCA bus, so you need to
+	  answer Y to "MCA support" as well and read
+	  <file:Documentation/mca.txt>.
+
+	  If the adapter isn't found during boot (a common problem for models
+	  56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
+	  option, where <pun> is the id of the SCSI subsystem (usually 7, but
+	  if that doesn't work check your reference diskette).  Owners of
+	  model 95 with a LED-matrix-display can in addition activate some
+	  activity info like under OS/2, but more informative, by setting
+	  'ibmmcascsi=display' as an additional kernel parameter.  Try "man
+	  bootparam" or see the documentation of your boot loader about how to
+	  pass options to the kernel.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called ibmmca.o.
+
+config IBMMCA_SCSI_ORDER_STANDARD
+	bool "Standard SCSI-order"
+	depends on SCSI_IBMMCA
+	---help---
+	  In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
+	  are assigned to the drive letters, starting with the lowest SCSI-id
+	  (physical number -- pun) to be drive C:, as seen from DOS and
+	  similar operating systems. When looking into papers describing the
+	  ANSI-SCSI-standard, this assignment of drives appears to be wrong.
+	  The SCSI-standard follows a hardware-hierarchy which says that id 7
+	  has the highest priority and id 0 the lowest. Therefore, the host
+	  adapters are still today everywhere placed as SCSI-id 7 by default.
+	  In the SCSI-standard, the drive letters express the priority of the
+	  disk. C: should be the hard disk, or a partition on it, with the
+	  highest priority. This must therefore be the disk with the highest
+	  SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
+	  original definition of the SCSI-standard as also industrial- and
+	  process-control-machines, like VME-CPUs running under realtime-OSes
+	  (e.g. LynxOS, OS9) do.
+
+	  If you like to run Linux on your MCA-machine with the same
+	  assignment of hard disks as seen from e.g. DOS or OS/2 on your
+	  machine, which is in addition conformant to the SCSI-standard, you
+	  must say Y here. This is also necessary for MCA-Linux users who want
+	  to keep downward compatibility to older releases of the
+	  IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
+	  June 1997).
+
+	  If you like to have the lowest SCSI-id assigned as drive C:, as
+	  modern SCSI-BIOSes do, which does not conform to the standard, but
+	  is widespread and common in the PC-world of today, you must say N
+	  here. If unsure, say Y.
+
+config IBMMCA_SCSI_DEV_RESET
+	bool "Reset SCSI-devices at boottime"
+	depends on SCSI_IBMMCA
+	---help---
+	  By default, SCSI-devices are reset when the machine is powered on.
+	  However, some devices exist, like special-control-devices,
+	  SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
+	  not reset when switched on. If you say Y here, each device connected
+	  to your SCSI-bus will be issued a reset-command after it has been
+	  probed, while the kernel is booting. This may cause problems with
+	  more modern devices, like hard disks, which do not appreciate these
+	  reset commands, and can cause your system to hang. So say Y only if
+	  you know that one of your older devices needs it; N is the safe
+	  answer.
+
+config SCSI_IPS
+	tristate "IBM ServeRAID support"
+	depends on X86 && SCSI && PCI
+	---help---
+	  This is support for the IBM ServeRAID hardware RAID controllers.
+	  See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
+	  for more information.  If this driver does not work correctly
+	  without modification please contact the author by email at
+	  ipslinux@us.ibm.com.
+
+	  You can build this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  but only a single instance may be loaded. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+	  The module will be called ips.o.
+
+config SCSI_INITIO
+	tristate "Initio 9100U(W) support"
+	depends on SCSI && PCI
+	help
+	  This is support for the Initio 91XXU(W) SCSI host adapter.  Please
+	  read the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called initio.o.
+
+config SCSI_INIA100
+	tristate "Initio INI-A100U2W support"
+	depends on SCSI && PCI
+	help
+	  This is support for the Initio INI-A100U2W SCSI host adapter.
+	  Please read the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called a100u2w.o.
+
+config SCSI_PPA
+	tristate "IOMEGA parallel port (ppa - older drives)"
+	depends on SCSI && PARPORT
+	---help---
+	  This driver supports older versions of IOMEGA's parallel port ZIP
+	  drive (a 100 MB removable media device).
+
+	  Note that you can say N here if you have the SCSI version of the ZIP
+	  drive: it will be supported automatically if you said Y to the
+	  generic "SCSI disk support", above.
+
+	  If you have the ZIP Plus drive or a more recent parallel port ZIP
+	  drive (if the supplied cable with the drive is labeled "AutoDetect")
+	  then you should say N here and Y to "IOMEGA parallel port (imm -
+	  newer drives)", below.
+
+	  For more information about this driver and how to use it you should
+	  read the file <file:drivers/scsi/README.ppa>.  You should also read
+	  the SCSI-HOWTO, which is available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  If you use this driver,
+	  you will still be able to use the parallel port for other tasks,
+	  such as a printer; it is safe to compile both drivers into the
+	  kernel.
+
+	  This driver is also available as a module which can be inserted in
+	  and removed from the running kernel whenever you want.  To compile
+	  this driver as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called ppa.o.
+
+config SCSI_IMM
+	tristate "IOMEGA parallel port (imm - newer drives)"
+	depends on SCSI && PARPORT
+	---help---
+	  This driver supports newer versions of IOMEGA's parallel port ZIP
+	  drive (a 100 MB removable media device).
+
+	  Note that you can say N here if you have the SCSI version of the ZIP
+	  drive: it will be supported automatically if you said Y to the
+	  generic "SCSI disk support", above.
+
+	  If you have the ZIP Plus drive or a more recent parallel port ZIP
+	  drive (if the supplied cable with the drive is labeled "AutoDetect")
+	  then you should say Y here; if you have an older ZIP drive, say N
+	  here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
+
+	  For more information about this driver and how to use it you should
+	  read the file <file:drivers/scsi/README.ppa>.  You should also read
+	  the SCSI-HOWTO, which is available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  If you use this driver,
+	  you will still be able to use the parallel port for other tasks,
+	  such as a printer; it is safe to compile both drivers into the
+	  kernel.
+
+	  This driver is also available as a module which can be inserted in
+	  and removed from the running kernel whenever you want.  To compile
+	  this driver as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called imm.o.
+
+config SCSI_IZIP_EPP16
+	bool "ppa/imm option - Use slow (but safe) EPP-16"
+	depends on PARPORT && (SCSI_PPA || SCSI_IMM)
+	---help---
+	  EPP (Enhanced Parallel Port) is a standard for parallel ports which
+	  allows them to act as expansion buses that can handle up to 64
+	  peripheral devices.
+
+	  Some parallel port chipsets are slower than their motherboard, and
+	  so we have to control the state of the chipset's FIFO queue every
+	  now and then to avoid data loss. This will be done if you say Y
+	  here.
+
+	  Generally, saying Y is the safe option and slows things down a bit.
+
+config SCSI_IZIP_SLOW_CTR
+	bool "ppa/imm option - Assume slow parport control register"
+	depends on PARPORT && (SCSI_PPA || SCSI_IMM)
+	help
+	  Some parallel ports are known to have excessive delays between
+	  changing the parallel port control register and good data being
+	  available on the parallel port data/status register. This option
+	  forces a small delay (1.0 usec to be exact) after changing the
+	  control register to let things settle out. Enabling this option may
+	  result in a big drop in performance but some very old parallel ports
+	  (found in 386 vintage machines) will not work properly.
+
+	  Generally, saying N is fine.
+
+config SCSI_NCR53C406A
+	tristate "NCR53c406a SCSI support"
+	depends on SCSI && ISA
+	help
+	  This is support for the NCR53c406a SCSI host adapter.  For user
+	  configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
+	  in the kernel source.  Also read the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called NCR53c406.o.
+
+config SCSI_NCR_D700
+	tristate "NCR Dual 700 MCA SCSI support"
+	depends on MCA && SCSI
+	help
+	  This is a driver for the MicroChannel Dual 700 card produced by
+	  NCR and commonly used in 345x/35xx/4100 class machines.  It always
+	  tries to negotiate sync and uses tag command queueing.
+
+	  Unless you have an NCR manufactured machine, the chances are that
+	  you do not have this SCSI card, so say N.
+
+config 53C700_IO_MAPPED
+	bool
+	depends on SCSI_NCR_D700
+	default y
+
+config SCSI_LASI700
+	tristate "HP LASI SCSI support for 53c700/710"
+	depends on PARISC && SCSI
+	help
+	  This is a driver for the lasi baseboard in some parisc machines
+	  which is based on the 53c700 chip.  Will also support LASI subsystems
+	  based on the 710 chip using 700 emulation mode.
+
+	  Unless you know you have a 53c700 or 53c710 based lasi, say N here
+
+config 53C700_MEM_MAPPED
+	bool
+	depends on SCSI_LASI700
+	default y
+
+config 53C700_LE_ON_BE
+	bool
+	depends on SCSI_LASI700
+	default y
+
+config 53C700_USE_CONSISTENT
+	bool
+	depends on SCSI_LASI700
+	default y
+
+config SCSI_NCR53C7xx
+	tristate "NCR53c7,8xx SCSI support"
+	depends on SCSI && PCI
+	---help---
+	  This is a driver for the 53c7 and 8xx NCR family of SCSI
+	  controllers, not to be confused with the NCR 5380 controllers.  It
+	  is explained in section 3.8 of the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/53c7,8xx.h>.  Please read
+	  <file:drivers/scsi/README.ncr53c7xx> for the available boot time
+	  command line options.
+
+	  Note: there is another driver for the 53c8xx family of controllers
+	  ("NCR53C8XX SCSI support" below).  If you want to use them both, you
+	  need to say M to both and build them as modules, but only one may be
+	  active at a time. If you have a 53c8xx board, it's better to use the
+	  other driver.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called 53c7,8xx.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_NCR53C7xx_sync
+	bool "always negotiate synchronous transfers"
+	depends on SCSI_NCR53C7xx
+	help
+	  In general, this is good; however, it is a bit dangerous since there
+	  are some broken SCSI devices out there. Take your chances. Safe bet
+	  is N.
+
+config SCSI_NCR53C7xx_FAST
+	bool "allow FAST-SCSI [10MHz]"
+	depends on SCSI_NCR53C7xx
+	help
+	  This will enable 10MHz FAST-SCSI transfers with your host
+	  adapter. Some systems have problems with that speed, so it's safest
+	  to say N here.
+
+config SCSI_NCR53C7xx_DISCONNECT
+	bool "allow DISCONNECT"
+	depends on SCSI_NCR53C7xx
+	help
+	  This enables the disconnect/reconnect feature of the NCR SCSI
+	  controller. When you say Y here, a slow SCSI device will not lock
+	  the SCSI bus while processing a request, allowing simultaneous use
+	  of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
+	  providing much better performance when using slow and fast SCSI
+	  devices at the same time. Some devices, however, do not operate
+	  properly with this option enabled, and will cause your SCSI system
+	  to hang, which might cause a system crash. The safe answer
+	  therefore is to say N.
+
+config SCSI_SYM53C8XX_2
+	tristate "SYM53C8XX Version 2 SCSI support"
+	depends on PCI && SCSI
+	---help---
+	  This driver supports the whole NCR53C8XX/SYM53C8XX family of 
+	  PCI-SCSI controllers. It also supports the subset of LSI53C10XX 
+	  Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS 
+	  language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI 
+	  controllers.
+
+	  If your system has problems using this new major version of the
+	  SYM53C8XX driver, you may switch back to driver version 1.
+
+	  Please read <file:drivers/scsi/sym53c8xx_2/Documentation.txt> for more
+	  information.
+
+config SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
+	int "DMA addressing mode"
+	depends on SCSI_SYM53C8XX_2
+	default "1"
+	---help---
+	  This option only applies to PCI-SCSI chip that are PCI DAC capable 
+	  (875A, 895A, 896, 1010-33, 1010-66, 1000).
+
+	  When set to 0, only PCI 32 bit DMA addressing (SAC) will be performed.
+	  When set to 1, 40 bit DMA addressing (with upper 24 bits of address 
+	  set to zero) is supported. The addressable range is here 1 TB.
+	  When set to 2, full 64 bits of address for DMA are supported, but only
+	  16 segments of 4 GB can be addressed. The addressable range is so 
+	  limited to 64 GB.
+
+	  The safest value is 0 (32 bit DMA addressing) that is guessed to still 
+	  fit most of real machines.
+
+	  The preferred value 1 (40 bit DMA addressing) should make happy 
+	  properly engineered PCI DAC capable host bridges. You may configure
+	  this option for Intel platforms with more than 4 GB of memory.
+
+	  The still experimental value 2 (64 bit DMA addressing with 16 x 4GB 
+	  segments limitation) can be used on systems that require PCI address 
+	  bits past bit 39 to be set for the addressing of memory using PCI 
+	  DAC cycles.
+
+config SCSI_SYM53C8XX_DEFAULT_TAGS
+	int "default tagged command queue depth"
+	depends on SCSI_SYM53C8XX_2
+	default "16"
+	help
+	  This is the default value of the command queue depth the driver will 
+	  announce to the generic SCSI layer for devices that support tagged 
+	  command queueing. This value can be changed from the boot command line.
+	  This is a soft limit that cannot exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
+
+config SCSI_SYM53C8XX_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_SYM53C8XX_2
+	default "64"
+	help
+	  This option allows you to specify the maximum number of commands
+	  that can be queued to any device, when tagged command queuing is
+	  possible. The driver supports up to 256 queued commands per device.
+	  This value is used as a compiled-in hard limit.
+
+config SCSI_SYM53C8XX_IOMAPPED
+	bool "use normal IO"
+	depends on SCSI_SYM53C8XX_2
+	help
+	  If you say Y here, the driver will preferently use normal IO rather than 
+	  memory mapped IO.
+
+config SCSI_NCR53C8XX
+	tristate "NCR53C8XX SCSI support"
+	depends on PCI && SCSI_SYM53C8XX_2!=y && SCSI
+	---help---
+	  This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
+	  of PCI-SCSI controllers.  This driver supports parity checking,
+	  tagged command queuing and fast synchronous data transfers up to 80
+	  MB/s with wide FAST-40 LVD devices and controllers.
+
+	  Recent versions of the 53C8XX chips are better supported by the
+	  option "SYM53C8XX SCSI support", below.
+
+	  Note: there is yet another driver for the 53c8xx family of
+	  controllers ("NCR53c7,8xx SCSI support" above).  If you want to use
+	  them both, you need to say M to both and build them as modules, but
+	  only one may be active at a time.  If you have a 53c8xx board, you
+	  probably do not want to use the "NCR53c7,8xx SCSI support".
+
+	  Please read <file:drivers/scsi/README.ncr53c8xx> for more
+	  information.
+
+config SCSI_SYM53C8XX
+	tristate "SYM53C8XX SCSI support"
+	depends on PCI && SCSI_SYM53C8XX_2!=y && SCSI
+	---help---
+	  This driver supports all the features of recent 53C8XX chips (used
+	  in PCI SCSI controllers), notably the hardware phase mismatch
+	  feature of the SYM53C896.
+
+	  Older versions of the 53C8XX chips are not supported by this
+	  driver.  If your system uses either a 810 rev. < 16, a 815, or a 825
+	  rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
+	  driver ("NCR53C8XX SCSI support" above) or configure both the
+	  NCR53C8XX and this SYM53C8XX drivers either as module or linked to
+	  the kernel image.
+
+	  When both drivers are linked into the kernel, the SYM53C8XX driver
+	  is called first at initialization and you can use the 'excl=ioaddr'
+	  driver boot option to exclude attachment of adapters by the
+	  SYM53C8XX driver.  For example, entering
+	  'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
+	  adapters at io address 0xb400 and 0xc000 from being attached by the
+	  SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
+	  The 'excl' option is also supported by the NCR53C8XX driver.
+
+	  Please read <file:drivers/scsi/README.ncr53c8xx> for more
+	  information.
+
+config SCSI_NCR53C8XX_DEFAULT_TAGS
+	int "default tagged command queue depth"
+	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX)
+	default "8"
+	---help---
+	  "Tagged command queuing" is a feature of SCSI-2 which improves
+	  performance: the host adapter can send several SCSI commands to a
+	  device's queue even if previous commands haven't finished yet.
+	  Because the device is intelligent, it can optimize its operations
+	  (like head positioning) based on its own request queue. Some SCSI
+	  devices don't implement this properly; if you want to disable this
+	  feature, enter 0 or 1 here (it doesn't matter which).
+
+	  The default value is 8 and should be supported by most hard disks.
+	  This value can be overridden from the boot command line using the
+	  'tags' option as follows (example):
+	  'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
+	  4, set queue depth to 16 for target 2 and target 3 on controller 0
+	  and set queue depth to 10 for target 0 / lun 2 on controller 1.
+
+	  The normal answer therefore is to go with the default 8 and to use
+	  a boot command line option for devices that need to use a different
+	  command queue depth.
+
+	  There is no safe option other than using good SCSI devices.
+
+config SCSI_NCR53C8XX_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX)
+	default "32"
+	---help---
+	  This option allows you to specify the maximum number of commands
+	  that can be queued to any device, when tagged command queuing is
+	  possible. The default value is 32. Minimum is 2, maximum is 64.
+	  Modern hard disks are able to support 64 tags and even more, but
+	  do not seem to be faster when more than 32 tags are being used.
+
+	  So, the normal answer here is to go with the default value 32 unless
+	  you are using very large hard disks with large cache (>= 1 MB) that
+	  are able to take advantage of more than 32 tagged commands.
+
+	  There is no safe option and the default answer is recommended.
+
+config SCSI_NCR53C8XX_SYNC
+	int "synchronous transfers frequency in MHz"
+	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX)
+	default "20"
+	---help---
+	  The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
+	  rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80.  The numbers
+	  are respectively the maximum data transfer rates in mega-transfers
+	  per second for each class.  For example, a FAST-20 Wide 16 device is
+	  able to transfer data at 20 million 16 bit packets per second for a
+	  total rate of 40 MB/s.
+
+	  You may specify 0 if you want to only use asynchronous data
+	  transfers. This is the safest and slowest option. Otherwise, specify
+	  a value between 5 and 80, depending on the capability of your SCSI
+	  controller.  The higher the number, the faster the data transfer.
+	  Note that 80 should normally be ok since the driver decreases the
+	  value automatically according to the controller's capabilities.
+
+	  Your answer to this question is ignored for controllers with NVRAM,
+	  since the driver will get this information from the user set-up.  It
+	  also can be overridden using a boot setup option, as follows
+	  (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
+	  for FAST-20 synchronous data transfer (20 mega-transfers per
+	  second).
+
+	  The normal answer therefore is not to go with the default but to
+	  select the maximum value 80 allowing the driver to use the maximum
+	  value supported by each controller. If this causes problems with
+	  your SCSI devices, you should come back and decrease the value.
+
+	  There is no safe option other than using good cabling, right
+	  terminations and SCSI conformant devices.
+
+config SCSI_NCR53C8XX_PROFILE
+	bool "enable profiling"
+	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX)
+	help
+	  This option allows you to enable profiling information gathering.
+	  These statistics are not very accurate due to the low frequency
+	  of the kernel clock (100 Hz on i386) and have performance impact
+	  on systems that use very fast devices.
+
+	  The normal answer therefore is N.
+
+config SCSI_NCR53C8XX_IOMAPPED
+	bool "use normal IO"
+	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX)
+	help
+	  If you say Y here, the driver will use normal IO, as opposed to
+	  memory mapped IO. Memory mapped IO has less latency than normal IO
+	  and works for most Intel-based hardware. Under Linux/Alpha only
+	  normal IO is currently supported by the driver and so, this option
+	  has no effect on those systems.
+
+	  The normal answer therefore is N; try Y only if you encounter SCSI
+	  related problems.
+
+config SCSI_NCR53C8XX_PQS_PDS
+	bool "include support for the NCR PQS/PDS SCSI card"
+	depends on (SCSI_NCR53C8XX || SCSI_SYM53C8XX) && SCSI_SYM53C8XX
+	help
+	  Say Y here if you have a special SCSI adapter produced by NCR
+	  corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
+	  this if you do not have one of these adapters. However, since this
+	  device is detected as a specific PCI device, this option is quite
+	  safe.
+
+	  The common answer here is N, but answering Y is safe.
+
+config SCSI_NCR53C8XX_NO_DISCONNECT
+	bool "not allow targets to disconnect"
+	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX) && SCSI_NCR53C8XX_DEFAULT_TAGS=0
+	help
+	  This option is only provided for safety if you suspect some SCSI
+	  device of yours to not support properly the target-disconnect
+	  feature. In that case, you would say Y here. In general however, to
+	  not allow targets to disconnect is not reasonable if there is more
+	  than 1 device on a SCSI bus. The normal answer therefore is N.
+
+config SCSI_NCR53C8XX_SYMBIOS_COMPAT
+	bool "assume boards are SYMBIOS compatible (EXPERIMENTAL)"
+	depends on PCI && SCSI_SYM53C8XX_2!=y && (SCSI_NCR53C8XX || SCSI_SYM53C8XX) && EXPERIMENTAL
+	---help---
+	  This option allows you to enable some features depending on GPIO
+	  wiring. These General Purpose Input/Output pins can be used for
+	  vendor specific features or implementation of the standard SYMBIOS
+	  features. Genuine SYMBIOS controllers use GPIO0 in output for
+	  controller LED and GPIO3 bit as a flag indicating
+	  singled-ended/differential interface. The Tekram DC-390U/F boards
+	  uses a different GPIO wiring.
+
+	  Your answer to this question is ignored if all your controllers have
+	  NVRAM, since the driver is able to detect the board type from the
+	  NVRAM format.
+
+	  If all the controllers in your system are genuine SYMBIOS boards or
+	  use BIOS and drivers from SYMBIOS, you would want to say Y here,
+	  otherwise N. N is the safe answer.
+
+config SCSI_MCA_53C9X
+	tristate "NCR MCA 53C9x SCSI support"
+	depends on MCA && SCSI
+	help
+	  Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
+	  controller based on the NCR 53C94.  This driver will allow use of
+	  the controller on the 3550, and very possibly others.
+
+	  If you want to compile this as a module (= code which can be
+	  inserted and removed from the running kernel whenever you want), say
+	  M here and read <file:Documentation/modules.txt>.  The module will
+	  be called mca_53c9x.o.
+
+config SCSI_PAS16
+	tristate "PAS16 SCSI support"
+	depends on SCSI && ISA
+	---help---
+	  This is support for a SCSI host adapter.  It is explained in section
+	  3.10 of the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/pas16.h>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called pas16.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_PCI2000
+	tristate "PCI2000 support"
+	depends on SCSI
+	help
+	  This is support for the PCI2000I EIDE interface card which acts as a
+	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module called pci2000.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want).  If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config SCSI_PCI2220I
+	tristate "PCI2220i support"
+	depends on SCSI
+	help
+	  This is support for the PCI2220i EIDE interface card which acts as a
+	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module called pci2220i.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want).  If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config SCSI_PSI240I
+	tristate "PSI240i support"
+	depends on SCSI && ISA
+	help
+	  This is support for the PSI240i EIDE interface card which acts as a
+	  SCSI host adapter.  Please read the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module called psi240i.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want).  If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config SCSI_QLOGIC_FAS
+	tristate "Qlogic FAS SCSI support"
+	depends on SCSI && ISA
+	---help---
+	  This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
+	  FastSCSI! cards as well as any other card based on the FASXX chip
+	  (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
+
+	  This driver does NOT support the PCI versions of these cards. The
+	  PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
+	  SCSI support"), below.
+
+	  Information about this driver is contained in
+	  <file:drivers/scsi/README.qlogicfas>.  You should also read the
+	  SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called qlogicfas.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_QLOGIC_ISP
+	tristate "Qlogic ISP SCSI support"
+	depends on PCI && SCSI
+	---help---
+	  This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
+	  IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card.  (This latter
+	  card is supported by the "AM53/79C974 PCI SCSI" driver.)
+
+	  If you say Y here, make sure to choose "BIOS" at the question "PCI
+	  access mode".
+
+	  Please read the file <file:drivers/scsi/README.qlogicisp>.  You
+	  should also read the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called qlogicisp.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_QLOGIC_FC
+	tristate "Qlogic ISP FC SCSI support"
+	depends on PCI && SCSI
+	help
+	  This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called qlogicfc.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_QLOGIC_FC_FIRMWARE
+	bool "Include loadable firmware in driver"
+	depends on SCSI_QLOGIC_FC
+
+config SCSI_QLOGIC_1280
+	tristate "Qlogic QLA 1280 SCSI support"
+	depends on PCI && SCSI
+	help
+	  Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called qla1280.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_SEAGATE
+	tristate "Seagate ST-02 and Future Domain TMC-8xx SCSI support"
+	depends on X86 && ISA && SCSI
+	---help---
+	  These are 8-bit SCSI controllers; the ST-01 is also supported by
+	  this driver.  It is explained in section 3.9 of the SCSI-HOWTO,
+	  available from <http://www.linuxdoc.org/docs.html#howto>.  If it
+	  doesn't work out of the box, you may have to change some settings in
+	  <file:drivers/scsi/seagate.h>.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called seagate.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+# definitely looks note 64bit safe:
+config SCSI_SIM710
+	tristate "Simple 53c710 SCSI support (Compaq, NCR machines)"
+	depends on (ISA || MCA && !X86_64) && SCSI
+	---help---
+	  This is a simple driver for NCR53c710 based SCSI host adapters.
+
+	  More complex drivers for this chip are available ("NCR53c7,8xx SCSI
+	  support", above), but they require that the scsi chip be able to do
+	  DMA block moves between memory and on-chip registers, which can
+	  cause problems under certain conditions.  This driver is designed to
+	  avoid these problems and is intended to work with any Intel machines
+	  using 53c710 chips, including various Compaq and NCR machines.
+
+	  Please read the comments at the top of the file
+	  <file:drivers/scsi/sim710.c> for more information.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called sim710.o.
+
+config SCSI_SYM53C416
+	tristate "Symbios 53c416 SCSI support"
+	depends on SCSI && ISA
+	---help---
+	  This is support for the sym53c416 SCSI host adapter, the SCSI
+	  adapter that comes with some HP scanners. This driver requires that
+	  the sym53c416 is configured first using some sort of PnP
+	  configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
+	  are using isapnp then you need to compile this driver as a module
+	  and then load it using insmod after isapnp has run. The parameters
+	  of the configured card(s) should be passed to the driver. The format
+	  is:
+
+	  insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
+
+	  There is support for up to four adapters. If you want to compile
+	  this driver as a module ( = code which can be inserted in and
+	  removed from the running kernel whenever you want), say M here and
+	  read <file:Documentation/modules.txt>. The module will be called
+	  sym53c416.o.
+
+config SCSI_DC390T
+	tristate "Tekram DC390(T) and Am53/79C974 SCSI support"
+	depends on PCI && SCSI
+	---help---
+	  This driver supports PCI SCSI host adapters based on the Am53C974A
+	  chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
+	  PCscsi/PCnet (Am53/79C974) solutions.
+
+	  Documentation can be found in <file:drivers/scsi/README.tmscsim>.
+
+	  Note that this driver does NOT support Tekram DC390W/U/F, which are
+	  based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
+	  Also note that there is another generic Am53C974 driver,
+	  "AM53/79C974 PCI SCSI support" below.  You can pick either one.
+
+	  If you want to compile this driver as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called tmscsim.o.
+
+config SCSI_DC390T_NOGENSUPP
+	bool "_omit_ support for non-DC390 adapters"
+	depends on SCSI_DC390T
+	---help---
+	  If you say N here, the DC390(T) SCSI driver relies on the DC390
+	  EEPROM to get initial values for its settings, such as speed,
+	  termination, etc.  If it can't find this EEPROM, it will use
+	  defaults or the user supplied boot/module parameters.  For details
+	  on driver configuration see <file:drivers/scsi/README.tmscsim>.
+
+	  If you say Y here and if no EEPROM is found, the driver gives up and
+	  thus only supports Tekram DC390(T) adapters.  This can be useful if
+	  you have a DC390(T) and another Am53C974 based adapter, which, for
+	  some reason, you want to drive with the other AM53C974 driver.
+
+	  If unsure, say N.
+
+config SCSI_T128
+	tristate "Trantor T128/T128F/T228 SCSI support"
+	depends on SCSI && ISA
+	---help---
+	  This is support for a SCSI host adapter. It is explained in section
+	  3.11 of the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/t128.h>.  Note that Trantor was purchased by
+	  Adaptec, and some former Trantor products are being sold under the
+	  Adaptec name.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called t128.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_U14_34F
+	tristate "UltraStor 14F/34F support"
+	depends on SCSI
+	---help---
+	  This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
+	  The source at <file:drivers/scsi/u14-34f.c> contains some
+	  information about this hardware.  If the driver doesn't work out of
+	  the box, you may have to change some settings in
+	  <file: drivers/scsi/u14-34f.c>.  Read the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  Note that there is also
+	  another driver for the same hardware: "UltraStor SCSI support",
+	  below.  You should say Y to both only if you want 24F support as
+	  well.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called u14-34f.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_U14_34F_LINKED_COMMANDS
+	bool "enable elevator sorting"
+	depends on SCSI_U14_34F
+	help
+	  This option enables elevator sorting for all probed SCSI disks and
+	  CD-ROMs. It definitely reduces the average seek distance when doing
+	  random seeks, but this does not necessarily result in a noticeable
+	  performance improvement: your mileage may vary...
+
+	  The safe answer is N.
+
+config SCSI_U14_34F_MAX_TAGS
+	int "maximum number of queued commands"
+	depends on SCSI_U14_34F
+	default "8"
+	help
+	  This specifies how many SCSI commands can be maximally queued for
+	  each probed SCSI device. You should reduce the default value of 8
+	  only if you have disks with buggy or limited tagged command support.
+	  Minimum is 2 and maximum is 14. This value is also the window size
+	  used by the elevator sorting option above. The effective value used
+	  by the driver for each probed SCSI device is reported at boot time.
+
+config SCSI_ULTRASTOR
+	tristate "UltraStor SCSI support"
+	depends on X86 && ISA && SCSI
+	---help---
+	  This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
+	  adapter family.  This driver is explained in section 3.12 of the
+	  SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.  If it doesn't work out
+	  of the box, you may have to change some settings in
+	  <file:drivers/scsi/ultrastor.h>.
+
+	  Note that there is also another driver for the same hardware:
+	  "UltraStor 14F/34F support", above.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called ultrastor.o.
+
+config SCSI_NSP32
+	tristate "Workbit NinjaSCSI-32Bi/UDE support"
+	depends on SCSI
+	help
+	  This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
+	  SCSI host adapter. Please read the SCSI-HOWTO, available from
+	  <http://www.linuxdoc.org/docs.html#howto>.
+
+	  If you want to compile this as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want),
+	  say M here and read <file:Documentation/modules.txt>.  The module
+	  will be called nsp32.o.
+
+#
+# Note - this is a very special 'host' adapter that simulates the presence of some disks.
+# It can come in very handy for troubleshooting.  Anyone else is welcome to use it - all
+# you do is hack it to simulate the condition you want to test for, and then use it.
+#
+# The actual configuration in any kernel release could change at any time as I hack it to
+# simulate various conditions that I am testing.
+#
+config SCSI_DEBUG
+	tristate "SCSI debugging host simulator (EXPERIMENTAL)"
+	depends on EXPERIMENTAL && SCSI
+	help
+	  This is a host adapter simulator that can be programmed to simulate
+	  a large number of conditions that could occur on a real bus. The
+	  advantage is that many hard to reproduce problems can be tested in a
+	  controlled environment where there is reduced risk of losing
+	  important data. This is primarily of use to people trying to debug
+	  the middle and upper layers of the SCSI subsystem. If unsure, say N.
+
+config SCSI_MESH
+	tristate "MESH (Power Mac internal SCSI) support"
+	depends on ALL_PPC && SCSI
+	help
+	  Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
+	  SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
+	  other Power Macintoshes do). Say Y to include support for this SCSI
+	  adaptor. This driver is also available as a module called mesh.o
+	  ( = code which can be inserted in and removed from the running
+	  kernel whenever you want). If you want to compile it as a module,
+	  say M here and read <file:Documentation/modules.txt>.
+
+config SCSI_MESH_SYNC_RATE
+	int "maximum synchronous transfer rate (MB/s) (0 = async)"
+	depends on SCSI_MESH
+	default "5"
+	help
+	  On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
+	  drives a bus which is entirely internal to the machine (such as the
+	  7500, 7600, 8500, etc.), the MESH is capable of synchronous
+	  operation at up to 10 MB/s. On machines where the SCSI bus
+	  controlled by the MESH can have external devices connected, it is
+	  usually rated at 5 MB/s. 5 is a safe value here unless you know the
+	  MESH SCSI bus is internal only; in that case you can say 10. Say 0
+	  to disable synchronous operation.
+
+config SCSI_MESH_RESET_DELAY_MS
+	int "initial bus reset delay (ms) (0 = no reset)"
+	depends on SCSI_MESH
+	default "4000"
+
+config SCSI_MAC53C94
+	tristate "53C94 (Power Mac external SCSI) support"
+	depends on ALL_PPC && SCSI
+	help
+	  On Power Macintoshes (and clones) with two SCSI buses, the external
+	  SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
+	  machines which only have one SCSI bus, such as the 7200, also use
+	  the 53C94. Say Y to include support for the 53C94.
+
+	  This driver is also available as a module called mac53c94.o ( = code
+	  which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+source "drivers/acorn/scsi/Kconfig"
+
+config JAZZ_ESP
+	bool "MIPS JAZZ FAS216 SCSI support"
+	depends on MIPS_JAZZ
+	help
+	  This is the driver for the onboard SCSI host adapter of MIPS Magnum
+	  4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
+	  systems.
+
+config A3000_SCSI
+	tristate "A3000 WD33C93A support"
+	depends on AMIGA && SCSI
+	help
+	  If you have an Amiga 3000 and have SCSI devices connected to the
+	  built-in SCSI controller, say Y. Otherwise, say N. This driver is
+	  also available as a module ( = code which can be inserted in and
+	  removed from the running kernel whenever you want). The module is
+	  called wd33c93.o. If you want to compile it as a module, say M here
+	  and read <file:Documentation/modules.txt>.
+
+config A4000T_SCSI
+	bool "A4000T SCSI support (EXPERIMENTAL)"
+	depends on AMIGA && EXPERIMENTAL
+	help
+	  Support for the NCR53C710 SCSI controller on the Amiga 4000T.
+
+config A2091_SCSI
+	tristate "A2091/A590 WD33C93A support"
+	depends on ZORRO && SCSI
+	help
+	  If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
+	  say N. This driver is also available as a module ( = code which can
+	  be inserted in and removed from the running kernel whenever you
+	  want). The module is called wd33c93.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config GVP11_SCSI
+	tristate "GVP Series II WD33C93A support"
+	depends on ZORRO && SCSI
+	---help---
+	  If you have a Great Valley Products Series II SCSI controller,
+	  answer Y. Also say Y if you have a later model of GVP SCSI
+	  controller (such as the GVP A4008 or a Combo board). Otherwise,
+	  answer N. This driver does NOT work for the T-Rex series of
+	  accelerators from TekMagic and GVP-M.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you
+	  want). The module will be called gvp11.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config CYBERSTORM_SCSI
+	tristate "CyberStorm SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with an original (MkI) Phase5 Cyberstorm
+	  accelerator board and the optional Cyberstorm SCSI controller,
+	  answer Y. Otherwise, say N.
+
+config CYBERSTORMII_SCSI
+	tristate "CyberStorm Mk II SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
+	  and the optional Cyberstorm SCSI controller, say Y. Otherwise,
+	  answer N.
+
+config BLZ2060_SCSI
+	tristate "Blizzard 2060 SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
+	  and want to use the onboard SCSI controller, say Y. Otherwise,
+	  answer N.
+
+config BLZ1230_SCSI
+	tristate "Blizzard 1230IV/1260 SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
+	  1260 accelerator, and the optional SCSI module, say Y. Otherwise,
+	  say N.
+
+config FASTLANE_SCSI
+	tristate "Fastlane SCSI support"
+	depends on ZORRO && SCSI
+	help
+	  If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
+	  one in the near future, say Y to this question. Otherwise, say N.
+
+config A4091_SCSI
+	bool "A4091 SCSI support (EXPERIMENTAL)"
+	depends on ZORRO && EXPERIMENTAL
+	help
+	  Support for the NCR53C710 chip on the Amiga 4091 Z3 SCSI2 controller
+	  (1993).  Very obscure -- the 4091 was part of an Amiga 4000 upgrade
+	  plan at the time the Amiga business was sold to DKB.
+
+config WARPENGINE_SCSI
+	bool "WarpEngine SCSI support (EXPERIMENTAL)"
+	depends on ZORRO && EXPERIMENTAL
+	help
+	  Support for MacroSystem Development's WarpEngine Amiga SCSI-2
+	  controller. Info at
+	  <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>.
+
+config BLZ603EPLUS_SCSI
+	bool "Blizzard PowerUP 603e+ SCSI (EXPERIMENTAL)"
+	depends on ZORRO && EXPERIMENTAL
+	help
+	  If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
+	  accelerator, say Y. Otherwise, say N.
+
+config OKTAGON_SCSI
+	tristate "BSC Oktagon SCSI support (EXPERIMENTAL)"
+	depends on ZORRO && EXPERIMENTAL && SCSI
+	help
+	  If you have the BSC Oktagon SCSI disk controller for the Amiga, say
+	  Y to this question.  If you're in doubt about whether you have one,
+	  see the picture at
+	  <http://amiga.multigraph.com/photos/oktagon.html>.
+
+#      bool 'Cyberstorm Mk III SCSI support (EXPERIMENTAL)' CONFIG_CYBERSTORMIII_SCSI
+#      bool 'GVP Turbo 040/060 SCSI support (EXPERIMENTAL)' CONFIG_GVP_TURBO_SCSI
+endmenu
+
+source "drivers/scsi/pcmcia/Kconfig"
+

drivers/scsi/aic7xxx/Kconfig

+config SCSI_AIC7XXX
+	tristate "New driver"
+	help
+	  This driver supports all of Adaptec's PCI based SCSI controllers
+	  (not the hardware RAID controllers though) as well as the aic7770
+	  based EISA and VLB SCSI controllers (the 274x and 284x series).
+	  This is an Adaptec sponsored driver written by Justin Gibbs.  It is
+	  intended to replace the previous aic7xxx driver maintained by Doug
+	  Ledford since Doug is no longer maintaining that driver.
+
+
+config AIC7XXX_CMDS_PER_DEVICE
+	int "Maximum number of TCQ commands per device"
+	depends on SCSI_AIC7XXX
+	default "253"
+	---help---
+	  Specify the number of commands you would like to allocate per SCSI
+	  device when Tagged Command Queueing (TCQ) is enabled on that device.
+
+	  This is an upper bound value for the number of tagged transactions
+	  to be used for any device.  The aic7xxx driver will automatically
+	  vary this number based on device behavior.  For devices with a
+	  fixed maximum, the driver will eventually lock to this maximum
+	  and display a console message inidicating this value.
+
+	  Note: Unless you experience some type of device failure, the default
+	  	value, no enforced limit, should work for you.
+
+	  Default: 253
+
+config AIC7XXX_RESET_DELAY_MS
+	int "Initial bus reset delay in milli-seconds"
+	depends on SCSI_AIC7XXX
+	default "15000"
+	help
+	  The number of milliseconds to delay after an initial bus reset.
+	  The bus settle delay following all error recovery actions is
+	  dictated by the SCSI layer and is not affected by this value.
+
+	  Default: 15000 (15 seconds)
+
+config AIC7XXX_BUILD_FIRMWARE
+	bool "Build Adapter Firmware with Kernel Build"
+	depends on SCSI_AIC7XXX
+	help
+	  This option should only be enabled if you are modifying the firmware
+	  source to the aic7xxx driver and wish to have the generated firmware
+	  include files updated during a normal kernel build.  The assembler
+	  for the firmware requires lex and yacc or their equivalents, as well
+	  as the db v1 library.  You may have to install additional packages
+	  or modify the assembler make file or the files it includes if your
+	  build environment is different than that of the author.
+

drivers/scsi/pcmcia/Kconfig

+#
+# PCMCIA SCSI adapter configuration
+#
+
+menu "PCMCIA SCSI adapter support"
+	depends on SCSI!=n && HOTPLUG && PCMCIA!=n
+
+config SCSI_PCMCIA
+	bool "PCMCIA SCSI adapter support"
+	help
+	  Say Y here if you intend to attach a PCMCIA or CardBus card to your
+	  computer which acts as a SCSI host adapter. These are credit card
+	  size devices often used with laptops.
+
+	  Note that the answer to this question won't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions PCMCIA SCSI host adapters.
+
+config PCMCIA_AHA152X
+	tristate "Adaptec AHA152X PCMCIA support"
+	depends on SCSI_PCMCIA && m
+	help
+	  Say Y here if you intend to attach this type of PCMCIA SCSI host
+	  adapter to your computer.
+
+	  This driver is also available as a module called aha152x_cs.o ( =
+	  code which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config PCMCIA_FDOMAIN
+	tristate "Future Domain PCMCIA support"
+	depends on SCSI_PCMCIA && m
+	help
+	  Say Y here if you intend to attach this type of PCMCIA SCSI host
+	  adapter to your computer.
+
+	  This driver is also available as a module called fdomain_cs.o ( =
+	  code which can be inserted in and removed from the running kernel
+	  whenever you want).  If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config PCMCIA_NINJA_SCSI
+	tristate "NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support"
+	depends on SCSI_PCMCIA && m
+	help
+	  If you intend to attach this type of PCMCIA SCSI host adapter to
+	  your computer, say Y here and read
+	  <file:Documentation/README.nsp_cs.eng>.
+
+	  This driver is also available as a module called nsp_cs.o ( =
+	  code which can be inserted in and removed from the running kernel
+	  whenever you want). If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config PCMCIA_QLOGIC
+	tristate "Qlogic PCMCIA support"
+	depends on SCSI_PCMCIA && m
+	help
+	  Say Y here if you intend to attach this type of PCMCIA SCSI host
+	  adapter to your computer.
+
+	  This driver is also available as a module called qlogic_cs.o ( =
+	  code which can be inserted in and removed from the running kernel
+	  whenever you want).  If you want to compile it as a module, say M
+	  here and read <file:Documentation/modules.txt>.
+
+config PCMCIA_SCSICARD
+	bool
+	depends on PCMCIA_QLOGIC=y || PCMCIA_AHA152X=y || PCMCIA_FDOMAIN=y || PCMCIA_NINJA_SCSI=y
+	default y
+
+endmenu
+

drivers/serial/Kconfig

+#
+# Serial device configuration
+#
+# $Id: Config.in,v 1.15 2002/07/06 17:16:24 rmk Exp $
+#
+
+menu "Serial drivers"
+
+#
+# The new 8250/16550 serial drivers
+config SERIAL_8250
+	tristate "8250/16550 and compatible serial support (EXPERIMENTAL)"
+	depends on EXPERIMENTAL
+	---help---
+	  This selects whether you want to include the driver for the standard
+	  serial ports.  The standard answer is Y.  People who might say N
+	  here are those that are setting up dedicated Ethernet WWW/FTP
+	  servers, or users that have one of the various bus mice instead of a
+	  serial mouse and don't intend to use their machine's standard serial
+	  port for anything.  (Note that the Cyclades and Stallion multi
+	  serial port drivers do not need this driver built in for them to
+	  work.)
+
+	  If you want to compile this driver as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  serial.o.
+	  [WARNING: Do not compile this driver as a module if you are using
+	  non-standard serial ports, since the configuration information will
+	  be lost when the driver is unloaded.  This limitation may be lifted
+	  in the future.]
+
+	  BTW1: If you have a mouseman serial mouse which is not recognized by
+	  the X window system, try running gpm first.
+
+	  BTW2: If you intend to use a software modem (also called Winmodem)
+	  under Linux, forget it.  These modems are crippled and require
+	  proprietary drivers which are only available under Windows.
+
+	  Most people will say Y or M here, so that they can use serial mice,
+	  modems and similar devices connecting to the standard serial ports.
+
+config SERIAL_8250_CONSOLE
+	bool "Console on 8250/16550 and compatible serial port (EXPERIMENTAL)"
+	depends on SERIAL_8250=y
+	---help---
+	  If you say Y here, it will be possible to use a serial port as the
+	  system console (the system console is the device which receives all
+	  kernel messages and warnings and which allows logins in single user
+	  mode). This could be useful if some terminal or printer is connected
+	  to that serial port.
+
+	  Even if you say Y here, the currently visible virtual console
+	  (/dev/tty0) will still be used as the system console by default, but
+	  you can alter that using a kernel command line option such as
+	  "console=ttyS1". (Try "man bootparam" or see the documentation of
+	  your boot loader (lilo or loadlin) about how to pass options to the
+	  kernel at boot time.)
+
+	  If you don't have a VGA card installed and you say Y here, the
+	  kernel will automatically use the first serial line, /dev/ttyS0, as
+	  system console.
+
+	  If unsure, say N.
+
+config SERIAL_8250_CS
+	tristate "8250/16550 PCMCIA device support"
+	depends on PCMCIA && SERIAL_8250
+	---help---
+	  Say Y here to enable support for 16-bit PCMCIA serial devices,
+	  including serial port cards, modems, and the modem functions of
+	  multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are
+	  credit-card size devices often used with laptops.)
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called serial_cs.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+	  If unsure, say N.
+
+config SERIAL_8250_EXTENDED
+	bool "Extended 8250/16550 serial driver options"
+	depends on SERIAL_8250
+	help
+	  If you wish to use any non-standard features of the standard "dumb"
+	  driver, say Y here. This includes HUB6 support, shared serial
+	  interrupts, special multiport support, support for more than the
+	  four COM 1/2/3/4 boards, etc.
+
+	  Note that the answer to this question won't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions about serial driver options. If unsure, say N.
+
+config SERIAL_8250_MANY_PORTS
+	bool "Support more than 4 serial ports"
+	depends on SERIAL_8250_EXTENDED
+	help
+	  Say Y here if you have dumb serial boards other than the four
+	  standard COM 1/2/3/4 ports. This may happen if you have an AST
+	  FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
+	  from <http://www.linuxdoc.org/docs.html#howto>), or other custom
+	  serial port hardware which acts similar to standard serial port
+	  hardware. If you only use the standard COM 1/2/3/4 ports, you can
+	  say N here to save some memory. You can also say Y if you have an
+	  "intelligent" multiport card such as Cyclades, Digiboards, etc.
+
+config SERIAL_8250_SHARE_IRQ
+	bool "Support for sharing serial interrupts"
+	depends on SERIAL_8250_EXTENDED
+	help
+	  Some serial boards have hardware support which allows multiple dumb
+	  serial ports on the same board to share a single IRQ. To enable
+	  support for this in the serial driver, say Y here.
+
+config SERIAL_8250_DETECT_IRQ
+	bool "Autodetect IRQ on standard ports (unsafe)"
+	depends on SERIAL_8250_EXTENDED
+	help
+	  Say Y here if you want the kernel to try to guess which IRQ
+	  to use for your serial port.
+
+	  This is considered unsafe; it is far better to configure the IRQ in
+	  a boot script using the setserial command.
+
+	  If unsure, say N.
+
+config SERIAL_8250_MULTIPORT
+	bool "Support special multiport boards"
+	depends on SERIAL_8250_EXTENDED
+	help
+	  Some multiport serial ports have special ports which are used to
+	  signal when there are any serial ports on the board which need
+	  servicing. Say Y here to enable the serial driver to take advantage
+	  of those special I/O ports.
+
+config SERIAL_8250_RSA
+	bool "Support RSA serial ports"
+	depends on SERIAL_8250_EXTENDED
+	help
+	  ::: To be written :::
+
+comment "Non-8250 serial port support"
+
+config SERIAL_8250_ACORN
+	tristate "Acorn expansion card serial port support"
+	depends on ARM && ARCH_ACORN && SERIAL_8250
+	help
+	  If you have an Atomwide Serial card or Serial Port card for an Acorn
+	  system, say Y to this option.  The driver can handle 1, 2, or 3 port
+	  cards.  If unsure, say N.
+
+config SERIAL_ANAKIN
+	bool "Anakin serial port support"
+	depends on ARM && ARCH_ANAKIN
+	help
+	  ::: To be written :::
+
+config SERIAL_ANAKIN_CONSOLE
+	bool "Console on Anakin serial port"
+	depends on SERIAL_ANAKIN
+	help
+	  Even if you say Y here, the currently visible virtual console
+	  (/dev/tty0) will still be used as the system console by default, but
+	  you can alter that using a kernel command line option such as
+	  "console=ttyAN0". (Try "man bootparam" or see the documentation of
+	  your boot loader (lilo or loadlin) about how to pass options to the
+	  kernel at boot time.)
+
+config ANAKIN_DEFAULT_BAUDRATE
+	int "Default Anakin serial baudrate"
+	depends on SERIAL_ANAKIN
+	default "9600"
+	help
+	  ::: To be written :::
+
+config SERIAL_AMBA
+	tristate "ARM AMBA serial port support"
+	depends on ARM && ARCH_INTEGRATOR
+	help
+	  This selects the ARM(R) AMBA(R) PrimeCell UART.  If you have an
+	  Integrator platform, say Y or M here.
+
+	  If unsure, say N.
+
+config SERIAL_AMBA_CONSOLE
+	bool "Support for console on AMBA serial port"
+	depends on SERIAL_AMBA=y
+	---help---
+	  Say Y here if you wish to use an AMBA PrimeCell UART as the system
+	  console (the system console is the device which receives all kernel
+	  messages and warnings and which allows logins in single user mode).
+
+	  Even if you say Y here, the currently visible framebuffer console
+	  (/dev/tty0) will still be used as the system console by default, but
+	  you can alter that using a kernel command line option such as
+	  "console=ttyAM0". (Try "man bootparam" or see the documentation of
+	  your boot loader (lilo or loadlin) about how to pass options to the
+	  kernel at boot time.)
+
+config SERIAL_INTEGRATOR
+	bool
+	depends on SERIAL_AMBA=y
+	default y
+
+config SERIAL_CLPS711X
+	tristate "CLPS711X serial port support"
+	depends on ARM && ARCH_CLPS711X
+	help
+	  ::: To be written :::
+
+config SERIAL_CLPS711X_CONSOLE
+	bool "Support for console on CLPS711X serial port"
+	depends on SERIAL_CLPS711X=y
+	help
+	  Even if you say Y here, the currently visible virtual console
+	  (/dev/tty0) will still be used as the system console by default, but
+	  you can alter that using a kernel command line option such as
+	  "console=ttyCL1". (Try "man bootparam" or see the documentation of
+	  your boot loader (lilo or loadlin) about how to pass options to the
+	  kernel at boot time.)
+
+config SERIAL_CLPS711X_OLD_NAME
+	bool "Use the old 2.4 names for CLPS711X serial port"
+	depends on SERIAL_CLPS711X=y
+	help
+	  ::: To be written :::
+
+config SERIAL_21285
+	tristate "DC21285 serial port support"
+	depends on ARM && FOOTBRIDGE
+	help
+	  If you have a machine based on a 21285 (Footbridge) StrongARM(R)/
+	  PCI bridge you can enable its onboard serial port by enabling this
+	  option.
+
+config SERIAL_21285_OLD
+	bool "Use /dev/ttyS0 device (OBSOLETE)"
+	depends on SERIAL_21285=y && OBSOLETE
+	help
+	  Use the old /dev/ttyS name, major 4 minor 64.  This is obsolete
+	  and will be removed during later 2.5 development.
+
+config SERIAL_21285_CONSOLE
+	bool "Console on DC21285 serial port"
+	depends on SERIAL_21285=y
+	help
+	  If you have enabled the serial port on the 21285 footbridge you can
+	  make it the console by answering Y to this option.
+
+	  Even if you say Y here, the currently visible virtual console
+	  (/dev/tty0) will still be used as the system console by default, but
+	  you can alter that using a kernel command line option such as
+	  "console=ttyFB". (Try "man bootparam" or see the documentation of
+	  your boot loader (lilo or loadlin) about how to pass options to the
+	  kernel at boot time.)
+
+config SERIAL_UART00
+	bool "Excalibur serial port (uart00) support"
+	depends on ARM && ARCH_CAMELOT
+	help
+	  Say Y here if you want to use the hard logic uart on Excalibur. This
+	  driver also supports soft logic implentations of this uart core.
+
+config SERIAL_UART00_CONSOLE
+	bool "Support for console on Excalibur serial port"
+	depends on SERIAL_UART00
+	help
+	  Say Y here if you want to support a serial console on an Excalibur
+	  hard logic uart or uart00 IP core.
+
+	  Even if you say Y here, the currently visible virtual console
+	  (/dev/tty0) will still be used as the system console by default, but
+	  you can alter that using a kernel command line option such as
+	  "console=ttyS1". (Try "man bootparam" or see the documentation of
+	  your boot loader (lilo or loadlin) about how to pass options to the
+	  kernel at boot time.)
+
+config SERIAL_SA1100
+	bool "SA1100 serial port support"
+	depends on ARM && ARCH_SA1100
+	help
+	  If you have a machine based on a SA1100/SA1110 StrongARM(R) CPU you
+	  can enable its onboard serial port by enabling this option.
+	  Please read <file:Documentation/arm/SA1100/serial_UART> for further
+	  info.
+
+config SERIAL_SA1100_CONSOLE
+	bool "Console on SA1100 serial port"
+	depends on SERIAL_SA1100
+	help
+	  If you have enabled the serial port on the SA1100/SA1110 StrongARM
+	  CPU you can make it the console by answering Y to this option.
+
+	  Even if you say Y here, the currently visible virtual console
+	  (/dev/tty0) will still be used as the system console by default, but
+	  you can alter that using a kernel command line option such as
+	  "console=ttySA0". (Try "man bootparam" or see the documentation of
+	  your boot loader (lilo or loadlin) about how to pass options to the
+	  kernel at boot time.)
+
+config SERIAL_SUNCORE
+	bool
+	depends on SPARC32 || SPARC64
+	default y
+
+config SERIAL_SUNZILOG
+	tristate "Sun Zilog8530 serial support"
+	depends on SPARC32 || SPARC64
+	help
+	  This driver supports the Zilog8530 serial ports found on many Sparc
+	  systems.  Say Y or M if you want to be able to these serial ports.
+
+config SERIAL_SUNSU
+	tristate "Sun SU serial support"
+	depends on (SPARC32 || SPARC64) && PCI
+	help
+	  This driver supports the 8250 serial ports that run the keyboard and
+	  mouse on (PCI) UltraSPARC systems.  Say Y or M if you want to be able
+	  to these serial ports.
+
+config SERIAL_SUNSAB
+	tristate "Sun Siemens SAB82532 serial support"
+	depends on (SPARC32 || SPARC64) && PCI
+	help
+	  This driver supports the Siemens SAB82532 DUSCC serial ports on newer
+	  (PCI) UltraSPARC systems.  Say Y or M if you want to be able to these
+	  serial ports.
+
+config SERIAL_CORE
+	tristate
+	default m if SERIAL_AMBA!=y && SERIAL_CLPS711X!=y && SERIAL_21285!=y && !SERIAL_SA1100 && !SERIAL_ANAKIN && !SERIAL_UART00 && SERIAL_8250!=y && !SERIAL_ROCKETPORT && !SERIAL_SUNCORE && (SERIAL_AMBA=m || SERIAL_CLPS711X=m || SERIAL_21285=m || SERIAL_8250=m)
+	default y if SERIAL_AMBA=y || SERIAL_CLPS711X=y || SERIAL_21285=y || SERIAL_SA1100 || SERIAL_ANAKIN || SERIAL_UART00 || SERIAL_8250=y || SERIAL_ROCKETPORT || SERIAL_SUNCORE
+
+config SERIAL_CORE_CONSOLE
+	bool
+	depends on SERIAL_AMBA_CONSOLE || SERIAL_CLPS711X_CONSOLE || SERIAL_21285_CONSOLE || SERIAL_SA1100_CONSOLE || SERIAL_ANAKIN_CONSOLE || SERIAL_UART00_CONSOLE || SERIAL_8250_CONSOLE || SERIAL_SUNCORE
+	default y
+
+endmenu
+

drivers/sgi/Kconfig

+#
+# Character device configuration
+#
+
+menu "SGI devices"
+	depends on SGI_IP22
+
+config SGI_SERIAL
+	bool "SGI Zilog85C30 serial support"
+	help
+	  If you want to use your SGI's built-in serial ports under Linux,
+	  answer Y.
+
+config SERIAL_CONSOLE
+	bool "Support for console on serial port"
+	depends on SGI_SERIAL
+	---help---
+	  If you say Y here, it will be possible to use a serial port as the
+	  system console (the system console is the device which receives all
+	  kernel messages and warnings and which allows logins in single user
+	  mode). This could be useful if some terminal or printer is connected
+	  to that serial port.
+
+	  Even if you say Y here, the currently visible virtual console
+	  (/dev/tty0) will still be used as the system console by default, but
+	  you can alter that using a kernel command line option such as
+	  "console=ttyS1". (Try "man bootparam" or see the documentation of
+	  your boot loader (lilo or loadlin) about how to pass options to the
+	  kernel at boot time.)
+
+	  If you don't have a VGA card installed and you say Y here, the
+	  kernel will automatically use the first serial line, /dev/ttyS0, as
+	  system console.
+
+	  If unsure, say N.
+
+config SGI_DS1286
+	bool "SGI DS1286  RTC support"
+	help
+	  If you say Y here and create a character special file /dev/rtc with
+	  major number 10 and minor number 135 using mknod ("man mknod"), you
+	  will get access to the real time clock built into your computer.
+	  Every SGI has such a clock built in. It reports status information
+	  via the file /proc/rtc and its behaviour is set by various ioctls on
+	  /dev/rtc.
+
+config SGI_NEWPORT_GFX
+	tristate "SGI Newport Graphics support (EXPERIMENTAL)"
+	depends on EXPERIMENTAL
+	help
+	  If you have an SGI machine and you want to compile the graphics
+	  drivers, say Y here. This will include the code for the
+	  /dev/graphics and /dev/gfx drivers into the kernel for supporting
+	  virtualized access to your graphics hardware.
+
+endmenu
+

drivers/telephony/Kconfig

+#
+# Telephony device configuration
+#
+
+menu "Telephony Support"
+
+config PHONE
+	tristate "Linux telephony support"
+	---help---
+	  Say Y here if you have a telephony card, which for example allows
+	  you to use a regular phone for voice-over-IP applications.
+
+	  Note: this has nothing to do with modems.  You do not need to say Y
+	  here in order to be able to use a modem under Linux.
+
+	  This support is also available as a module.  If you want to compile
+	  it as a module, say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  phonedev.o.
+
+config PHONE_IXJ
+	tristate "QuickNet Internet LineJack/PhoneJack support"
+	depends on PHONE
+	---help---
+	  Say M if you have a telephony card manufactured by Quicknet
+	  Technologies, Inc.  These include the Internet PhoneJACK and
+	  Internet LineJACK Telephony Cards. You will get a module called
+	  ixj.o.
+
+	  For the ISA versions of these products, you can configure the
+	  cards using the isapnp tools (pnpdump/isapnp) or you can use the
+	  isapnp support.  Please read <file:Documentation/telephony/ixj.txt>.
+
+	  For more information on these cards, see Quicknet's web site at:
+	  <http://www.quicknet.net/>.
+
+	  If you do not have any Quicknet telephony cards, you can safely
+	  say N here.
+
+config PHONE_IXJ_PCMCIA
+	tristate "QuickNet Internet LineJack/PhoneJack PCMCIA support"
+	depends on PHONE_IXJ
+	help
+	  Say Y here to configure in PCMCIA service support for the Quicknet
+	  cards manufactured by Quicknet Technologies, Inc.  This changes the
+	  card initialization code to work with the card manager daemon.
+
+endmenu
+

drivers/usb/Kconfig

+#
+# USB device configuration
+#
+
+menu "USB support"
+
+# ARM SA1111 chips have a non-PCI based "OHCI-compatible" USB host interface.
+config USB
+	tristate "Support for USB"
+	depends on PCI || SA1111
+	---help---
+	  Universal Serial Bus (USB) is a specification for a serial bus
+	  subsystem which offers higher speeds and more features than the
+	  traditional PC serial port.  The bus supplies power to peripherals
+	  and allows for hot swapping.  Up to 127 USB peripherals can be
+	  connected to a single USB port in a tree structure.  The USB port is
+	  the root of the tree, the peripherals are the leaves and the inner
+	  nodes are special USB devices called hubs.  Many newer PC's have USB
+	  ports and newer peripherals such as scanners, keyboards, mice,
+	  modems, and printers support the USB protocol and can be connected
+	  to the PC via those ports.
+
+	  Say Y here if your computer has a USB port and you want to use USB
+	  devices.  You then need to say Y to at least one of "UHCI HCD support"
+	  or "OHCI HCD support" below (the type of interface that the USB hardware
+	  in your computer provides to the operating system) and then choose
+	  from amongst the drivers for USB peripherals.  You may want to check
+	  out the information provided in <file:Documentation/usb/> and
+	  especially the links given in <file:Documentation/usb/usb-help.txt>.
+
+	  If you have a new USB 2.0 High Speed system, you should also choose
+	  "EHCI HCD (USB 2.0) support" as well as at least one of UHCI or OHCI.
+
+	  It doesn't normally hurt to select them all if you are not certain.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called usbcore.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+source "drivers/usb/core/Kconfig"
+
+source "drivers/usb/host/Kconfig"
+
+source "drivers/usb/class/Kconfig"
+
+source "drivers/usb/storage/Kconfig"
+
+source "drivers/usb/input/Kconfig"
+
+source "drivers/usb/image/Kconfig"
+
+source "drivers/usb/media/Kconfig"
+
+source "drivers/usb/net/Kconfig"
+
+comment "USB port drivers"
+	depends on USB
+
+config USB_USS720
+	tristate "USS720 parport driver"
+	depends on USB && PARPORT
+	---help---
+	  This driver is for USB parallel port adapters that use the Lucent
+	  Technologies USS-720 chip. These cables are plugged into your USB
+	  port and provide USB compatibility to peripherals designed with
+	  parallel port interfaces.
+
+	  The chip has two modes: automatic mode and manual mode. In automatic
+	  mode, it looks to the computer like a standard USB printer. Only
+	  printers may be connected to the USS-720 in this mode. The generic
+	  USB printer driver ("USB Printer support", above) may be used in
+	  that mode, and you can say N here if you want to use the chip only
+	  in this mode.
+
+	  Manual mode is not limited to printers, any parallel port
+	  device should work. This driver utilizes manual mode.
+	  Note however that some operations are three orders of magnitude
+	  slower than on a PCI/ISA Parallel Port, so timing critical
+	  applications might not work.
+
+	  Say Y here if you own an USS-720 USB->Parport cable and intend to
+	  connect anything other than a printer to it.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called uss720.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+source "drivers/usb/serial/Kconfig"
+
+source "drivers/usb/misc/Kconfig"
+
+endmenu
+

drivers/usb/class/Kconfig

+#
+# USB Class driver configuration
+#
+comment "USB Device Class drivers"
+	depends on USB
+
+config USB_AUDIO
+	tristate "USB Audio support"
+	depends on USB && SOUND
+	help
+	  Say Y here if you want to connect USB audio equipment such as
+	  speakers to your computer's USB port.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called audio.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_BLUETOOTH_TTY
+	tristate "USB Bluetooth TTY support"
+	depends on USB
+	---help---
+	  Say Y here if you want to connect a USB Bluetooth device to your
+	  computer's USB port. You will need the Bluetooth stack (available
+	  at <http://developer.axis.com/software/index.shtml>) to fully use
+	  the device.
+
+	  This driver implements a tty inteface to a Bluetooth device.  If
+	  you want to use a socket based Bluetooth stack (like the BlueZ
+	  stack), do not use this driver.
+
+	  If in doubt, say N here.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called bluetty.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_MIDI
+	tristate "USB MIDI support"
+	depends on USB
+	---help---
+	  Say Y here if you want to connect a USB MIDI device to your
+	  computer's USB port. This driver is for devices that comply with
+	  'Universal Serial Bus Device Class Definition for MIDI Device'.
+
+	  The following devices are known to work:
+	  * Steinberg USB2MIDI
+	  * Roland MPU64
+	  * Roland PC-300
+	  * Roland SC8850
+	  * Roland UM-1
+	  * Roland UM-2
+	  * Roland UA-100
+	  * Yamaha MU1000
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called usb-midi.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_ACM
+	tristate "USB Modem (CDC ACM) support"
+	depends on USB
+	---help---
+	  This driver supports USB modems and ISDN adapters which support the
+	  Communication Device Class Abstract Control Model interface.
+	  Please read <file:Documentation/usb/acm.txt> for details.
+
+	  If your modem only reports "Cls=ff(vend.)" in the descriptors in
+	  /proc/bus/usb/devices, then your modem will not work with this
+	  driver.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called acm.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_PRINTER
+	tristate "USB Printer support"
+	depends on USB
+	help
+	  Say Y here if you want to connect a USB printer to your computer's
+	  USB port.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called printer.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+

drivers/usb/core/Kconfig

+#
+# USB Core configuration
+#
+config USB_DEBUG
+	bool "USB verbose debug messages"
+	depends on USB
+	help
+	  Say Y here if you want the USB core & hub drivers to produce a bunch
+	  of debug messages to the system log. Select this if you are having a
+	  problem with USB support and want to see more of what is going on.
+
+comment "Miscellaneous USB options"
+	depends on USB
+
+config USB_DEVICEFS
+	bool "USB device filesystem"
+	depends on USB
+	---help---
+	  If you say Y here (and to "/proc file system support" in the "File
+	  systems" section, above), you will get a file /proc/bus/usb/devices
+	  which lists the devices currently connected to your USB bus or
+	  busses, a file /proc/bus/usb/drivers which lists the USB kernel
+	  client drivers currently loaded, and for every connected device a
+	  file named  "/proc/bus/usb/xxx/yyy", where xxx is the bus number and
+	  yyy the device number; the latter files can be used by user space
+	  programs to talk directly to the device. These files are "virtual",
+	  meaning they are generated on the fly and not stored on the hard
+	  drive.
+
+	  You may need to mount the usbfs file system to see the files, use
+	  mount -t usbfs none /proc/bus/usb
+
+	  For the format of the various /proc/bus/usb/ files, please read
+	  <file:Documentation/usb/proc_usb_info.txt>.
+
+	  Please note that this code is completely unrelated to devfs, the
+	  "/dev file system support".
+
+	  Most users want to say Y here.
+
+config USB_LONG_TIMEOUT
+	bool "Long timeout for slow-responding devices (some MGE Ellipse UPSes)"
+	depends on USB
+	help
+	  This option makes the standard time out a bit longer.  Basically,
+	  some devices are just slow to respond, so this makes usb more
+	  patient.  There should be no harm in selecting this, but it is
+	  needed for some MGE Ellipse UPSes.
+
+	  If you have an MGE Ellipse UPS, or you see timeouts in HID
+	  transactions, say Y; otherwise say N.
+
+config USB_BANDWIDTH
+	bool "Enforce USB bandwidth allocation (EXPERIMENTAL)"
+	depends on USB && EXPERIMENTAL
+	help
+	  If you say Y here, the USB subsystem enforces USB bandwidth
+	  allocation and will prevent some device opens from succeeding
+	  if they would cause USB bandwidth usage to go above 90% of
+	  the bus bandwidth.
+
+	  If you say N here, these conditions will cause warning messages
+	  about USB bandwidth usage to be logged and some devices or
+	  drivers may not work correctly.
+
+config USB_DYNAMIC_MINORS
+	bool "Dynamic USB minor allocation (EXPERIMENTAL)"
+	depends on USB && EXPERIMENTAL
+	help
+	  If you say Y here, the USB subsystem will use dynamic minor
+	  allocation for any device that uses the USB major number.
+	  This means that you can have more than 16 of a single type
+	  of device (like USB printers).
+
+	  If you are unsure about this, say N here.
+

drivers/usb/host/Kconfig

+#
+# USB Host Controller Drivers
+#
+comment "USB Host Controller Drivers"
+	depends on USB
+
+config USB_EHCI_HCD
+	tristate "EHCI HCD (USB 2.0) support"
+	depends on USB
+	---help---
+	  The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0
+	  "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware.
+	  If your USB host controller supports USB 2.0, you will likely want to
+	  configure this Host Controller Driver.  At this writing, the primary
+	  implementation of EHCI is a chip from NEC, widely available in add-on
+	  PCI cards, but implementations are in the works from other vendors
+	  including Intel and Philips.  Motherboard support is appearing.
+
+	  EHCI controllers are packaged with "companion" host controllers (OHCI
+	  or UHCI) to handle USB 1.1 devices connected to root hub ports.  Ports
+	  will connect to EHCI if it the device is high speed, otherwise they
+	  connect to a companion controller.  If you configure EHCI, you should
+	  probably configure the OHCI (for NEC and some other vendors) USB Host
+	  Controller Driver or UHCI (for Via motherboards) Host Controller
+	  Driver too.
+
+	  You may want to read <file:Documentation/usb/ehci.txt>.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ehci-hcd.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_OHCI_HCD
+	tristate "OHCI HCD support"
+	depends on USB
+	---help---
+	  The Open Host Controller Interface (OHCI) is a standard for accessing
+	  USB 1.1 host controller hardware.  It does more in hardware than Intel's
+	  UHCI specification.  If your USB host controller follows the OHCI spec,
+	  say Y.  On most non-x86 systems, and on x86 hardware that's not using a
+	  USB controller from Intel or VIA, this is appropriate.  If your host
+	  controller doesn't use PCI, this is probably appropriate.  For a PCI
+	  based system where you're not sure, the "lspci -v" entry will list the
+	  right "prog-if" for your USB controller(s):  EHCI, OHCI, or UHCI.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ohci-hcd.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_UHCI_HCD_ALT
+	tristate "UHCI HCD (most Intel and VIA) support"
+	depends on USB
+	---help---
+	  The Universal Host Controller Interface is a standard by Intel for
+	  accessing the USB hardware in the PC (which is also called the USB
+	  host controller). If your USB host controller conforms to this
+	  standard, you may want to say Y, but see below. All recent boards
+	  with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
+	  i810, i820) conform to this standard. Also all VIA PCI chipsets
+	  (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
+	  133). If unsure, say Y.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called uhci-hcd.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SL811HS
+	tristate "SL811HS support"
+	depends on ARM && USB
+	help
+	  Say Y here if you have a SL811HS USB host controller in your system.
+
+	  If you do not know what this is, please say N.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called hc_sl811.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+

drivers/usb/image/Kconfig

+#
+# USB Imageing devices configuration
+#
+comment "USB Imaging devices"
+	depends on USB
+
+config USB_MDC800
+	tristate "USB Mustek MDC800 Digital Camera support (EXPERIMENTAL)"
+	depends on USB && EXPERIMENTAL
+	---help---
+	  Say Y here if you want to connect this type of still camera to
+	  your computer's USB port. This driver can be used with gphoto 0.4.3
+	  and higher (look at <http://www.gphoto.org/>).
+	  To use it create a device node with "mknod /dev/mustek c 180 32" and
+	  configure it in your software.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called mdc800.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SCANNER
+	tristate "USB Scanner support"
+	depends on USB
+	help
+	  Say Y here if you want to connect a USB scanner to your computer's
+	  USB port. Please read <file:Documentation/usb/scanner.txt> and
+	  <file:Documentation/usb/scanner-hp-sane.txt> for more information.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called scanner.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_MICROTEK
+	tristate "Microtek X6USB scanner support"
+	depends on USB && SCSI
+	help
+	  Say Y here if you want support for the Microtek X6USB and
+	  possibly the Phantom 336CX, Phantom C6 and ScanMaker V6U(S)L.
+	  Support for anything but the X6 is experimental.
+	  Please report failures and successes.
+	  The scanner will appear as a scsi generic device to the rest
+	  of the system. Scsi support is required.
+	  This driver can be compiled as a module, called microtek.o.
+
+config USB_HPUSBSCSI
+	tristate "HP53xx USB scanner support (EXPERIMENTAL)"
+	depends on USB && SCSI && EXPERIMENTAL
+	help
+	  Say Y here if you want support for the HP 53xx series of scanners
+	  and the Minolta Scan Dual. This driver is experimental.
+	  The scanner will be accessible as a SCSI device.
+	  This can be compiled as a module, called hpusbscsi.o.
+

drivers/usb/input/Kconfig

+#
+# USB Input driver configuration
+#
+comment "USB Human Interface Devices (HID)"
+	depends on USB
+
+config USB_HID
+	tristate "USB Human Interface Device (full HID) support"
+	depends on USB
+	---help---
+	  Say Y here if you want full HID support to connect keyboards,
+	  mice, joysticks, graphic tablets, or any other HID based devices
+	  to your computer via USB. You also need to select HID Input layer
+	  support (below) if you want to use keyboards, mice, joysticks and
+	  the like.
+
+	  You can't use this driver and the HIDBP (Boot Protocol) keyboard
+	  and mouse drivers at the same time. More information is available:
+	  <file:Documentation/input/input.txt>.
+
+	  If unsure, say Y.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called hid.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+comment "Input core support is needed for USB HID input layer or HIDBP support"
+	depends on USB && INPUT=n
+
+config USB_HIDINPUT
+	bool "HID input layer support"
+	depends on INPUT && USB_HID
+	help
+	  Say Y here if you want to use a USB keyboard, mouse or joystick,
+	  or any other HID input device. You also need "Input core support", 
+	  (CONFIG_INPUT), which you select under "Input device support", above.
+
+	  If unsure, say Y.
+
+config HID_FF
+	bool "Force feedback support (EXPERIMENTAL)"
+	depends on USB_HIDINPUT && EXPERIMENTAL
+	help
+	  Say Y here is you want force feedback support for a few HID devices. See
+	  below for a list of supported devices.
+	  See Documentation/input/ff.txt for a description of the force feedback API.
+
+	  If unsure, say N.
+
+config HID_PID
+	bool "PID Devices"
+	depends on HID_FF
+	help
+	  Say Y here if you have a PID-compliant joystick and wish to enable force
+	  feedback for it. The Microsoft Sidewinder Force Feedback 2 is one such
+	  device.
+
+config LOGITECH_FF
+	bool "Logitech WingMan *3D support"
+	depends on HID_FF
+	help
+	  Say Y here if you have one of these devices:
+	  - Logitech WingMan Cordless RumblePad
+	  - Logitech WingMan Force 3D
+	  and if you want to enable force feedback for them.
+	  Note: if you say N here, this device will still be supported, but without
+	  force feedback.
+
+config USB_HIDDEV
+	bool "/dev/hiddev raw HID device support"
+	depends on USB_HID
+	help
+	  Say Y here if you want to support HID devices (from the USB
+	  specification standpoint) that aren't strictly user interface
+	  devices, like monitor controls and Uninterruptable Power Supplies.
+
+	  This module supports these devices separately using a separate
+	  event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
+	  This driver requires CONFIG_USB_HID.
+
+	  If unsure, say Y.
+
+
+menu "USB HID Boot Protocol drivers"
+	depends on USB!=n && USB_HID!=y
+
+config USB_KBD
+	tristate "USB HIDBP Keyboard (simple Boot) support"
+	depends on USB && INPUT
+	---help---
+	  Say Y here only if you are absolutely sure that you don't want
+	  to use the generic HID driver for your USB keyboard and prefer
+	  to use the keyboard in its limited Boot Protocol mode instead.
+
+	  This is almost certainly not what you want.  This is mostly
+	  useful for embedded applications or simple keyboards.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called usbkbd.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+	  If even remotely unsure, say N.
+
+config USB_MOUSE
+	tristate "USB HIDBP Mouse (simple Boot) support"
+	depends on USB && INPUT
+	---help---
+	  Say Y here only if you are absolutely sure that you don't want
+	  to use the generic HID driver for your USB keyboard and prefer
+	  to use the keyboard in its limited Boot Protocol mode instead.
+
+	  This is almost certainly not what you want.  This is mostly
+	  useful for embedded applications or simple mice.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called usbmouse.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+	  If even remotely unsure, say N.
+
+endmenu
+
+config USB_AIPTEK
+	tristate "Aiptek 6000U/8000U tablet support"
+	depends on USB && INPUT
+	help
+	  Say Y here if you want to use the USB version of the Aiptek 6000U
+	  or Aiptek 8000U tablet.  Make sure to say Y to "Mouse support"
+	  (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
+	  (CONFIG_INPUT_EVDEV) as well.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called aiptek.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_WACOM
+	tristate "Wacom Intuos/Graphire tablet support"
+	depends on USB && INPUT
+	help
+	  Say Y here if you want to use the USB version of the Wacom Intuos
+	  or Graphire tablet.  Make sure to say Y to "Mouse support"
+	  (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
+	  (CONFIG_INPUT_EVDEV) as well.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called wacom.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_POWERMATE
+	tristate "Griffin PowerMate and Contour Jog support"
+	depends on USB && INPUT
+	---help---
+	  Say Y here if you want to use  Griffin PowerMate or Contour Jog devices.
+	  These are stainless steel dials which can measure clockwise and
+	  anticlockwise rotation. The dial also acts as a pushbutton. The base
+	  contains an LED which can be instructed to pulse or to switch to a
+	  particular intensity.
+
+	  You can download userspace tools from http://sowerbutts.com/powermate/
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called powermate.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_XPAD
+	tristate "X-Box gamepad support"
+	depends on USB && INPUT
+	---help---
+	  Say Y here if you want to use the X-Box pad with your computer.
+	  Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
+	  and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
+
+	  For information about how to connect the X-Box pad to USB, see
+	  Documentation/input/xpad.txt.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called wacom.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+

drivers/usb/media/Kconfig

+#
+# USB Multimedia device configuration
+#
+comment "USB Multimedia devices"
+	depends on USB
+
+config USB_DABUSB
+	tristate "DABUSB driver"
+	depends on USB
+	---help---
+	  A Digital Audio Broadcasting (DAB) Receiver for USB and Linux
+	  brought to you by the DAB-Team (<http://dab.in.tum.de/>).  This
+	  driver can be taken as an example for URB-based bulk, control, and
+	  isochronous transactions. URB's are explained in
+	  <file:Documentation/usb/URB.txt>.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called dabusb.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+comment "Video4Linux support is needed for USB Multimedia device support"
+	depends on USB && VIDEO_DEV=n
+
+config USB_VICAM
+	tristate "USB 3com HomeConnect (aka vicam) support (EXPERIMENTAL)"
+	depends on USB && VIDEO_DEV && EXPERIMENTAL
+	---help---
+	  Say Y here if you have 3com homeconnect camera (vicam).
+
+	  This driver uses the Video For Linux API. You must say Y or M to
+	  "Video For Linux" (under Multimedia Devices) to use this driver.
+	  Information on this API and pointers to "v4l" programs may be found
+	  on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called vicam.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_DSBR
+	tristate "D-Link USB FM radio support (EXPERIMENTAL)"
+	depends on USB && VIDEO_DEV && EXPERIMENTAL
+	---help---
+	  Say Y here if you want to connect this type of radio to your
+	  computer's USB port. Note that the audio is not digital, and
+	  you must connect the line out connector to a sound card or a
+	  set of speakers.
+
+	  This driver uses the Video For Linux API.  You must enable
+	  (Y or M in config) Video For Linux (under Character Devices)
+	  to use this driver.  Information on this API and pointers to
+	  "v4l" programs may be found on the WWW at
+	  <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called dsbr100.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_IBMCAM
+	tristate "USB IBM (Xirlink) C-it Camera support"
+	depends on USB && VIDEO_DEV
+	---help---
+	  Say Y here if you want to connect a IBM "C-It" camera, also known as
+	  "Xirlink PC Camera" to your computer's USB port.  For more
+	  information, read <file:Documentation/usb/ibmcam.txt>.
+
+	  This driver uses the Video For Linux API.  You must enable
+	  (Y or M in config) Video For Linux (under Character Devices)
+	  to use this driver.  Information on this API and pointers to
+	  "v4l" programs may be found on the WWW at
+	  <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ibmcam.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>. This
+	  camera has several configuration options which can be specified when
+	  you load the module.  Read <file:Documentation/usb/ibmcam.txt> to
+	  learn more.
+
+config USB_KONICAWC
+	tristate "USB Konica Webcam support"
+	depends on USB && VIDEO_DEV
+	---help---
+	  Say Y here if you want support for webcams based on a Konica
+	  chipset. This is known to work with the Intel YC76 webcam.
+
+	  This driver uses the Video For Linux API.  You must enable
+	  (Y or M in config) Video For Linux (under Character Devices)
+	  to use this driver.  Information on this API and pointers to
+	  "v4l" programs may be found on the WWW at
+	  <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called konicawc.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_OV511
+	tristate "USB OV511 Camera support"
+	depends on USB && VIDEO_DEV
+	---help---
+	  Say Y here if you want to connect this type of camera to your
+	  computer's USB port. See <file:Documentation/usb/ov511.txt> for more
+	  information and for a list of supported cameras.
+
+	  This driver uses the Video For Linux API. You must say Y or M to
+	  "Video For Linux" (under Character Devices) to use this driver.
+	  Information on this API and pointers to "v4l" programs may be found
+	  on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ov511.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_PWC
+	tristate "USB Philips Cameras"
+	depends on USB && VIDEO_DEV
+	---help---
+	  Say Y or M here if you want to use one of these Philips USB webcams:
+	  PCA645, PCA646, PCVC675, PCVC680, PCVC690, PCVC730, PCVC740, or
+	  the Askey VC010. The PCA635, PCVC665 and PCVC720 are not supported
+	  by this driver and never will be.
+
+	  This driver has an optional plugin, which is distributed as a binary
+	  module only.  It contains code that allow you to use higher
+	  resolutions and framerates but may not be distributed as source.
+	  But even without this plugin you can these cams for most
+	  applications.
+
+	  See <file:Documentation/usb/philips.txt> for more information and
+	  installation instructions.
+
+	  The built-in microphone is enabled by selecting USB Audio support.
+
+	  This driver uses the Video For Linux API. You must say Y or M to
+	  "Video For Linux" (under Character Devices) to use this driver.
+	  Information on this API and pointers to "v4l" programs may be found
+	  on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called pwc.o.  If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SE401
+	tristate "USB SE401 Camera support"
+	depends on USB && VIDEO_DEV
+	---help---
+	  Say Y here if you want to connect this type of camera to your
+	  computer's USB port. See <file:Documentation/usb/se401.txt> for more
+	  information and for a list of supported cameras.
+
+	  This driver uses the Video For Linux API. You must say Y or M to
+	  "Video For Linux" (under Multimedia Devices) to use this driver.
+	  Information on this API and pointers to "v4l" programs may be found
+	  on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called se401.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_STV680
+	tristate "USB STV680 (Pencam) Camera support"
+	depends on USB && VIDEO_DEV
+	---help---
+	  Say Y here if you want to connect this type of camera to your
+	  computer's USB port. This includes the Pencam line of cameras.
+	  See <file:Documentation/usb/stv680.txt> for more information and for
+	  a list of supported cameras.
+
+	  This driver uses the Video For Linux API. You must say Y or M to
+	  "Video For Linux" (under Multimedia Devices) to use this driver.
+	  Information on this API and pointers to "v4l" programs may be found
+	  on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called stv680.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+

drivers/usb/misc/Kconfig

+#
+# USB Miscellaneous driver configuration
+#
+comment "USB Miscellaneous drivers"
+	depends on USB
+
+config USB_EMI26
+	tristate "EMI 2|6 USB Audio interface support"
+	depends on USB_AUDIO
+	---help---
+	  This driver loads firmware to Emagic EMI 2|6 low latency USB
+	  Audio interface.
+
+	  After firmware load the device is handled with standard linux
+	  USB Audio driver.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called audio.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_TIGL
+	tristate "Texas Instruments Graph Link USB (aka SilverLink) cable support"
+	depends on USB
+	---help---
+	  If you own a Texas Instruments graphing calculator and use a 
+	  TI-GRAPH LINK USB cable (aka SilverLink), then you might be 
+	  interested in this driver.
+
+	  If you enable this driver, you will be able to communicate with
+	  your calculator through a set of device nodes under /dev.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called tiglusb.o. If you want to compile it as a
+	  module, say M here and read Documentation/modules.txt.
+
+	  If you don't know what the SilverLink cable is or what a Texas
+	  Instruments graphing calculator is, then you probably don't need this
+	  driver.
+
+	  If unsure, say N.
+
+config USB_AUERSWALD
+	tristate "USB Auerswald ISDN support (EXPERIMENTAL)"
+	depends on USB && EXPERIMENTAL
+	help
+	  Say Y here if you want to connect an Auerswald USB ISDN Device
+	  to your computer's USB port.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called auerswald.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_RIO500
+	tristate "USB Diamond Rio500 support (EXPERIMENTAL)"
+	depends on USB && EXPERIMENTAL
+	help
+	  Say Y here if you want to connect a USB Rio500 mp3 player to your
+	  computer's USB port. Please read <file:Documentation/usb/rio.txt>
+	  for more information.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called rio500.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_BRLVGER
+	tristate "Tieman Voyager USB Braille display support (EXPERIMENTAL)"
+	depends on USB && EXPERIMENTAL
+	help
+	  Say Y here if you want to use the Voyager USB Braille display from
+	  Tieman. See <file:Documentation/usb/brlvger.txt> for more
+	  information.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called brlvger.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_LCD
+	tristate "USB LCD driver support"
+	depends on USB
+	help
+	  Say Y here if you want to connect an USBLCD to your computer's
+	  USB port. The USBLCD is a small USB interface board for
+	  alphanumeric LCD modules. See <http://www.usblcd.de> for more
+	  information.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called usblcd.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SPEEDTOUCH
+	tristate "Alcatel Speedtouch ADSL USB Modem"
+	depends on USB && ATM
+
+config USB_TEST
+	tristate "USB testing driver (DEVELOPMENT)"
+	depends on USB_DEVICEFS && EXPERIMENTAL
+	help
+
+	  This driver is for testing host controller software.  It is used
+	  with specialized device firmware for regression and stress testing,
+	  to help prevent problems from cropping up with 'real" drivers.
+

drivers/usb/net/Kconfig

+#
+# USB Network devices configuration
+#
+comment "USB Network adaptors"
+	depends on USB
+
+comment "Networking support is needed for USB Networking device support"
+	depends on USB && !NET
+
+config USB_CATC
+	tristate "USB CATC NetMate-based Ethernet device support (EXPERIMENTAL)"
+	depends on USB && NET && EXPERIMENTAL
+	---help---
+	  Say Y if you want to use one of the following 10Mbps USB Ethernet
+	  device based on the EL1210A chip. Supported devices are:
+	  Belkin F5U011
+	  Belkin F5U111
+	  CATC NetMate
+	  CATC NetMate II
+	  smartBridges smartNIC
+
+	  This driver makes the adapter appear as a normal Ethernet interface,
+	  typically on eth0, if it is the only ethernet device, or perhaps on
+	  eth1, if you have a PCI or ISA ethernet card installed.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called catc.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_CDCETHER
+	tristate "USB CDC Ethernet support (EXPERIMENTAL)"
+	depends on USB && NET && EXPERIMENTAL
+	---help---
+	  This driver supports devices conforming to the Communication Device
+	  Class Ethernet Control Model.  This is used in some cable modems.
+	  For more details on the specification, get the Communication Device
+	  Class specification from <http://www.usb.org/>.
+
+	  This driver should work with the following devices:
+	  * Ericsson PipeRider (all variants)
+	  * Motorola (DM100 and SB4100)
+	  * Broadcom Cable Modem (reference design)
+	  * Toshiba PCX1100U and possibly other cable modems
+
+	  The device creates a network device (ethX, where X depends on what
+	  other networking devices you have in use), as for a normal PCI
+	  or ISA based ethernet network card.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called cdc-ether.o.  If you want to compile it 
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_KAWETH
+	tristate "USB KLSI KL5USB101-based ethernet device support"
+	depends on USB && NET
+	---help---
+	  Say Y here if you want to use one of the following 10Mbps only
+	  USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
+	  3Com 3C19250
+	  ADS USB-10BT
+	  ATEN USB Ethernet
+	  ASANTE USB To Ethernet Adapter
+	  AOX Endpoints USB Ethernet
+	  Correga K.K.
+	  D-Link DSB-650C and DU-E10
+	  Entrega / Portgear E45
+	  I-O DATA USB-ET/T
+	  Jaton USB Ethernet Device Adapter
+	  Kingston Technology USB Ethernet Adapter
+	  Linksys USB10T
+	  Mobility USB-Ethernet Adapter
+	  NetGear EA-101
+	  Peracom Enet and Enet2
+	  Portsmith Express Ethernet Adapter
+	  Shark Pocket Adapter
+	  SMC 2202USB
+	  Sony Vaio port extender
+
+	  This driver is likely to work with most 10Mbps only USB Ethernet
+	  adapters, including some "no brand" devices. It does NOT work on
+	  SmartBridges smartNIC or on Belkin F5U111 devices - you should use
+	  the CATC NetMate driver for those. If you are not sure which one
+	  you need, select both, and the correct one should be selected for
+	  you.
+
+	  This driver makes the adapter appear as a normal Ethernet interface,
+	  typically on eth0, if it is the only ethernet device, or perhaps on
+	  eth1, if you have a PCI or ISA ethernet card installed.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called kaweth.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_PEGASUS
+	tristate "USB Pegasus/Pegasus-II based ethernet device support"
+	depends on USB && NET
+	---help---
+	  Say Y here if you know you have Pegasus or Pegasus-II based adapter.
+	  If in doubt then look at linux/drivers/usb/pegasus.h for the complete
+	  list of supported devices.
+	  If your particular adapter is not in the list and you are _sure_ it
+	  is Pegasus or Pegasus II based then send me (petkan@users.sourceforge.net)
+	  vendor and device IDs.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called pegasus.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_RTL8150
+	tristate "USB RTL8150 based ethernet device support (EXPERIMENTAL)"
+	depends on USB && NET && EXPERIMENTAL
+	help
+	  Say Y here if you have RTL8150 based usb-ethernet adapter.
+	  Send me (petkan@users.sourceforge.net) any comments you may have.
+	  You can also check for updates at http://pegasus2.sourceforge.net/
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called rtl8150.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_USBNET
+	tristate "USB-to-USB Networking cable device support"
+	depends on USB && NET
+	---help---
+	  This driver supports network links over USB with USB "Network"
+	  or "data transfer" cables, often used to network laptops to PCs.
+	  Such cables have chips from suppliers such as Belkin/eTEK, GeneSys
+	  (GeneLink), NetChip and Prolific. Intelligent USB devices could also
+	  use this approach to provide Internet access, using standard USB
+	  cabling. You can find these chips also on some motherboards with
+	  USB PC2PC support.
+
+	  These links will have names like "usb0", "usb1", etc.  They act
+	  like two-node Ethernets, so you can use 802.1d Ethernet Bridging
+	  (CONFIG_BRIDGE) to simplify your network routing.
+
+	  This code is also available as a kernel module (code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called usbnet.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+

drivers/usb/serial/Kconfig

+#
+# USB Serial device configuration
+#
+
+menu "USB Serial Converter support"
+	depends on USB!=n
+
+config USB_SERIAL
+	tristate "USB Serial Converter support"
+	depends on USB
+	---help---
+	  Say Y here if you have a USB device that provides normal serial
+	  ports, or acts like a serial device, and you want to connect it to
+	  your USB bus.
+
+	  Please read <file:Documentation/usb/usb-serial.txt> for more
+	  information on the specifics of the different devices that are
+	  supported, and on how to use them.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called usbserial.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_DEBUG
+	bool "USB Serial Converter verbose debug"
+	depends on USB_SERIAL=y
+	help
+	  Say Y here if you want verbose debug messages from the USB Serial
+	  Drivers sent to the kernel debug log.
+
+config USB_SERIAL_CONSOLE
+	bool "USB Serial Console device support (EXPERIMENTAL)"
+	depends on USB_SERIAL=y && EXPERIMENTAL
+	---help---
+	  If you say Y here, it will be possible to use a USB to serial
+	  converter port as the system console (the system console is the
+	  device which receives all kernel messages and warnings and which
+	  allows logins in single user mode). This could be useful if some
+	  terminal or printer is connected to that serial port.
+
+	  Even if you say Y here, the currently visible virtual console
+	  (/dev/tty0) will still be used as the system console by default, but
+	  you can alter that using a kernel command line option such as
+	  "console=ttyUSB0". (Try "man bootparam" or see the documentation of
+	  your boot loader (lilo or loadlin) about how to pass options to the
+	  kernel at boot time.)
+
+	  If you don't have a VGA card installed and you say Y here, the
+	  kernel will automatically use the first USB to serial converter
+	  port, /dev/ttyUSB0, as system console.
+
+	  If unsure, say N.
+
+config USB_SERIAL_GENERIC
+	bool "USB Generic Serial Driver"
+	depends on USB_SERIAL
+	help
+	  Say Y here if you want to use the generic USB serial driver.  Please
+	  read <file:Documentation/usb/usb-serial.txt> for more information on
+	  using this driver.  It is recommended that the "USB Serial converter
+	  support" be compiled as a module for this driver to be used
+	  properly.
+
+config USB_SERIAL_BELKIN
+	tristate "USB Belkin and Peracom Single Port Serial Driver"
+	depends on USB_SERIAL
+	help
+	  Say Y here if you want to use a Belkin USB Serial single port
+	  adaptor (F5U103 is one of the model numbers) or the Peracom single
+	  port USB to serial adapter.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called belkin_sa.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_WHITEHEAT
+	tristate "USB ConnectTech WhiteHEAT Serial Driver"
+	depends on USB_SERIAL
+	help
+	  Say Y here if you want to use a ConnectTech WhiteHEAT 4 port
+	  USB to serial converter device.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called whiteheat.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_DIGI_ACCELEPORT
+	tristate "USB Digi International AccelePort USB Serial Driver"
+	depends on USB_SERIAL
+	---help---
+	  Say Y here if you want to use Digi AccelePort USB 2 or 4 devices,
+	  2 port (plus parallel port) and 4 port USB serial converters.  The
+	  parallel port on the USB 2 appears as a third serial port on Linux.
+	  The Digi Acceleport USB 8 is not yet supported by this driver.
+
+	  This driver works under SMP with the usb-uhci driver.  It does not
+	  work under SMP with the uhci driver.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called digi_acceleport.o.  If you want to compile
+	  it as a module, say M here and read
+	  <file:Documentation/modules.txt>.
+
+config USB_SERIAL_EMPEG
+	tristate "USB Empeg empeg-car Mark I/II Driver"
+	depends on USB_SERIAL
+	help
+	  Say Y here if you want to connect to your Empeg empeg-car Mark I/II
+	  mp3 player via USB.  The driver uses a single ttyUSB{0,1,2,...}
+	  device node.  See <file:Documentation/usb/usb-serial.txt> for more
+	  tidbits of information.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called empeg.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_FTDI_SIO
+	tristate "USB FTDI Single Port Serial Driver (EXPERIMENTAL)"
+	depends on USB_SERIAL && EXPERIMENTAL
+	---help---
+	  Say Y here if you want to use a FTDI SIO single port USB to serial
+	  converter device. The implementation I have is called the USC-1000.
+	  This driver has also be tested with the 245 and 232 devices.
+
+	  See <http://ftdi-usb-sio.sourceforge.net/> for more
+	  information on this driver and the device.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ftdi_sio.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_VISOR
+	tristate "USB Handspring Visor / Palm m50x / Sony Clie Driver"
+	depends on USB_SERIAL
+	help
+	  Say Y here if you want to connect to your HandSpring Visor, Palm
+	  m500 or m505 through its USB docking station. See
+	  <http://usbvisor.sourceforge.net/> for more information on using this
+	  driver.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called visor.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_IPAQ
+	tristate "USB Compaq iPAQ / HP Jornada / Casio EM500 Driver"
+	depends on USB_SERIAL
+	help
+	  Say Y here if you want to connect to your Compaq iPAQ, HP Jornada
+	  548/568 or Casio EM500 running Windows CE 3.0 or PocketPC 2002
+	  using a USB cradle/cable. For information on using the driver,
+	  read <file:Documentation/usb/usb-serial.txt>.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ipaq.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_IR
+	tristate "USB IR Dongle Serial Driver (EXPERIMENTAL)"
+	depends on USB_SERIAL && EXPERIMENTAL
+	help
+	  Say Y here if you want to enable simple serial support for USB IrDA
+	  devices.  This is useful if you do not want to use the full IrDA
+	  stack.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called ir-usb.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_EDGEPORT
+	tristate "USB Inside Out Edgeport Serial Driver"
+	depends on USB_SERIAL
+	---help---
+	  Say Y here if you want to use any of the following devices from
+	  Inside Out Networks (Digi):
+	  Edgeport/4
+	  Rapidport/4
+	  Edgeport/4t
+	  Edgeport/2
+	  Edgeport/4i
+	  Edgeport/2i
+	  Edgeport/421
+	  Edgeport/21
+	  Edgeport/8
+	  Edgeport/8 Dual
+	  Edgeport/2D8
+	  Edgeport/4D8
+	  Edgeport/8i
+	  Edgeport/2 DIN
+	  Edgeport/4 DIN
+	  Edgeport/16 Dual
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called io_edgeport.o.  If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_EDGEPORT_TI
+	tristate "USB Inside Out Edgeport Serial Driver (TI devices)"
+	depends on USB_SERIAL
+	help
+	  Say Y here if you want to use any of the devices from Inside Out
+	  Networks (Digi) that are not supported by the io_edgeport driver.
+	  This includes the Edgeport/1 device.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called io_ti.o.  If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_KEYSPAN_PDA
+	tristate "USB Keyspan PDA Single Port Serial Driver"
+	depends on USB_SERIAL
+	help
+	  Say Y here if you want to use a Keyspan PDA single port USB to
+	  serial converter device.  This driver makes use of firmware
+	  developed from scratch by Brian Warner.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called keyspan_pda.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_KEYSPAN
+	tristate "USB Keyspan USA-xxx Serial Driver"
+	depends on USB_SERIAL
+	---help---
+	  Say Y here if you want to use Keyspan USB to serial converter
+	  devices.  This driver makes use of Keyspan's official firmware
+	  and was developed with their support.  You must also include
+	  firmware to support your particular device(s).
+
+	  See <http://misc.nu/hugh/keyspan.html> for more information.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called keyspan.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_KEYSPAN_USA28
+	bool "USB Keyspan USA-28 Firmware"
+	depends on USB_SERIAL_KEYSPAN
+	help
+	  Say Y here to include firmware for the USA-28 converter.
+
+config USB_SERIAL_KEYSPAN_USA28X
+	bool "USB Keyspan USA-28X Firmware"
+	depends on USB_SERIAL_KEYSPAN
+	help
+	  Say Y here to include firmware for the USA-28X converter.
+	  Be sure you have a USA-28X, there are also 28XA and 28XB
+	  models, the label underneath has the actual part number.
+
+config USB_SERIAL_KEYSPAN_USA28XA
+	bool "USB Keyspan USA-28XA Firmware"
+	depends on USB_SERIAL_KEYSPAN
+	help
+	  Say Y here to include firmware for the USA-28XA converter.
+	  Be sure you have a USA-28XA, there are also 28X and 28XB
+	  models, the label underneath has the actual part number.
+
+config USB_SERIAL_KEYSPAN_USA28XB
+	bool "USB Keyspan USA-28XB Firmware"
+	depends on USB_SERIAL_KEYSPAN
+	help
+	  Say Y here to include firmware for the USA-28XB converter.
+	  Be sure you have a USA-28XB, there are also 28X and 28XA
+	  models, the label underneath has the actual part number.
+
+config USB_SERIAL_KEYSPAN_USA19
+	bool "USB Keyspan USA-19 Firmware"
+	depends on USB_SERIAL_KEYSPAN
+	help
+	  Say Y here to include firmware for the USA-19 converter.
+
+config USB_SERIAL_KEYSPAN_USA18X
+	bool "USB Keyspan USA-18X Firmware"
+	depends on USB_SERIAL_KEYSPAN
+	help
+	  Say Y here to include firmware for the USA-18X converter.
+
+config USB_SERIAL_KEYSPAN_USA19W
+	bool "USB Keyspan USA-19W Firmware"
+	depends on USB_SERIAL_KEYSPAN
+	help
+	  Say Y here to include firmware for the USA-19W converter.
+
+config USB_SERIAL_KEYSPAN_USA19QW
+	bool "USB Keyspan USA-19QW Firmware"
+	depends on USB_SERIAL_KEYSPAN
+
+config USB_SERIAL_KEYSPAN_USA19QI
+	bool "USB Keyspan USA-19QI Firmware"
+	depends on USB_SERIAL_KEYSPAN
+
+config USB_SERIAL_KEYSPAN_USA49W
+	bool "USB Keyspan USA-49W Firmware"
+	depends on USB_SERIAL_KEYSPAN
+	help
+	  Say Y here to include firmware for the USA-49W converter.
+
+config USB_SERIAL_KLSI
+	tristate "USB KL5KUSB105 (Palmconnect) Driver (EXPERIMENTAL)"
+	depends on USB_SERIAL && EXPERIMENTAL
+	---help---
+	  Say Y here if you want to use a KL5KUSB105 - based single port
+	  serial adapter. The most widely known -- and currently the only
+	  tested -- device in this category is the PalmConnect USB Serial
+	  adapter sold by Palm Inc. for use with their Palm III and Palm V
+	  series PDAs.
+
+	  Please read <file:Documentation/usb/usb-serial.txt> for more
+	  information.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called kl5kusb105.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_MCT_U232
+	tristate "USB MCT Single Port Serial Driver"
+	depends on USB_SERIAL
+	---help---
+	  Say Y here if you want to use a USB Serial single port adapter from
+	  Magic Control Technology Corp. (U232 is one of the model numbers).
+
+	  This driver also works with Sitecom U232-P25 and D-Link DU-H3SP USB
+	  BAY devices.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called mct_u232.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_PL2303
+	tristate "USB Prolific 2303 Single Port Serial Driver"
+	depends on USB_SERIAL
+	help
+	  Say Y here if you want to use the PL2303 USB Serial single port
+	  adapter from Prolific.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called pl2303.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_SAFE
+	tristate "USB Safe Serial (Encapsulated) Driver (EXPERIMENTAL)"
+	depends on USB_SERIAL && EXPERIMENTAL
+
+config USB_SERIAL_SAFE_PADDED
+	bool "USB Secure Encapsulated Driver - Padded"
+	depends on USB_SERIAL_SAFE
+
+config USB_SERIAL_CYBERJACK
+	tristate "USB REINER SCT cyberJack pinpad/e-com chipcard reader (EXPERIMENTAL)"
+	depends on USB_SERIAL && EXPERIMENTAL
+	---help---
+	  Say Y here if you want to use a cyberJack pinpad/e-com USB chipcard
+	  reader. This is an interface to ISO 7816 compatible contactbased
+	  chipcards, e.g. GSM SIMs.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called cyberjack.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+	  If unsure, say N.
+
+config USB_SERIAL_XIRCOM
+	tristate "USB Xircom / Entregra Single Port Serial Driver"
+	depends on USB_SERIAL
+	help
+	  Say Y here if you want to use a Xircom or Entregra single port USB to
+	  serial converter device.  This driver makes use of firmware
+	  developed from scratch by Brian Warner.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called keyspan_pda.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_SERIAL_OMNINET
+	tristate "USB ZyXEL omni.net LCD Plus Driver (EXPERIMENTAL)"
+	depends on USB_SERIAL && EXPERIMENTAL
+	help
+	  Say Y here if you want to use a ZyXEL omni.net LCD ISDN TA.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called omninet.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+endmenu
+

drivers/usb/storage/Kconfig

+#
+# USB Storage driver configuration
+#
+comment "SCSI support is needed for USB Storage"
+	depends on USB && SCSI=n
+
+config USB_STORAGE
+	tristate "USB Mass Storage support"
+	depends on USB && SCSI
+	---help---
+	  Say Y here if you want to connect USB mass storage devices to your
+	  computer's USB port. This is the driver you need for USB floppy drives,
+	  USB hard disks, USB tape drives and USB CD-ROMs, along with
+	  similar devices. This driver may also be used for some cameras and
+	  card readers.
+
+	  This code is also available as a module ( = code which can be
+	  inserted in and removed from the running kernel whenever you want).
+	  The module will be called usb-storage.o. If you want to compile it
+	  as a module, say M here and read <file:Documentation/modules.txt>.
+
+config USB_STORAGE_DEBUG
+	bool "USB Mass Storage verbose debug"
+	depends on USB_STORAGE
+	help
+	  Say Y here in order to have the USB Mass Storage code generate
+	  verbose debugging messages.
+
+config USB_STORAGE_DATAFAB
+	bool "Datafab Compact Flash Reader support (EXPERIMENTAL)"
+	depends on USB_STORAGE && EXPERIMENTAL
+	help
+	  Support for certain Datafab CompactFlash readers.
+	  Datafab has a web page at <http://www.datafabusa.com/>.
+
+config USB_STORAGE_FREECOM
+	bool "Freecom USB/ATAPI Bridge support"
+	depends on USB_STORAGE
+	help
+	  Support for the Freecom USB to IDE/ATAPI adaptor.
+	  Freecom has a web page at <http://www.freecom.de/>.
+
+config USB_STORAGE_ISD200
+	bool "ISD-200 USB/ATA Bridge support"
+	depends on USB_STORAGE
+	---help---
+	  Say Y here if you want to use USB Mass Store devices based
+	  on the In-Systems Design ISD-200 USB/ATA bridge.
+
+	  Some of the products that use this chip are:
+
+	  - Archos Jukebox 6000
+	  - ISD SmartCable for Storage
+	  - Taiwan Skymaster CD530U/DEL-0241 IDE bridge
+	  - Sony CRX10U CD-R/RW drive
+	  - CyQ've CQ8060A CDRW drive
+	  - Planex eXtreme Drive RX-25HU USB-IDE cable (not model RX-25U)
+
+config USB_STORAGE_DPCM
+	bool "Microtech CompactFlash/SmartMedia support"
+	depends on USB_STORAGE
+	help
+	  Say Y here to support the Microtech ZiO! CompactFlash reader.
+	  There is a web page at <http://www.microtechint.com/zio/index.html>.
+
+config USB_STORAGE_HP8200e
+	bool "HP CD-Writer 82xx support (EXPERIMENTAL)"
+	depends on USB_STORAGE && EXPERIMENTAL
+	help
+	  Say Y here to include additional code to support Hewlett-Packard
+	  8200e/8210e/8230e CD-Writer Plus drives.
+
+config USB_STORAGE_SDDR09
+	bool "SanDisk SDDR-09 (and other SmartMedia) support (EXPERIMENTAL)"
+	depends on USB_STORAGE && EXPERIMENTAL
+	help
+	  Say Y here to include additional code to support the Sandisk SDDR-09
+	  SmartMedia reader in the USB Mass Storage driver.
+	  Also works for the Microtech Zio! SmartMedia reader.
+
+config USB_STORAGE_SDDR55
+	bool "SanDisk SDDR-55 SmartMedia support (EXPERIMENTAL)"
+	depends on USB_STORAGE && EXPERIMENTAL
+	help
+	  Say Y here to include additional code to support the Sandisk SDDR-55
+	  SmartMedia reader in the USB Mass Storage driver.
+
+config USB_STORAGE_JUMPSHOT
+	bool "Lexar Jumpshot Compact Flash Reader (EXPERIMENTAL)"
+	depends on USB_STORAGE && EXPERIMENTAL
+	help
+	  Say Y here to include additional code to support the Lexar Jumpshot
+	  USB CompactFlash reader.
+

drivers/video/Kconfig

+#
+# Video configuration
+#
+
+menu "Frame-buffer support"
+
+config FB
+	bool "Support for frame buffer devices (EXPERIMENTAL)"
+	---help---
+	  The frame buffer device provides an abstraction for the graphics
+	  hardware. It represents the frame buffer of some video hardware and
+	  allows application software to access the graphics hardware through
+	  a well-defined interface, so the software doesn't need to know
+	  anything about the low-level (hardware register) stuff.
+
+	  Frame buffer devices work identically across the different
+	  architectures supported by Linux and make the implementation of
+	  application programs easier and more portable; at this point, an X
+	  server exists which uses the frame buffer device exclusively.
+	  On several non-X86 architectures, the frame buffer device is the
+	  only way to use the graphics hardware.
+
+	  The device is accessed through special device nodes, usually located
+	  in the /dev directory, i.e. /dev/fb*.
+
+	  You need an utility program called fbset to make full use of frame
+	  buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
+	  and the Framebuffer-HOWTO at
+	  <http://www.tahallah.demon.co.uk/programming/prog.html> for more
+	  information.
+
+	  Say Y here and to the driver for your graphics board below if you
+	  are compiling a kernel for a non-x86 architecture.
+
+	  If you are compiling for the x86 architecture, you can say Y if you
+	  want to play with it, but it is not essential. Please note that
+	  running graphical applications that directly touch the hardware
+	  (e.g. an accelerated X server) and that are not frame buffer
+	  device-aware may cause unexpected results. If unsure, say N.
+
+config DUMMY_CONSOLE
+	bool
+	depends on FB
+	default y
+
+config FB_CLGEN
+	tristate "Cirrus Logic support (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && (AMIGA || PCI)
+	---help---
+	  This enables support for Cirrus Logic GD542x/543x based boards on
+	  Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
+
+	  If you have a PCI-based system, this enables support for these
+	  chips: GD-543x, GD-544x, GD-5480.
+
+	  Please read the file <file:Documentation/fb/clgenfb.txt>.
+
+	  Say N unless you have such a graphics board or plan to get one
+	  before you next recompile the kernel.
+
+config FB_PM2
+	tristate "Permedia2 support (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && (AMIGA || PCI)
+	help
+	  This is the frame buffer device driver for the Permedia2 AGP frame
+	  buffer card from ASK, aka `Graphic Blaster Exxtreme'.  There is a
+	  product page at
+	  <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
+
+config FB_PM2_FIFO_DISCONNECT
+	bool "enable FIFO disconnect feature"
+	depends on FB_PM2 && PCI
+	help
+	  Support the Permedia2 FIFOI disconnect feature (see CONFIG_FB_PM2).
+
+config FB_PM2_PCI
+	bool "generic Permedia2 PCI board support"
+	depends on FB_PM2 && PCI
+	help
+	  Say Y to enable support for Permedia2 AGP frame buffer card from
+	  3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus.
+
+config FB_PM2_CVPPC
+	bool "Phase5 CVisionPPC/BVisionPPC support"
+	depends on FB_PM2 && AMIGA
+	help
+	  Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC
+	  framebuffer cards.  Phase 5 is no longer with us, alas.
+
+config FB_ACORN
+	bool "Acorn VIDC support"
+	depends on FB && ARM && ARCH_ACORN
+	help
+	  This is the frame buffer device driver for the Acorn VIDC graphics
+	  hardware found in Acorn RISC PCs and other ARM-based machines.  If
+	  unsure, say N.
+
+config FB_ANAKIN
+	bool "Anakin LCD support"
+	depends on FB && ARM && ARCH_ANAKIN
+
+config FB_CLPS711X
+	bool "CLPS711X LCD support"
+	depends on FB && ARM && ARCH_CLPS711X
+
+config FB_SA1100
+	bool "SA-1100 LCD support"
+	depends on FB && ARM && ARCH_SA1100
+	help
+	  This is a framebuffer device for the SA-1100 LCD Controller.
+	  See <http://www.linux-fbdev.org/> for information on framebuffer
+	  devices.
+
+	  If you plan to use the LCD display with your SA-1100 system, say
+	  Y here.
+
+choice
+	prompt "CerfBoard LCD Display Size"
+	depends on FB_SA1100 && SA1100_CERF
+	default CERF_LCD_57_A
+
+config CERF_LCD_38_A
+	bool "3.8_Color"
+
+config CERF_LCD_38_B
+	bool "3.8_Mono"
+
+config CERF_LCD_57_A
+	bool "5.7"
+
+config CERF_LCD_72_A
+	bool "7.2"
+
+endchoice
+
+config SA1100_CERF_LCD_BACKLIGHT
+	bool "Cerfboard Backlight (CerfPDA)"
+	depends on FB_SA1100 && SA1100_CERF_CPLD
+
+config FB_CYBER2000
+	tristate "CyberPro 2000/2010/5000 support"
+	depends on FB && PCI
+	help
+	  This enables support for the Integraphics CyberPro 20x0 and 5000
+	  VGA chips used in the Rebel.com Netwinder and other machines.
+	  Say Y if you have a NetWinder or a graphics card containing this
+	  device, otherwise say N.
+
+config FB_APOLLO
+	bool
+	depends on FB && APOLLO
+	default y
+
+config FB_Q40
+	bool
+	depends on FB && Q40
+	default y
+
+config FB_AMIGA
+	tristate "Amiga native chipset support"
+	depends on FB && AMIGA
+	help
+	  This is the frame buffer device driver for the builtin graphics
+	  chipset found in Amigas.
+
+	  The driver is also available as a module ( = code which can be
+	  inserted and removed from the running kernel whenever you want). The
+	  module will be called amifb.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config FB_AMIGA_OCS
+	bool "Amiga OCS chipset support"
+	depends on FB_AMIGA
+	help
+	  This enables support for the original Agnus and Denise video chips,
+	  found in the Amiga 1000 and most A500's and A2000's. If you intend
+	  to run Linux on any of these systems, say Y; otherwise say N.
+
+config FB_AMIGA_ECS
+	bool "Amiga ECS chipset support"
+	depends on FB_AMIGA
+	help
+	  This enables support for the Enhanced Chip Set, found in later
+	  A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
+	  you intend to run Linux on any of these systems, say Y; otherwise
+	  say N.
+
+config FB_AMIGA_AGA
+	bool "Amiga AGA chipset support"
+	depends on FB_AMIGA
+	help
+	  This enables support for the Advanced Graphics Architecture (also
+	  known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
+	  and CD32. If you intend to run Linux on any of these systems, say Y;
+	  otherwise say N.
+
+config FB_CYBER
+	tristate "Amiga CyberVision support"
+	depends on FB && ZORRO
+	help
+	  This enables support for the Cybervision 64 graphics card from
+	  Phase5. Please note that its use is not all that intuitive (i.e. if
+	  you have any questions, be sure to ask!). Say N unless you have a
+	  Cybervision 64 or plan to get one before you next recompile the
+	  kernel. Please note that this driver DOES NOT support the
+	  Cybervision 64 3D card, as they use incompatible video chips.
+
+config FB_VIRGE
+	bool "Amiga CyberVision3D support (EXPERIMENTAL)"
+	depends on FB && ZORRO && EXPERIMENTAL
+	help
+	  This enables support for the Cybervision 64/3D graphics card from
+	  Phase5. Please note that its use is not all that intuitive (i.e. if
+	  you have any questions, be sure to ask!). Say N unless you have a
+	  Cybervision 64/3D or plan to get one before you next recompile the
+	  kernel. Please note that this driver DOES NOT support the older
+	  Cybervision 64 card, as they use incompatible video chips.
+
+config FB_RETINAZ3
+	tristate "Amiga RetinaZ3 support (EXPERIMENTAL)"
+	depends on FB && ZORRO && EXPERIMENTAL
+	help
+	  This enables support for the Retina Z3 graphics card. Say N unless
+	  you have a Retina Z3 or plan to get one before you next recompile
+	  the kernel.
+
+config FB_FM2
+	bool "Amiga FrameMaster II/Rainbow II support (EXPERIMENTAL)"
+	depends on FB && ZORRO && EXPERIMENTAL
+	help
+	  This is the frame buffer device driver for the Amiga FrameMaster
+	  card from BSC (exhibited 1992 but not shipped as a CBM product).
+
+config FB_ATARI
+	bool "Atari native chipset support"
+	depends on FB && ATARI
+	help
+	  This is the frame buffer device driver for the builtin graphics
+	  chipset found in Ataris.
+
+config FB_ATY
+	tristate "ATI Mach64 display support (EXPERIMENTAL)" if EXPERIMENTAL && PCI
+	depends on FB
+	help
+	  This driver supports graphics boards with the ATI Mach64 chips.
+	  Say Y if you have such a graphics board.
+
+	  The driver is also available as a module ( = code which can be
+	  inserted and removed from the running kernel whenever you want). The
+	  module will be called atyfb.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config FB_ATY
+	prompt "ATI Mach64 display support"
+	depends on FB && (SPARC64 && PCI && FB_PCI || ATARI)
+
+config FB_ATY_GX
+	bool "Mach64 GX support (EXPERIMENTAL)" if EXPERIMENTAL && PCI
+	depends on FB_ATY
+	default y if ATARI
+	help
+	  Say Y here to support use of the ATI Mach64 Graphics Expression
+	  board (or other boards based on the Mach64 GX chipset) as a
+	  framebuffer device.  The ATI product support page for these boards
+	  is at
+	  <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
+
+config FB_OF
+	bool "Open Firmware frame buffer device support"
+	depends on FB && PPC && ALL_PPC
+	help
+	  Say Y if you want support with Open Firmware for your graphics
+	  board.
+
+config FB_CONTROL
+	bool "Apple \"control\" display support"
+	depends on FB && PPC && ALL_PPC
+	help
+	  This driver supports a frame buffer for the graphics adapter in the
+	  Power Macintosh 7300 and others.
+
+config FB_PLATINUM
+	bool "Apple \"platinum\" display support"
+	depends on FB && PPC && ALL_PPC
+	help
+	  This driver supports a frame buffer for the "platinum" graphics
+	  adapter in some Power Macintoshes.
+
+config FB_VALKYRIE
+	bool "Apple \"valkyrie\" display support"
+	depends on FB && (MAC || PPC && ALL_PPC)
+	help
+	  This driver supports a frame buffer for the "valkyrie" graphics
+	  adapter in some Power Macintoshes.
+
+config FB_CT65550
+	bool "Chips 65550 display support"
+	depends on FB && PPC
+	help
+	  This is the frame buffer device driver for the Chips & Technologies
+	  65550 graphics chip in PowerBooks.
+
+config FB_IMSTT
+	bool "IMS Twin Turbo display support"
+	depends on FB && PPC
+	help
+	  The IMS Twin Turbo is a PCI-based frame buffer card bundled with
+	  many Macintosh and compatible computers.
+
+config FB_S3TRIO
+	bool "S3 Trio display support"
+	depends on FB && PPC
+	help
+	  If you have a S3 Trio say Y. Say N for S3 Virge.
+
+config FB_VGA16
+	tristate "VGA 16-color graphics console"
+	depends on FB && (X86 || PPC)
+	help
+	  This is the frame buffer device driver for VGA 16 color graphic
+	  cards. Say Y if you have such a card.
+
+	  This code is also available as a module. If you want to compile it
+	  as a module ( = code which can be inserted in and removed from the
+	  running kernel whenever you want), say M here and read
+	  <file:Documentation/modules.txt>.  The module will be called
+	  vga16fb.o.
+
+config FB_STI
+	bool "Generic STI frame buffer device support"
+	depends on FB && PARISC
+	---help---
+	  STI refers to the HP "Standard Text Interface" which is a set of
+	  BIOS routines contained in a ROM chip in HP PA-RISC based machines.
+	  Enabling this option will implement the linux framebuffer device and
+	  an fbcon color text console using calls to the STI BIOS routines.
+	  The HP framebuffer device is usually planar, uses a strange memory
+	  layout, and changing the plane mask to create colored pixels
+	  requires a call to the STI routines, so do not expect /dev/fb to
+	  actually be useful.  However, it is the best we have as far as
+	  graphics on the HP chipsets due to lack of hardware level
+	  documentation for the various on-board HP chipsets used in these
+	  systems.  It is sufficient for basic text console functions,
+	  including fonts.
+
+	  You should probably enable this option, unless you are having
+	  trouble getting video when booting the kernel (make sure it isn't
+	  just that you are running the console on the serial port, though).
+	  Really old HP boxes may not have STI, and must use the PDC BIOS
+	  console or the IODC BIOS.
+
+config FB_MAC
+	bool
+	depends on FB && MAC
+	default y
+
+#      bool '  Apple DAFB display support' CONFIG_FB_DAFB
+config FB_HP300
+	bool
+	depends on FB && HP300
+	default y
+
+config FB_TGA
+	tristate "TGA framebuffer support"
+	depends on FB && ALPHA
+	help
+	  This is the frame buffer device driver for generic TGA graphic
+	  cards. Say Y if you have one of those.
+
+config FB_VESA
+	bool "VESA VGA graphics console"
+	depends on FB && X86
+	help
+	  This is the frame buffer device driver for generic VESA 2.0
+	  compliant graphic cards. The older VESA 1.2 cards are not supported.
+	  You will get a boot time penguin logo at no additional cost. Please
+	  read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
+
+config FB_HGA
+	tristate "Hercules mono graphics console (EXPERIMENTAL)"
+	depends on FB && X86
+	help
+	  Say Y here if you have a Hercules mono graphics card.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted and removed from the running kernel whenever you want).
+	  The module will be called hgafb.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+	  As this card technology is 15 years old, most people will answer N
+	  here.
+
+config VIDEO_SELECT
+	bool
+	depends on FB && X86
+	default y
+
+config FB_SGIVW
+	tristate "SGI Visual Workstation framebuffer support"
+	depends on FB && VISWS
+	help
+	  SGI Visual Workstation support for framebuffer graphics.
+
+config BUS_I2C
+	bool
+	depends on FB && VISWS
+	default y
+
+config FB_SUN3
+	bool "Sun3 framebuffer support"
+	depends on FB && (SUN3 || SUN3X)
+
+config FB_BWTWO
+	bool "BWtwo support"
+	depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
+	help
+	  This is the frame buffer device driver for the BWtwo frame buffer.
+
+config FB_CGTHREE
+	bool "CGthree support"
+	depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
+	help
+	  This is the frame buffer device driver for the CGthree frame buffer.
+
+config FB_CGSIX
+	bool "CGsix (GX,TurboGX) support"
+	depends on FB && ((SPARC32 || SPARC64) && FB_SBUS || (SUN3 || SUN3X) && FB_SUN3)
+	help
+	  This is the frame buffer device driver for the CGsix (GX, TurboGX)
+	  frame buffer.
+
+config FB_PVR2
+	tristate "NEC PowerVR 2 display support"
+	depends on FB && SH_DREAMCAST
+	---help---
+	  Say Y here if you have a PowerVR 2 card in your box.  If you plan to
+	  run linux on your Dreamcast, you will have to say Y here.
+	  This driver may or may not work on other PowerVR 2 cards, but is
+	  totally untested.  Use at your own risk.  If unsure, say N.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted and removed from the running kernel whenever you want).
+	  The module will be called pvr2fb.o.  If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+	  You can pass several parameters to the driver at boot time or at
+	  module load time.  The parameters look like "video=pvr2:XXX", where
+	  the meaning of XXX can be found at the end of the main source file
+	  (<file:drivers/video/pvr2fb.c>). Please see the file
+	  <file:Documentation/fb/pvr2fb.txt>.
+
+config FB_PVR2_DEBUG
+	bool "Debug pvr2fb"
+	depends on FB_PVR2=y
+	help
+	  Say Y here if you wish for the pvr2fb driver to print out debugging
+	  messages. Most people will want to say N here. If unsure, you will
+	  also want to say N.
+
+config FB_E1355
+	bool "Epson 1355 framebuffer support"
+	depends on FB && SUPERH
+	help
+	  Build in support for the SED1355 Epson Research Embedded RAMDAC
+	  LCD/CRT Controller (since redesignated as the S1D13505) as a
+	  framebuffer.  Product specs at
+	  <http://www.erd.epson.com/vdc/html/products.htm>.
+
+config E1355_REG_BASE
+	hex "Register Base Address"
+	depends on FB_E1355
+	default "a8000000"
+	help
+	  Epson SED1355/S1D13505 LCD/CRT controller register base address.
+	  See the manuals at
+	  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
+	  discussion.
+
+config E1355_FB_BASE
+	hex "Framebuffer Base Address"
+	depends on FB_E1355
+	default "a8200000"
+	help
+	  Epson SED1355/S1D13505 LCD/CRT controller memory base address.  See
+	  the manuals at
+	  <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
+	  discussion.
+
+config FB_RIVA
+	tristate "nVidia Riva support (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && PCI
+	help
+	  This driver supports graphics boards with the nVidia Riva/Geforce
+	  chips.
+	  Say Y if you have such a graphics board.
+
+	  The driver is also available as a module ( = code which can be
+	  inserted and removed from the running kernel whenever you want). The
+	  module will be called rivafb.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config FB_MATROX
+	tristate "Matrox acceleration (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && PCI
+	---help---
+	  Say Y here if you have a Matrox Millennium, Matrox Millennium II,
+	  Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
+	  Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video,
+	  Matrox G400, G450 or G550 card in your box.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted and removed from the running kernel whenever you want).
+	  The module will be called matroxfb.o. If you want to compile it as
+	  a module, say M here and read <file:Documentation/modules.txt>.
+
+	  You can pass several parameters to the driver at boot time or at
+	  module load time. The parameters look like "video=matrox:XXX", and
+	  are described in <file:Documentation/fb/matroxfb.txt>.
+
+config FB_MATROX_MILLENIUM
+	bool "Millennium I/II support"
+	depends on FB_MATROX
+	help
+	  Say Y here if you have a Matrox Millennium or Matrox Millennium II
+	  video card. If you select "Advanced lowlevel driver options" below,
+	  you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
+	  packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
+	  also use font widths different from 8.
+
+config FB_MATROX_MYSTIQUE
+	bool "Mystique support"
+	depends on FB_MATROX
+	help
+	  Say Y here if you have a Matrox Mystique or Matrox Mystique 220
+	  video card. If you select "Advanced lowlevel driver options" below,
+	  you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
+	  packed pixel and 32 bpp packed pixel. You can also use font widths
+	  different from 8.
+
+config FB_MATROX_G450
+	bool "G100/G200/G400/G450/G550 support"
+	depends on FB_MATROX
+	---help---
+	  Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
+	  video card. If you select "Advanced lowlevel driver options", you
+	  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
+	  pixel and 32 bpp packed pixel. You can also use font widths
+	  different from 8.
+
+	  If you need support for G400 secondary head, you must first say Y to
+	  "I2C support" and "I2C bit-banging support" in the character devices
+	  section, and then to "Matrox I2C support" and "G400 second head
+	  support" here in the framebuffer section. G450/G550 secondary head
+	  and digital output are supported without additional modules.
+
+	  The driver starts in monitor mode. You must use the matroxset tool 
+	  (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to 
+	  swap primary and secondary head outputs, or to change output mode.  
+	  Secondary head driver always start in 640x480 resolution and you 
+	  must use fbset to change it.
+
+	  Do not forget that second head supports only 16 and 32 bpp
+	  packed pixels, so it is a good idea to compile them into the kernel
+	  too. You can use only some font widths, as the driver uses generic
+	  painting procedures (the secondary head does not use acceleration
+	  engine).
+
+	  G450/G550 hardware can display TV picture only from secondary CRTC,
+	  and it performs no scaling, so picture must have 525 or 625 lines.
+
+config FB_MATROX_G100A
+	bool "G100/G200/G400 support"
+	depends on FB_MATROX && !FB_MATROX_G450
+	---help---
+	  Say Y here if you have a Matrox G100, G200 or G400 based
+	  video card. If you select "Advanced lowlevel driver options", you
+	  should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
+	  pixel and 32 bpp packed pixel. You can also use font widths
+	  different from 8.
+
+	  If you need support for G400 secondary head, you must first say Y to
+	  "I2C support" and "I2C bit-banging support" in the character devices
+	  section, and then to "Matrox I2C support" and "G400 second head
+	  support" here in the framebuffer section.
+
+config FB_MATROX_G100
+	bool
+	depends on FB_MATROX && (FB_MATROX_G450 || FB_MATROX_G100A)
+	default y
+
+config FB_MATROX_I2C
+	tristate "Matrox I2C support"
+	depends on FB_MATROX && I2C_ALGOBIT
+	---help---
+	  This drivers creates I2C buses which are needed for accessing the
+	  DDC (I2C) bus present on all Matroxes, an I2C bus which
+	  interconnects Matrox optional devices, like MGA-TVO on G200 and
+	  G400, and the secondary head DDC bus, present on G400 only.
+
+	  You can say Y or M here if you want to experiment with monitor
+	  detection code. You must say Y or M here if you want to use either
+	  second head of G400 or MGA-TVO on G200 or G400.
+
+	  If you compile it as module, it will create a module named
+	  i2c-matroxfb.o.
+
+config FB_MATROX_MAVEN
+	tristate "G400 second head support"
+	depends on FB_MATROX_G100 && FB_MATROX_I2C
+	---help---
+	  WARNING !!! This support does not work with G450 !!!
+
+	  Say Y or M here if you want to use a secondary head (meaning two
+	  monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
+	  head is not compatible with accelerated XFree 3.3.x SVGA servers -
+	  secondary head output is blanked while you are in X. With XFree
+	  3.9.17 preview you can use both heads if you use SVGA over fbdev or
+	  the fbdev driver on first head and the fbdev driver on second head.
+
+	  If you compile it as module, two modules are created,
+	  matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
+	  both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
+	  also load i2c-matroxfb to get it to run.
+
+	  The driver starts in monitor mode and you must use the matroxset
+	  tool (available at
+	  <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
+	  PAL or NTSC or to swap primary and secondary head outputs.
+	  Secondary head driver also always start in 640x480 resolution, you
+	  must use fbset to change it.
+
+	  Also do not forget that second head supports only 16 and 32 bpp
+	  packed pixels, so it is a good idea to compile them into the kernel
+	  too.  You can use only some font widths, as the driver uses generic
+	  painting procedures (the secondary head does not use acceleration
+	  engine).
+
+config FB_MATROX_MULTIHEAD
+	bool "Multihead support"
+	depends on FB_MATROX
+	---help---
+	  Say Y here if you have more than one (supported) Matrox device in
+	  your computer and you want to use all of them for different monitors
+	  ("multihead"). If you have only one device, you should say N because
+	  the driver compiled with Y is larger and a bit slower, especially on
+	  ia32 (ix86).
+
+	  If you said M to "Matrox unified accelerated driver" and N here, you
+	  will still be able to use several Matrox devices simultaneously:
+	  insert several instances of the module matroxfb.o into the kernel
+	  with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
+	  for the different Matrox devices. This method is slightly faster but
+	  uses 40 KB of kernel memory per Matrox card.
+
+	  There is no need for enabling 'Matrox multihead support' if you have
+	  only one Matrox card in the box.
+
+config FB_ATY_CT
+	bool "Mach64 CT/VT/GT/LT (incl. 3D RAGE) support" if EXPERIMENTAL
+	depends on PCI && FB_ATY
+	default y if SPARC64 && FB_PCI
+	help
+	  Say Y here to support use of ATI's 64-bit Rage boards (or other
+	  boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
+	  framebuffer device.  The ATI product support page for these boards
+	  is at <http://support.ati.com/products/pc/mach64/>.
+
+config FB_RADEON
+	tristate "ATI Radeon display support (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && PCI
+	help
+	  Choose this option if you want to use an ATI Radeon graphics card as
+	  a framebuffer device.  There are both PCI and AGP versions.  You
+	  don't need to choose this to run the Radeon in plain VGA mode.
+	  There is a product page at
+	  <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
+
+config FB_ATY128
+	tristate "ATI Rage128 display support (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && PCI
+	help
+	  This driver supports graphics boards with the ATI Rage128 chips.
+	  Say Y if you have such a graphics board and read
+	  <file:Documentation/fb/aty128fb.txt>.
+
+	  The driver is also available as a module ( = code which can be
+	  inserted and removed from the running kernel whenever you want). The
+	  module will be called aty128fb.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config FB_SIS
+	tristate "SIS acceleration (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && PCI
+	help
+	  This is the frame buffer device driver for the SiS 630 and 640 Super
+	  Socket 7 UMA cards.  Specs available at <http://www.sis.com.tw/>.
+
+config FB_SIS_300
+	bool "SIS 630/540/730 support"
+	depends on FB_SIS
+	help
+	  This is the frame buffer device driver for the SiS 630 and related
+	  Super Socket 7 UMA cards.  Specs available at
+	  <http://www.sis.com.tw/>.
+
+config FB_SIS_315
+	bool "SIS 315H/315 support"
+	depends on FB_SIS
+	help
+	  This is the frame buffer device driver for the SiS 315 graphics
+	  card.  Specs available at <http://www.sis.com.tw/>.
+
+config FB_NEOMAGIC
+	tristate "NeoMagic display support (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && PCI
+	help
+	  This driver supports notebooks with NeoMagic PCI chips.
+	  Say Y if you have such a graphics card. 
+
+	  The driver is also available as a module ( = code which can be
+	  inserted and removed from the running kernel whenever you want). The
+	  module will be called neofb.o. If you want to compile it as a
+	  module, say M here and read Documentation/modules.txt.
+
+config FB_3DFX
+	tristate "3Dfx Banshee/Voodoo3 display support (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && PCI
+	help
+	  This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
+	  chips. Say Y if you have such a graphics board.
+
+	  The driver is also available as a module ( = code which can be
+	  inserted and removed from the running kernel whenever you want). The
+	  module will be called tdfxfb.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config FB_VOODOO1
+	tristate "3Dfx Voodoo Graphics (sst1) support (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && PCI
+	---help---
+	  Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or 
+	  Voodoo2 (cvg) based graphics card.
+
+	  This driver is also available as a module ( = code which can be 
+	  inserted and removed from the running kernel whenever you want).
+	  The module will be called sstfb.o. If you want to compile it as
+	  a module, say M here and read Documentation/modules.txt.
+
+	  WARNING: Do not use any application that uses the 3D engine
+	  (namely glide) while using this driver.
+	  Please read the file Documentation/fb/README-sstfb.txt for supported
+	  options and other important info  support.
+
+config FB_TRIDENT
+	tristate "Trident support (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && PCI
+	---help---
+	  This driver is supposed to support graphics boards with the
+	  Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
+	  but also on some motherboards. For more information, read
+	  <file:Documentation/fb/tridentfb.txt>
+
+	  Say Y if you have such a graphics board.
+
+	  The driver is also available as a module ( = code which can be
+	  inserted and removed from the running kernel whenever you want). The
+	  module will be called rivafb.o. If you want to compile it as a
+	  module, say M here and read <file:Documentation/modules.txt>.
+
+config FB_PM3
+	tristate "Permedia3 support (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL && PCI
+	help
+	  This is the frame buffer device driver for the 3DLabs Permedia3
+	  chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
+	  similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
+	  and maybe other boards.
+
+config FB_SBUS
+	bool "SBUS and UPA framebuffers"
+	depends on FB && (SPARC32 || SPARC64)
+	help
+	  Say Y if you want support for SBUS or UPA based frame buffer device.
+
+config FB_CREATOR
+	bool "Creator/Creator3D support"
+	depends on FB_SBUS && SPARC64
+	help
+	  This is the frame buffer device driver for the Creator and Creator3D
+	  graphics boards.
+
+config FB_TCX
+	bool "TCX (SS4/SS5 only) support"
+	depends on FB_SBUS && SPARC32
+	help
+	  This is the frame buffer device driver for the TCX 24/8bit frame
+	  buffer.
+
+config FB_CGFOURTEEN
+	bool "CGfourteen (SX) support"
+	depends on FB_SBUS && SPARC32
+	help
+	  This is the frame buffer device driver for the CGfourteen frame
+	  buffer on Desktop SPARCsystems with the SX graphics option.
+
+config FB_P9100
+	bool "P9100 (Sparcbook 3 only) support"
+	depends on FB_SBUS && SPARC32
+	help
+	  This is the frame buffer device driver for the P9100 card
+	  supported on Sparcbook 3 machines.
+
+config FB_LEO
+	bool "Leo (ZX) support"
+	depends on FB_SBUS
+	help
+	  This is the frame buffer device driver for the SBUS-based Sun ZX
+	  (leo) frame buffer cards.
+
+config FB_PCI
+	bool "PCI framebuffers"
+	depends on FB && PCI && (SPARC64 || SPARC32)
+
+config FB_IGA
+	bool "IGA 168x display support"
+	depends on SPARC32 && FB_PCI
+	help
+	  This is the framebuffer device for the INTERGRAPHICS 1680 and
+	  successor frame buffer cards.
+
+config FB_HIT
+	tristate "HD64461 Frame Buffer support"
+	depends on FB && HD64461
+	help
+	  This is the frame buffer device driver for the Hitachi HD64461 LCD
+	  frame buffer card.
+
+config FB_PMAG_BA
+	bool "PMAG-BA TURBOchannel framebuffer support"
+	depends on FB && DECSTATION && TC
+	help
+	  Say Y here to directly support the on-board PMAG-BA framebuffer in
+	  the 5000/1xx versions of the DECstation.  There is a page dedicated
+	  to Linux on DECstations at <http://decstation.unix-ag.org/>.
+
+config FB_PMAGB_B
+	bool "PMAGB-B TURBOchannel framebuffer spport"
+	depends on FB && DECSTATION && TC
+	help
+	  Say Y here to directly support the on-board PMAGB-B framebuffer in
+	  the 5000/1xx versions of the DECstation.  There is a page dedicated
+	  to Linux on DECstations at <http://decstation.unix-ag.org/>.
+
+config FB_MAXINE
+	bool "Maxine (Personal DECstation) onboard framebuffer spport"
+	depends on FB && DECSTATION && TC
+	help
+	  Say Y here to directly support the on-board framebuffer in the
+	  Maxine (5000/20, /25, /33) version of the DECstation.  There is a
+	  page dedicated to Linux on DECstations at <http://decstation.unix-ag.org/>.
+
+config FB_TX3912
+	bool "TMPTX3912/PR31700 frame buffer support"
+	depends on FB && NINO
+	help
+	  The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core
+	  see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
+
+	  Say Y here to enable kernel support for the on-board framebuffer.
+
+config FB_VIRTUAL
+	tristate "Virtual Frame Buffer support (ONLY FOR TESTING!) (EXPERIMENTAL)"
+	depends on FB && EXPERIMENTAL
+	---help---
+	  This is a `virtual' frame buffer device. It operates on a chunk of
+	  unswappable kernel memory instead of on the memory of a graphics
+	  board. This means you cannot see any output sent to this frame
+	  buffer device, while it does consume precious memory. The main use
+	  of this frame buffer device is testing and debugging the frame
+	  buffer subsystem. Do NOT enable it for normal systems! To protect
+	  the innocent, it has to be enabled explicitly at boot time using the
+	  kernel option `video=vfb:'.
+
+	  This driver is also available as a module ( = code which can be
+	  inserted and removed from the running kernel whenever you want). The
+	  module will be called vfb.o. If you want to compile it as a module,
+	  say M here and read <file:Documentation/modules.txt>.
+
+	  If unsure, say N.
+
+config FBCON_ADVANCED
+	bool "Advanced low level driver options"
+	depends on FB
+	---help---
+	  The frame buffer console uses character drawing routines that are
+	  tailored to the specific organization of pixels in the memory of
+	  your graphics hardware. These are called the low level frame buffer
+	  console drivers. Note that they are used for text console output
+	  only; they are NOT needed for graphical applications.
+
+	  If you say N here, the needed low level drivers are automatically
+	  enabled, depending on what frame buffer devices you selected above.
+	  This is recommended for most users.
+
+	  If you say Y here, you have more fine-grained control over which low
+	  level drivers are enabled. You can e.g. leave out low level drivers
+	  for color depths you do not intend to use for text consoles.
+
+	  Low level frame buffer console drivers can be modules ( = code which
+	  can be inserted and removed from the running kernel whenever you
+	  want). The modules will be called fbcon-*.o. If you want to compile
+	  (some of) them as modules, read <file:Documentation/modules.txt>.
+
+	  If unsure, say N.
+
+config FBCON_MFB
+	tristate "Monochrome support" if FBCON_ADVANCED
+	depends on FB
+	default m if !FBCON_ADVANCED && !FB_ACORN && FB_AMIGA!=y && !FB_ATARI && FB_CYBER!=y && !FB_BWTWO && FB_RETINAZ3!=y && !FB_VIRGE && FB_CLGEN!=y && (FB_AMIGA=m || FB_CYBER=m || FB_RETINAZ3=m || FB_CLGEN=m)
+	default y if !FBCON_ADVANCED && (FB_ACORN || FB_AMIGA=y || FB_ATARI || FB_CYBER=y || FB_BWTWO || FB_RETINAZ3=y || FB_VIRGE || FB_CLGEN=y)
+	help
+	  This is the low level frame buffer console driver for monochrome
+	  (2 colors) packed pixels.
+
+config FBCON_CFB2
+	tristate "2 bpp packed pixels support" if FBCON_ADVANCED
+	depends on FB
+	default y if !FBCON_ADVANCED && (FB_ACORN || FB_SA1100)
+	help
+	  This is the low level frame buffer console driver for 2 bits per
+	  pixel (4 colors) packed pixels.
+
+config FBCON_CFB4
+	tristate "4 bpp packed pixels support" if FBCON_ADVANCED
+	depends on FB
+	default y if !FBCON_ADVANCED && (FB_ACORN || FB_SA1100)
+	help
+	  This is the low level frame buffer console driver for 4 bits per
+	  pixel (16 colors) packed pixels.
+
+config FBCON_CFB8
+	tristate "8 bpp packed pixels support" if FBCON_ADVANCED
+	depends on FB
+	default m if !FBCON_ADVANCED && !FB_ACORN && !FB_ATARI && !FB_P9100 && FB_CYBER2000!=y && FB_RADEON!=y && FB_TGA!=y && FB_SIS!=y && FB_PM3!=y && !FB_TCX && !FB_CGTHREE && !FB_CONTROL && FB_CLGEN!=y && !FB_CGFOURTEEN && FB_TRIDENT!=y && !FB_VIRGE && FB_CYBER!=y && !FB_VALKYRIE && !FB_PLATINUM && !FB_IGA && FB_MATROX!=y && !FB_CT65550 && FB_PM2!=y && !FB_SA1100 && (FB_CYBER2000=m || FB_RADEON=m || FB_TGA=m || FB_SIS=m || FB_PM3=m || FB_CLGEN=m || FB_TRIDENT=m || FB_CYBER=m || FB_MATROX=m || FB_PM2=m)
+	default y if !FBCON_ADVANCED && (FB_ACORN || FB_ATARI || FB_P9100 || FB_CYBER2000=y || FB_RADEON=y || FB_TGA=y || FB_SIS=y || FB_PM3=y || FB_TCX || FB_CGTHREE || FB_CONTROL || FB_CLGEN=y || FB_CGFOURTEEN || FB_TRIDENT=y || FB_VIRGE || FB_CYBER=y || FB_VALKYRIE || FB_PLATINUM || FB_IGA || FB_MATROX=y || FB_CT65550 || FB_PM2=y || FB_SA1100)
+	help
+	  This is the low level frame buffer console driver for 8 bits per
+	  pixel (256 colors) packed pixels.
+
+config FBCON_CFB16
+	tristate "16 bpp packed pixels support" if FBCON_ADVANCED
+	depends on FB
+	default m if !FBCON_ADVANCED && !FB_ATARI && FB_PM3!=y && FB_SIS!=y && FB_PVR2!=y && FB_TRIDENT!=y && !FB_TBOX && FB_VOODOO1!=y && FB_RADEON!=y && !FB_CONTROL && FB_CLGEN!=y && !FB_VIRGE && FB_CYBER!=y && !FB_VALKYRIE && !FB_PLATINUM && !FB_CT65550 && FB_MATROX!=y && FB_PM2!=y && FB_CYBER2000!=y && !FB_SA1100 && (FB_SIS=m || FB_RADEON=m || FB_PVR2=m || FB_TRIDENT=m || FB_VOODOO1=m || FB_PM3=m || FB_CLGEN=m || FB_CYBER=m || FB_MATROX=m || FB_PM2=m || FB_CYBER2000=m || FB_SA1100)
+	default y if !FBCON_ADVANCED && (FB_ATARI || FB_PM3=y || FB_SIS=y || FB_PVR2=y || FB_TRIDENT=y || FB_TBOX || FB_VOODOO1=y || FB_RADEON=y || FB_CONTROL || FB_CLGEN=y || FB_VIRGE || FB_CYBER=y || FB_VALKYRIE || FB_PLATINUM || FB_CT65550 || FB_MATROX=y || FB_PM2=y || FB_CYBER2000=y || FB_SA1100)
+	help
+	  This is the low level frame buffer console driver for 15 or 16 bits
+	  per pixel (32K or 64K colors, also known as `hicolor') packed
+	  pixels.
+
+config FBCON_CFB24
+	tristate "24 bpp packed pixels support" if FBCON_ADVANCED
+	depends on FB
+	default m if !FBCON_ADVANCED && FB_ATY!=y && FB_VIRTUAL!=y && FB_CLGEN!=y && !FB_VESA && FB_MATROX!=y && FB_PM2!=y && FB_ATY128!=y && FB_RADEON!=y && FB_CYBER2000!=y && FB_PVR2!=y && FB_VOODOO1!=y && FB_NEOMAGIC!=y && (FB_ATY=m || FB_VIRTUAL=m || FB_CLGEN=m || FB_MATROX=m || FB_PM2=m || FB_ATY128=m || FB_RADEON=m || FB_CYBER2000=m || FB_PVR2=m || FB_VOODOO1=m || FB_NEOMAGIC=y)
+	default y if !FBCON_ADVANCED && (FB_ATY=y || FB_VIRTUAL=y || FB_CLGEN=y || FB_VESA || FB_MATROX=y || FB_PM2=y || FB_ATY128=y || FB_RADEON=y || FB_CYBER2000=y || FB_PVR2=y || FB_VOODOO1=y || FB_NEOMAGIC=y)
+	help
+	  This is the low level frame buffer console driver for 24 bits per
+	  pixel (16M colors, also known as `truecolor') packed pixels. It is
+	  NOT for `sparse' 32 bits per pixel mode.
+
+config FBCON_CFB32
+	tristate "32 bpp packed pixels support" if FBCON_ADVANCED
+	depends on FB
+	default m if !FBCON_ADVANCED && !FB_ATARI && FB_RADEON!=y && FB_VOODOO1!=y && FB_TRIDENT!=y && !FB_CONTROL && FB_CLGEN!=y && FB_TGA!=y && !FB_PLATINUM && FB_MATROX!=y && FB_PM2!=y && FB_PVR2!=y && FB_PM3!=y && FB_SIS!=y && (FB_RADEON=m || FB_VOODOO1=m || FB_TRIDENT=m || FB_CLGEN=m || FB_TGA=m || FB_MATROX=m || FB_PM2=m || FB_SIS=m || FB_PVR2=m || FB_PM3=m)
+	default y if !FBCON_ADVANCED && (FB_ATARI || FB_RADEON=y || FB_VOODOO1=y || FB_TRIDENT=y || FB_CONTROL || FB_CLGEN=y || FB_TGA=y || FB_PLATINUM || FB_MATROX=y || FB_PM2=y || FB_PVR2=y || FB_PM3=y || FB_SIS=y)
+	help
+	  This is the low level frame buffer console driver for 32 bits per
+	  pixel (16M colors, also known as `truecolor') sparse packed pixels.
+
+config FBCON_ACCEL
+	tristate "Hardware acceleration support" if FBCON_ADVANCED
+	depends on FB
+	default m if !FBCON_ADVANCED && FB_NEOMAGIC!=y && !FB_VESA && !FB_FM2 && FB_HIT!=y && !FB_HP300 && !FB_Q40 && !FB_ANAKIN && !FB_G364 && FB_VIRTUAL!=y && !FB_CLPS711X && !FB_PMAG_BA && !FB_PMAGB_B && FB_3DFX!=y && !FB_TX3912 && !FB_MAXINE && !FB_APOLLO && FB_ATY!=y && !FB_MAC && FB_RIVA!=y && !FB_OF && FB_SGIVW!=y && (FB_NEOMAGIC=m || FB_HIT=m || FB_VIRTUAL=m || FB_3DFX=m || FB_RIVA=m || FB_SGIVW=m)
+	default y if !FBCON_ADVANCED && (FB_NEOMAGIC=y || FB_VESA || FB_FM2 || FB_HIT=y || FB_HP300 || FB_Q40 || FB_ANAKIN || FB_G364 || FB_VIRTUAL=y || FB_CLPS711X || FB_PMAG_BA || FB_PMAGB_B || FB_3DFX=y || FB_TX3912 || FB_MAXINE || FB_APOLLO || FB_ATY=y || FB_MAC || FB_RIVA=y || FB_OF || FB_SGIVW=y)
+
+config FBCON_AFB
+	tristate "Amiga bitplanes support" if FBCON_ADVANCED
+	depends on FB
+	default m if !FBCON_ADVANCED && FB_AMIGA=m
+	default y if !FBCON_ADVANCED && FB_AMIGA=y
+	help
+	  This is the low level frame buffer console driver for 1 to 8
+	  bitplanes (2 to 256 colors) on Amiga.
+
+config FBCON_ILBM
+	tristate "Amiga interleaved bitplanes support" if FBCON_ADVANCED
+	depends on FB
+	default m if !FBCON_ADVANCED && FB_AMIGA=m
+	default y if !FBCON_ADVANCED && FB_AMIGA=y
+	help
+	  This is the low level frame buffer console driver for 1 to 8
+	  interleaved bitplanes (2 to 256 colors) on Amiga.
+
+config FBCON_IPLAN2P2
+	tristate "Atari interleaved bitplanes (2 planes) support" if FBCON_ADVANCED
+	depends on FB
+	default y if !FBCON_ADVANCED && FB_ATARI
+	help
+	  This is the low level frame buffer console driver for 2 interleaved
+	  bitplanes (4 colors) on Atari.
+
+config FBCON_IPLAN2P4
+	tristate "Atari interleaved bitplanes (4 planes) support" if FBCON_ADVANCED
+	depends on FB
+	default y if !FBCON_ADVANCED && FB_ATARI
+	help
+	  This is the low level frame buffer console driver for 4 interleaved
+	  bitplanes (16 colors) on Atari.
+
+config FBCON_IPLAN2P8
+	tristate "Atari interleaved bitplanes (8 planes) support" if FBCON_ADVANCED
+	depends on FB
+	default y if !FBCON_ADVANCED && FB_ATARI
+	help
+	  This is the low level frame buffer console driver for 8 interleaved
+	  bitplanes (256 colors) on Atari.
+
+#      tristate '    Atari interleaved bitplanes (16 planes) support' CONFIG_FBCON_IPLAN2P16
+config FBCON_VGA_PLANES
+	tristate "VGA 16-color planar support" if FBCON_ADVANCED
+	depends on FB
+	default m if !FBCON_ADVANCED && FB_VGA16=m
+	default y if !FBCON_ADVANCED && FB_VGA16=y
+	help
+	  This low level frame buffer console driver enable the kernel to use
+	  the 16-color planar modes of the old VGA cards where the bits of
+	  each pixel are separated into 4 planes.
+
+	  Only answer Y here if you have a (very old) VGA card that isn't VESA
+	  2 compatible.
+
+config FBCON_HGA
+	tristate "HGA monochrome support (EXPERIMENTAL)" if FBCON_ADVANCED
+	depends on FB
+	default m if !FBCON_ADVANCED && FB_HGA=m
+	default y if !FBCON_ADVANCED && FB_HGA=y
+	help
+	  This is the low level frame buffer console driver for Hercules mono
+	  graphics cards.
+
+# Guess what we need
+config FBCON_STI
+	tristate
+	depends on !FBCON_ADVANCED && FB_STI
+	default y
+
+config FBCON_FONTWIDTH8_ONLY
+	bool "Support only 8 pixels wide fonts"
+	depends on FB
+	help
+	  Answer Y here will make the kernel provide only the 8x8 fonts (these
+	  are the less readable).
+
+	  If unsure, say N.
+
+config FONT_SUN8x16
+	bool "Sparc console 8x16 font"
+	depends on FB && (!SPARC32 && !SPARC64 && FBCON_FONTS || SPARC32 || SPARC64)
+	help
+	  This is the high resolution console font for Sun machines. Say Y.
+
+config FONT_SUN12x22
+	bool "Sparc console 12x22 font (not supported by all drivers)"
+	depends on FB && !FBCON_FONTWIDTH8_ONLY && (!SPARC32 && !SPARC64 && FBCON_FONTS || SPARC32 || SPARC64)
+	help
+	  This is the high resolution console font for Sun machines with very
+	  big letters (like the letters used in the SPARC PROM). If the
+	  standard font is unreadable for you, say Y, otherwise say N.
+
+config FBCON_FONTS
+	bool "Select other fonts" if SPARC32 || SPARC64
+	depends on FB
+	help
+	  Say Y here if you would like to use fonts other than the default
+	  your frame buffer console usually use.
+
+	  Note that the answer to this question won't directly affect the
+	  kernel: saying N will just cause the configurator to skip all
+	  the questions about foreign fonts.
+
+	  If unsure, say N (the default choices are safe).
+
+config FBCON_FONTS
+	prompt "Select compiled-in fonts"
+	depends on FB && !SPARC32 && !SPARC64
+
+config FONT_8x8
+	bool "VGA 8x8 font" if FBCON_FONTS
+	depends on FB
+	default y if !SPARC32 && !SPARC64 && !FBCON_FONTS
+	help
+	  This is the "high resolution" font for the VGA frame buffer (the one
+	  provided by the text console 80x50 (and higher) modes).
+
+	  Note that this is a poor quality font. The VGA 8x16 font is quite a
+	  lot more readable.
+
+	  Given the resolution provided by the frame buffer device, answer N
+	  here is safe.
+
+config FONT_8x16
+	bool "VGA 8x16 font" if FBCON_FONTS
+	depends on FB
+	default y if !SPARC32 && !SPARC64 && !FBCON_FONTS
+	help
+	  This is the "high resolution" font for the VGA frame buffer (the one
+	  provided by the VGA text console 80x25 mode.
+
+	  If unsure, say Y.
+
+config FONT_6x11
+	bool "Mac console 6x11 font (not supported by all drivers)" if FBCON_FONTS
+	depends on FB && !FBCON_FONTWIDTH8_ONLY
+	default y if !SPARC32 && !SPARC64 && !FBCON_FONTS && MAC
+	help
+	  Small console font with Macintosh-style high-half glyphs.  Some Mac
+	  framebuffer drivers don't support this one at all.
+
+config FONT_PEARL_8x8
+	bool "Pearl (old m68k) console 8x8 font" if FBCON_FONTS
+	depends on FB
+	default y if !SPARC32 && !SPARC64 && !FBCON_FONTS && AMIGA
+	help
+	  Small console font with PC-style control-character and high-half
+	  glyphs.
+
+config FONT_ACORN_8x8
+	bool "Acorn console 8x8 font" if FBCON_FONTS
+	depends on FB
+	default y if !SPARC32 && !SPARC64 && !FBCON_FONTS && ARM && ARCH_ACORN
+	help
+	  Small console font with PC-style control characters and high-half
+	  glyphs.
+
+config FONT_MINI_4x6
+	bool "Mini 4x6 font"
+	depends on !SPARC32 && !SPARC64 && FBCON_FONTS
+
+endmenu
+

drivers/zorro/Kconfig

+#
+# Zorro configuration
+#
+config ZORRO_NAMES
+	bool "Zorro device name database"
+	depends on ZORRO
+	---help---
+	  By default, the kernel contains a database of all known Zorro device
+	  names to make the information in /proc/iomem comprehensible to the
+	  user. This database increases the size of the kernel image by about
+	  15KB, but it gets freed after the system boots up, so it doesn't
+	  take up kernel memory. Anyway, if you are building an installation
+	  floppy or kernel for an embedded system where kernel image size
+	  really matters, you can disable this feature and you'll get device
+	  ID numbers instead of names.
+
+	  When in doubt, say Y.
+