Delete old-style config files.

18 files changed, 0 insertions, 883 deletions

diff --git a/drivers/input/Config.help b/drivers/input/Config.help
deleted file mode 100644
index 2e3ff3acd8c9..000000000000
--- a/drivers/input/Config.help
+++ /dev/null
@@ -1,90 +0,0 @@
-CONFIG_INPUT
-  Say Y here if you have any input device (mouse, keyboard, tablet,
-  joystick, steering wheel ...) connected to your system and want
-  it to be available to applications. This includes standard PS/2
-  keyboard and mouse.
-
-  Say N here if you have a headless (no monitor, no keyboard) system.
-
-  More information is available: <file:Documentation/input/input.txt>
-
-  If unsure, say Y.
-
-  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 input.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_INPUT_MOUSEDEV
-  Say Y here if you want your mouse to be accessible as char devices
-  13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
-  emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
-  programs (includung SVGAlib, GPM and X) will be able to use your
-  mouse.
-
-  If unsure, say Y.
-
-  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 mousedev.o. If you want to compile it as
-  a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_INPUT_MOUSEDEV_SCREEN_X
-  If you're using a digitizer, or a graphic tablet, and want to use
-  it as a mouse then the mousedev driver needs to know the X window
-  screen resolution you are using to correctly scale the data. If
-  you're not using a digitizer, this value is ignored.
-
-CONFIG_INPUT_MOUSEDEV_SCREEN_Y
-  If you're using a digitizer, or a graphic tablet, and want to use
-  it as a mouse then the mousedev driver needs to know the X window
-  screen resolution you are using to correctly scale the data. If
-  you're not using a digitizer, this value is ignored.
-
-CONFIG_INPUT_JOYDEV
-  Say Y here if you want your joystick or gamepad to be
-  accessible as char device 13:0+ - /dev/input/jsX device.
-
-  If unsure, say Y.
-
-  More information is available: <file:Documentation/input/joystick.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 joydev.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_INPUT_TSDEV
-  Say Y here if you have an application that only can understand the
-  Compaq touchscreen protocol for absolute pointer data. This is
-  useful namely for embedded configurations.
-
-  If unsure, 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 will be called tsdev.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_INPUT_EVDEV
-  Say Y here if you want your input device events be accessible
-  under char device 13:64+ - /dev/input/eventX in a generic way.
-
-  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 evdev.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_INPUT_EVBUG
-  Say Y here if you have a problem with the input subsystem and
-  want all events (keypresses, mouse movements), to be output to
-  the system log. While this is useful for debugging, it's also
-  a security threat - your keypresses include your passwords, of
-  course.
-
-  If unsure, 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 will be called joydev.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
diff --git a/drivers/input/Config.in b/drivers/input/Config.in
deleted file mode 100644
index 1b7dff514529..000000000000
--- a/drivers/input/Config.in
+++ /dev/null
@@ -1,40 +0,0 @@
-#
-# Input device configuration
-#
-
-mainmenu_option next_comment
-comment 'Input device support'
-
-define_tristate CONFIG_INPUT y
-
-comment 'Userland interfaces'
-dep_tristate '  Mouse interface' CONFIG_INPUT_MOUSEDEV $CONFIG_INPUT
-dep_mbool '    Provide legacy /dev/psaux device' CONFIG_INPUT_MOUSEDEV_PSAUX $CONFIG_INPUT_MOUSEDEV
-if [ "$CONFIG_INPUT_MOUSEDEV" != "n" ]; then
-   int '   Horizontal screen resolution' CONFIG_INPUT_MOUSEDEV_SCREEN_X 1024
-   int '   Vertical screen resolution' CONFIG_INPUT_MOUSEDEV_SCREEN_Y 768
-fi
-dep_tristate '  Joystick interface' CONFIG_INPUT_JOYDEV $CONFIG_INPUT
-dep_tristate '  Touchscreen interface' CONFIG_INPUT_TSDEV $CONFIG_INPUT
-if [ "$CONFIG_INPUT_TSDEV" != "n" ]; then
-   int '   Horizontal screen resolution' CONFIG_INPUT_TSDEV_SCREEN_X 240
-   int '   Vertical screen resolution' CONFIG_INPUT_TSDEV_SCREEN_Y 320 
-fi
-dep_tristate '  Event interface' CONFIG_INPUT_EVDEV $CONFIG_INPUT
-dep_tristate '  Event debugging' CONFIG_INPUT_EVBUG $CONFIG_INPUT
-
-
-comment 'Input I/O drivers'
-source drivers/input/gameport/Config.in
-source drivers/input/serio/Config.in
-
-comment 'Input Device Drivers'
-if [ "$CONFIG_INPUT" != "n" ]; then
-   source drivers/input/keyboard/Config.in
-   source drivers/input/mouse/Config.in
-   source drivers/input/joystick/Config.in
-   source drivers/input/touchscreen/Config.in
-   source drivers/input/misc/Config.in
-fi
-
-endmenu
diff --git a/drivers/input/gameport/Config.help b/drivers/input/gameport/Config.help
deleted file mode 100644
index 2d66d4e98260..000000000000
--- a/drivers/input/gameport/Config.help
+++ /dev/null
@@ -1,62 +0,0 @@
-CONFIG_GAMEPORT
-  Gameport support is for the standard 15-pin PC gameport. If you
-  have a joystick, gamepad, gameport card, a soundcard with a gameport
-  or anything else that uses the gameport, say Y or M here and also to
-  at least one of the hardware specific drivers.
-
-  For Ensoniq AudioPCI (ES1370), AudioPCI 97 (ES1371), ESS Solo1,
-  S3 SonicVibes, Trident 4DWave, SiS7018, and ALi 5451 gameport
-  support is provided by the sound drivers, so you won't need any
-  from the below listed modules. You still need to say Y here.
-
-  If unsure, say Y.
-
-  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 gameport.o. If you want to compile it as
-  a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_GAMEPORT_NS558
-  Say Y here if you have an ISA or PnP gameport.
-
-  If unsure, say Y.
-
-  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 ns558.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_GAMEPORT_L4
-  Say Y here if you have a PDPI Lightning 4 gamecard.
-
-  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 lightning.o. If you want to compile it as
-  a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_GAMEPORT_EMU10K1
-  Say Y here if you have a SoundBlaster Live! or SoundBlaster
-  Audigy card and want to use its gameport.
-
-  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 emu10k1-gp.o. If you want to compile it as
-  a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_GAMEPORT_VORTEX
-  Say Y here if you have an Aureal Vortex 1 or 2  card and want
-  to use its gameport.
-
-  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 vortex.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_GAMEPORT_CS461X
-  Say Y here if you have a Cirrus CS461x aka "Crystal SoundFusion"
-  PCI audio accelerator and want to use its gameport.
-
-  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 cs461x.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
diff --git a/drivers/input/gameport/Config.in b/drivers/input/gameport/Config.in
deleted file mode 100644
index 25e5f8bb84d4..000000000000
--- a/drivers/input/gameport/Config.in
+++ /dev/null
@@ -1,19 +0,0 @@
-#
-# Gameport configuration
-#
-
-tristate 'Gameport support' CONFIG_GAMEPORT
-
-if [ "$CONFIG_GAMEPORT" = "m" ]; then
-	define_tristate CONFIG_SOUND_GAMEPORT m
-fi
-if [ "$CONFIG_GAMEPORT" != "m" ]; then
-	define_tristate CONFIG_SOUND_GAMEPORT y
-fi
-
-dep_tristate '  Classic ISA and PnP gameport support' CONFIG_GAMEPORT_NS558 $CONFIG_GAMEPORT
-dep_tristate '  PDPI Lightning 4 gamecard support' CONFIG_GAMEPORT_L4 $CONFIG_GAMEPORT
-dep_tristate '  SB Live and Audigy gameport support' CONFIG_GAMEPORT_EMU10K1 $CONFIG_GAMEPORT
-dep_tristate '  Aureal Vortex, Vortex 2 gameport support' CONFIG_GAMEPORT_VORTEX $CONFIG_GAMEPORT
-dep_tristate '  ForteMedia FM801 gameport support' CONFIG_GAMEPORT_FM801 $CONFIG_GAMEPORT
-dep_tristate '  Crystal SoundFusion gameport support' CONFIG_GAMEPORT_CS461x $CONFIG_GAMEPORT
diff --git a/drivers/input/joystick/Config.help b/drivers/input/joystick/Config.help
deleted file mode 100644
index 0ae13e6c582e..000000000000
--- a/drivers/input/joystick/Config.help
+++ /dev/null
@@ -1,223 +0,0 @@
-CONFIG_INPUT_JOYSTICK
-  If you have a joystick, 6dof controller, gamepad, steering wheel,
-  weapon control system or something like that you can say Y here
-  and the list of supported devices will be displayed. This option
-  doesn't affect the kernel.
-
-  Please read the file <file:Documentation/input/joystick.txt> which
-  contains more information.
-
-CONFIG_JOYSTICK_ANALOG
-  Say Y here if you have a joystick that connects to the PC
-  gameport. In addition to the usual PC analog joystick, this driver
-  supports many extensions, including joysticks with throttle control,
-  with rudders, additional hats and buttons compatible with CH
-  Flightstick Pro, ThrustMaster FCS, 6 and 8 button gamepads, or
-  Saitek Cyborg joysticks. 
-
-  Please read the file <file:Documentation/input/joystick.txt> which
-  contains 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 analog.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_A3D
-  Say Y here if you have an FPGaming or MadCatz controller using the
-  A3D protocol over the PC gameport. 
-
-  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 a3d.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_ADI
-  Say Y here if you have a Logitech controller using the ADI
-  protocol over the PC gameport. 
-
-  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 adi.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_COBRA
-  Say Y here if you have a Creative Labs Blaster Cobra gamepad.
-
-  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 cobra.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_GF2K
-  Say Y here if you have a Genius Flight2000 or MaxFighter digitally
-  communicating joystick or gamepad.
-
-  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 gf2k.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_GRIP
-  Say Y here if you have a Gravis controller using the GrIP protocol
-  over the PC gameport. 
-
-  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 grip.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_GRIP_MP
-  Say Y here if you have the original Gravis GrIP MultiPort, a hub
-  that connects to the gameport and you connect gamepads to it.
-
-  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 grip_mp.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_GUILLEMOT
-  Say Y here if you have a Guillemot joystick using a digital
-  protocol over the PC gameport. 
-
-  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 guillemot.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_INTERACT
-  Say Y here if you have an InterAct gameport or joystick
-  communicating digitally over the gameport.
-
-  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 interact.o. If you want to compile it as
-  a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_SIDEWINDER
-  Say Y here if you have a Microsoft controller using the Digital
-  Overdrive protocol over PC gameport.
-
-  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 sidewinder.o. If you want to compile it
-  as a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_TMDC
-  Say Y here if you have a ThrustMaster controller using the
-  DirectConnect (BSP) protocol over the PC gameport. 
-
-  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 tmdc.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_WARRIOR
-  Say Y here if you have a Logitech WingMan Warrior joystick connected
-  to your computer's serial port. 
-
-  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 warrior.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_MAGELLAN
-  Say Y here if you have a Magellan or Space Mouse 6DOF controller
-  connected to your computer's serial port.
-
-  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 magellan.o. If you want to compile it as
-  a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_SPACEORB
-  Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
-  controller connected to your computer's serial port.
-
-  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 spaceorb.o. If you want to compile it as
-  a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_SPACEBALL
-  Say Y here if you have a SpaceTec SpaceBall 2003/3003/4000 FLX
-  controller connected to your computer's serial port. For the
-  SpaceBall 4000 USB model, use the USB HID 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 spaceball.o. If you want to compile it as
-  a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_STINGER
-  Say Y here if you have a Gravis Stinger connected to one of your
-  serial ports.
-
-  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 stinger.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_TWIDDLER
-  Say Y here if you have a Handykey Twiddler connected to your
-  computer's serial port and want to use it as a joystick.
-
-  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 twidjoy.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_DB9
-  Say Y here if you have a Sega Master System gamepad, Sega Genesis
-  gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
-  Commodore, Amstrad CPC joystick connected to your parallel port.
-  For more information on how to use the driver please read
-  <file:Documentation/input/joystick-parport.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 db9.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_GAMECON
-  Say Y here if you have a Nintendo Entertainment System gamepad,
-  Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
-  Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
-  Commodore, Amstrad CPC joystick connected to your parallel port.
-  For more information on how to use the driver please read
-  <file:Documentation/input/joystick-parport.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 gamecon.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_TURBOGRAFX
-  Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
-  and want to use it with Multisystem -- Atari, Amiga, Commodore,
-  Amstrad CPC joystick. For more information on how to use the driver
-  please read <file:Documentation/input/joystick-parport.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 turbografx.o. If you want to compile it
-  as a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_AMIGA
-  Say Y here if you have an Amiga with a digital joystick connected
-  to it.
-
-  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 amijoy.o. If you want to compile it as
-  a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_INPUT_JOYDUMP
-  Say Y here if you want to dump data from your joystick into the system
-  log for debugging purposes. Say N if you are making a production
-  configuration or aren't sure. 
-
-  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 joydump.o. If you want to compile it as
-  a module, say M here and read <file:Documentation/modules.txt>.
diff --git a/drivers/input/joystick/Config.in b/drivers/input/joystick/Config.in
deleted file mode 100644
index 832387fee1a3..000000000000
--- a/drivers/input/joystick/Config.in
+++ /dev/null
@@ -1,34 +0,0 @@
-#
-# Joystick driver configuration
-#
-
-bool 'Joysticks' CONFIG_INPUT_JOYSTICK
-
-dep_tristate '  Classic PC analog joysticks and gamepads' CONFIG_JOYSTICK_ANALOG $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT
-dep_tristate '  Assasin 3D and MadCatz Panther devices' CONFIG_JOYSTICK_A3D $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT
-dep_tristate '  Logitech ADI digital joysticks and gamepads' CONFIG_JOYSTICK_ADI $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT
-dep_tristate '  Creative Labs Blaster Cobra gamepad' CONFIG_JOYSTICK_COBRA $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT
-dep_tristate '  Genius Flight2000 Digital joysticks and gamepads' CONFIG_JOYSTICK_GF2K $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT
-dep_tristate '  Gravis GrIP joysticks and gamepads' CONFIG_JOYSTICK_GRIP $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT
-dep_tristate '  Gravis GrIP MultiPort' CONFIG_JOYSTICK_GRIP_MP $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT
-dep_tristate '  Guillemot joysticks and gamepads' CONFIG_JOYSTICK_GUILLEMOT $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT
-dep_tristate '  InterAct digital joysticks and gamepads' CONFIG_JOYSTICK_INTERACT $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT
-dep_tristate '  Microsoft SideWinder digital joysticks and gamepads' CONFIG_JOYSTICK_SIDEWINDER $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT
-dep_tristate '  ThrustMaster DirectConnect joysticks and gamepads' CONFIG_JOYSTICK_TMDC $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_GAMEPORT
-source drivers/input/joystick/iforce/Config.in
-dep_tristate '  Logitech WingMan Warrior joystick' CONFIG_JOYSTICK_WARRIOR $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO
-dep_tristate '  LogiCad3d Magellan/SpaceMouse 6dof controllers' CONFIG_JOYSTICK_MAGELLAN $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO
-dep_tristate '  SpaceTec SpaceOrb/Avenger 6dof controllers' CONFIG_JOYSTICK_SPACEORB $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO
-dep_tristate '  SpaceTec SpaceBall 6dof controllers' CONFIG_JOYSTICK_SPACEBALL $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO
-dep_tristate '  Gravis Stinger gamepad' CONFIG_JOYSTICK_STINGER $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO
-dep_tristate '  Twiddler as a joystick' CONFIG_JOYSTICK_TWIDDLER $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_SERIO
-
-dep_tristate '  Multisystem, Sega Genesis, Saturn joysticks and gamepads' CONFIG_JOYSTICK_DB9 $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_PARPORT
-dep_tristate '  Multisystem, NES, SNES, N64, PSX joysticks and gamepads' CONFIG_JOYSTICK_GAMECON $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_PARPORT
-dep_tristate '  Multisystem joysticks via TurboGraFX device' CONFIG_JOYSTICK_TURBOGRAFX $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK $CONFIG_PARPORT
-
-if [ "$CONFIG_AMIGA" = "y" ]; then
-   dep_tristate '  Amiga joysticks' CONFIG_JOYSTICK_AMIGA $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK
-fi
-
-dep_tristate '  Gameport data dumper' CONFIG_INPUT_JOYDUMP $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK
diff --git a/drivers/input/joystick/iforce/Config.help b/drivers/input/joystick/iforce/Config.help
deleted file mode 100644
index 3b823ee357e4..000000000000
--- a/drivers/input/joystick/iforce/Config.help
+++ /dev/null
@@ -1,21 +0,0 @@
-CONFIG_JOYSTICK_IFORCE
-  Say Y here if you have an I-Force joystick or steering wheel
-
-  You also must choose at least one of the two options 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 iforce.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_JOYSTICK_IFORCE_USB
-  Say Y here if you have an I-Force joystick or steering wheel
-  connected to your USB port. 
-
-CONFIG_JOYSTICK_IFORCE_232
-  Say Y here if you have an I-Force joystick or steering wheel
-  connected to your serial (COM) port.
-
-  You will need an additional utility called inputattach, see
-  Documentation/input/joystick.txt and ff.txt.
-
diff --git a/drivers/input/joystick/iforce/Config.in b/drivers/input/joystick/iforce/Config.in
deleted file mode 100644
index 13cdf88f48b6..000000000000
--- a/drivers/input/joystick/iforce/Config.in
+++ /dev/null
@@ -1,14 +0,0 @@
-#
-# I-Force driver configuration
-#
-
-dep_tristate '  I-Force devices' CONFIG_JOYSTICK_IFORCE $CONFIG_INPUT $CONFIG_INPUT_JOYSTICK
-
-if [ "$CONFIG_JOYSTICK_IFORCE" = "m" -o "$CONFIG_JOYSTICK_IFORCE" = "y" ]; then
-	if [ "$CONFIG_JOYSTICK_IFORCE" = "m" -o "$CONFIG_USB" = "y" ]; then
-		dep_mbool '    I-Force USB joysticks and wheels' CONFIG_JOYSTICK_IFORCE_USB $CONFIG_USB
-	fi
-	if [ "$CONFIG_JOYSTICK_IFORCE" = "m" -o "$CONFIG_SERIO" = "y" ]; then
-		dep_mbool '    I-Force Serial joysticks and wheels' CONFIG_JOYSTICK_IFORCE_232 $CONFIG_SERIO
-	fi
-fi
diff --git a/drivers/input/keyboard/Config.help b/drivers/input/keyboard/Config.help
deleted file mode 100644
index 0a318a6b2365..000000000000
--- a/drivers/input/keyboard/Config.help
+++ /dev/null
@@ -1,66 +0,0 @@
-CONFIG_INPUT_KEYBOARD
-  Say Y here, and a list of supported keyboards will be displayed.
-  This option doesn't affect the kernel.
-
-  If unsure, say Y.
-
-CONFIG_KEYBOARD_ATKBD
-  Say Y here if you want to use the standard AT keyboard. Usually
-  you'll need this, unless you have a different type keyboard (USB,
-  ADB or other). This also works for AT keyboards connected over
-  a PS/2 to serial converter.
-
-  If unsure, say Y.
-
-  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 atkbd.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_KEYBOARD_SUNKBD
-  Say Y here if you want to use a Sun Type 4 or Type 5 keyboard,
-  connected either to the Sun keyboard connector or to an serial
-  (RS-232) port via a simple 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 sunkbd.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_KEYBOARD_XTKBD
-  Say Y here if you want to use the old IBM PC/XT keyboard (or
-  compatible) on your system. This is only possible with a
-  parallel port keyboard adapter, you cannot connect it to the
-  keyboard port on a PC that runs Linux. 
-
-  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 xtkbd.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_KEYBOARD_NEWTON
-  Say Y here if you have a Newton keyboard on a serial port.
-
-  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 maple_keyb.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_KEYBOARD_MAPLE  
-  Say Y here if you have a DreamCast console running Linux and have
-  a keyboard attached to its Maple bus.
-
-  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 maple_keyb.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_KEYBOARD_AMIGA
-  Say Y here if you are running Linux on any AMIGA and have a keyboard
-  attached.	
-
-  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 amikbd.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
diff --git a/drivers/input/keyboard/Config.in b/drivers/input/keyboard/Config.in
deleted file mode 100644
index 81138e1fe206..000000000000
--- a/drivers/input/keyboard/Config.in
+++ /dev/null
@@ -1,18 +0,0 @@
-#
-# Input core configuration
-#
-
-bool 'Keyboards' CONFIG_INPUT_KEYBOARD
-
-dep_tristate '  AT keyboard support' CONFIG_KEYBOARD_ATKBD $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD $CONFIG_SERIO
-dep_tristate '  Sun Type 4 and Type 5 keyboard support' CONFIG_KEYBOARD_SUNKBD $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD $CONFIG_SERIO
-dep_tristate '  XT Keyboard support' CONFIG_KEYBOARD_XTKBD $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD $CONFIG_SERIO
-dep_tristate '  Newton keyboard' CONFIG_KEYBOARD_NEWTON $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD $CONFIG_SERIO
-
-if [ "$CONFIG_SH_DREAMCAST" = "y" ]; then
-   dep_tristate '  Maple bus keyboard support' CONFIG_KEYBOARD_MAPLE $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD $CONFIG_MAPLE
-fi
-
-if [ "$CONFIG_AMIGA" = "y" ]; then
-   dep_tristate '  Amiga keyboard' CONFIG_KEYBOARD_AMIGA $CONFIG_INPUT $CONFIG_INPUT_KEYBOARD
-fi
diff --git a/drivers/input/misc/Config.help b/drivers/input/misc/Config.help
deleted file mode 100644
index b03e459be96d..000000000000
--- a/drivers/input/misc/Config.help
+++ /dev/null
@@ -1,39 +0,0 @@
-CONFIG_INPUT_MISC
-
-  Say Y here, and a list of miscellaneous input drivers will be displayed.
-  Everything that didn't fit into the other categories is here. This option
-  doesn't affect the kernel.
-
-  If unsure, say Y.
-
-CONFIG_INPUT_PCSPKR
-  Say Y here if you want the standard PC Speaker to be used for
-  bells and whistles.
-
-  If unsure, say Y.
-
-  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 pcspkr.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_INPUT_SPARCSPKR
-  Say Y here if you want the standard Speaker on Sparc PCI systems
-  to be used for bells and whistles.
-
-  If unsure, say Y.
-
-  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 pcspkr.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-
-CONFIG_INPUT_UINPUT
-  Say Y here if you want to support user level drivers for input
-  subsystem accessible under char device 10:223 - /dev/input/uinput.
-
-  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 uinput.o.  If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.	    
diff --git a/drivers/input/misc/Config.in b/drivers/input/misc/Config.in
deleted file mode 100644
index af844186945d..000000000000
--- a/drivers/input/misc/Config.in
+++ /dev/null
@@ -1,14 +0,0 @@
-#
-# Input misc drivers configuration
-#
-
-bool 'Misc' CONFIG_INPUT_MISC
-
-dep_tristate '  PC Speaker support' CONFIG_INPUT_PCSPKR $CONFIG_INPUT $CONFIG_INPUT_MISC
-if [ "$CONFIG_SPARC32" = "y" -o "$CONFIG_SPARC64" = "y" ]; then
-   dep_tristate '  SPARC Speaker support' CONFIG_INPUT_SPARCSPKR $CONFIG_INPUT $CONFIG_INPUT_MISC
-fi
-if [ "$CONFIG_M68K" = "y" ]; then
-dep_tristate '  M68k Beeper support' CONFIG_INPUT_M68K_BEEP $CONFIG_INPUT $CONFIG_INPUT_MISC
-fi
-dep_tristate '  User level driver support' CONFIG_INPUT_UINPUT $CONFIG_INPUT $CONFIG_INPUT_MISC
diff --git a/drivers/input/mouse/Config.help b/drivers/input/mouse/Config.help
deleted file mode 100644
index c5b191e2c0eb..000000000000
--- a/drivers/input/mouse/Config.help
+++ /dev/null
@@ -1,87 +0,0 @@
-CONFIG_INPUT_MOUSE
-  Say Y here, and a list of supported mice will be displayed.
-  This option doesn't affect the kernel.
-
-  If unsure, say Y.
-
-CONFIG_MOUSE_PS2
-  Say Y here if you have a PS/2 mouse connected to your system. This
-  includes the standard 2 or 3-button PS/2 mouse, as well as PS/2
-  mice with wheels and extra buttons, Microsoft, Logitech or Genius
-  compatible.
-
-  If unsure, say Y.
-
-  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 psmouse.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_MOUSE_SERIAL
-  Say Y here if you have a serial (RS-232, COM port) mouse connected
-  to your system. This includes Sun, MouseSystems, Microsoft,
-  Logitech and all other compatible serial mice.
-
-  If unsure, 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 will be called sermouse.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_MOUSE_INPORT
-  Say Y here if you have an InPort, Microsoft or ATI XL busmouse.
-  They are rather rare these days.
-
-  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 inport.o. If you want to compile it as a
-  module, say M here and read <file.:Documentation/modules.txt>.
-
-CONFIG_MOUSE_ATIXL
-  Say Y here if your mouse is of the ATI XL variety.
-
-CONFIG_MOUSE_LOGIBM
-  Say Y here if you have a Logitech busmouse.
-  They are rather rare these days.
-
-  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 logibm.o. If you want to compile it as a
-  module, say M here and read <file.:Documentation/modules.txt>.
-
-CONFIG_MOUSE_PC110PAD
-  Say Y if you have the IBM PC-110 micro-notebook and want its
-  touchpad supported.
-
-  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 pc110pad.o. If you want to compile it as a
-  module, say M here and read <file.:Documentation/modules.txt>.
-
-CONFIG_MOUSE_MAPLE
-  Say Y if you have a DreamCast console and a mouse attached to
-  its Maple bus.
-
-  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 maplemouse.o. If you want to compile it as a
-  module, say M here and read <file.:Documentation/modules.txt>.
-
-CONFIG_MOUSE_AMIGA
-  Say Y here if you have an Amiga and want its native mouse
-  supported by the kernel.
-
-  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 amimouse.o. If you want to compile it as a
-  module, say M here and read <file.:Documentation/modules.txt>.
-
-CONFIG_MOUSE_ACORN
-  Say Y here if you have the Acorn RiscPC computer and want its
-  native mouse supported.
-
-  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 rpcmouse.o. If you want to compile it as a
-  module, say M here and read <file.:Documentation/modules.txt>.
diff --git a/drivers/input/mouse/Config.in b/drivers/input/mouse/Config.in
deleted file mode 100644
index d740c4188ebd..000000000000
--- a/drivers/input/mouse/Config.in
+++ /dev/null
@@ -1,24 +0,0 @@
-#
-# Mouse driver configuration
-#
-
-bool 'Mice' CONFIG_INPUT_MOUSE
-
-dep_tristate '  PS/2 mouse' CONFIG_MOUSE_PS2 $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_SERIO
-dep_tristate '  Serial mouse' CONFIG_MOUSE_SERIAL $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_SERIO
-
-dep_tristate '  InPort/MS/ATIXL busmouse' CONFIG_MOUSE_INPORT $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_ISA
-if [ "$CONFIG_MOUSE_INPORT" != "n" ]; then
-   bool '  ATI XL variant' CONFIG_MOUSE_ATIXL
-fi
-dep_tristate '  Logitech busmouse' CONFIG_MOUSE_LOGIBM $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_ISA
-dep_tristate '  IBM PC110 touchpad' CONFIG_MOUSE_PC110PAD $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_ISA
-if [ "$CONFIG_SH_DREAMCAST" = "y" ]; then
-  dep_tristate '  Maple bus mouse' CONFIG_MOUSE_MAPLE $CONFIG_INPUT $CONFIG_INPUT_MOUSE $CONFIG_MAPLE
-fi
-if [ "$CONFIG_AMIGA" = "y" ]; then
-   dep_tristate '  Amiga mouse' CONFIG_MOUSE_AMIGA $CONFIG_INPUT $CONFIG_INPUT_MOUSE
-fi
-if [ "$CONFIG_ARCH_ACORN" = "y" ]; then
-   dep_tristate '  Acorn RiscPC mouse' CONFIG_MOUSE_ACORN $CONFIG_INPUT $CONFIG_INPUT_MOUSE
-fi
diff --git a/drivers/input/serio/Config.help b/drivers/input/serio/Config.help
deleted file mode 100644
index ae97e4223fc0..000000000000
--- a/drivers/input/serio/Config.help
+++ /dev/null
@@ -1,73 +0,0 @@
-CONFIG_SERIO
-  Say Yes here if you have any input device that uses serial I/O to
-  communicate with the system. This includes the 
-		* standard AT keyboard and PS/2 mouse *
-  as well as serial mice, Sun keyboards, some joysticks and 6dof
-  devices and more.
-
-  If unsure, say Y.
-
-  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 serio.o. If you want to compile it
-  as a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_SERIO_I8042
-  i8042 is the chip over which the standard AT keyboard and PS/2
-  mouse are connected to the computer. If you use these devices,
-  you'll need to say Y here.
-
-  If unsure, say Y.
-
-  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 i8042.o. If you want to compile it
-  as a module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_SERIO_SERPORT
-  Say Y here if you plan to use an input device (mouse, joystick,
-  tablet, 6dof) that communicates over the RS232 serial (COM) port.
- 
-  More information is available: <file:Documentation/input/input.txt>
-
-  If unsure, say Y.
-
-  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 serport.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_SERIO_CT82C710
-  Say Y here if you have a Texas Instruments TravelMate notebook
-  equipped with the ct82c710 chip and want to use a mouse connected
-  to the "QuickPort".
-
-  If unsure, 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 will be called ct82c710.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_SERIO_PARKBD
-  Say Y here if you built a simple parallel port adapter to attach
-  an additional AT keyboard, XT keyboard or PS/2 mouse.
-
-  More information is available: <file:Documentation/input/input.txt>
-
-  If unsure, 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 will be called parkbd.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_SERIO_ACORN
-  Say Y here if you have the Acorn RiscPC and want to use an AT
-  keyboard connected to its keyboard controller.
-
-  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 rpckbd.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
diff --git a/drivers/input/serio/Config.in b/drivers/input/serio/Config.in
deleted file mode 100644
index 919740e1fc0d..000000000000
--- a/drivers/input/serio/Config.in
+++ /dev/null
@@ -1,23 +0,0 @@
-#
-# Input core configuration
-#
-
-tristate 'Serial i/o support' CONFIG_SERIO
-
-dep_tristate '  i8042 PC Keyboard controller' CONFIG_SERIO_I8042 $CONFIG_SERIO
-dep_tristate '  Serial port line discipline' CONFIG_SERIO_SERPORT $CONFIG_SERIO 
-dep_tristate '  ct82c710 Aux port controller' CONFIG_SERIO_CT82C710 $CONFIG_SERIO
-if [ "$CONFIG_Q40" = "y" ]; then
-   dep_tristate '  Q40 keyboard controller' CONFIG_SERIO_Q40KBD $CONFIG_SERIO
-fi
-dep_tristate '  Parallel port keyboard adapter' CONFIG_SERIO_PARKBD $CONFIG_SERIO $CONFIG_PARPORT
-
-if [ "$CONFIG_ARCH_ACORN" = "y" ]; then
-   dep_tristate '  Acorn RiscPC keyboard controller' CONFIG_SERIO_ACORN $CONFIG_SERIO
-fi
-if [ "$CONFIG_ARCH_INTEGRATOR" = "y" ]; then
-   dep_tristate '  AMBA KMI keyboard controller' CONFIG_SERIO_AMBAKMI $CONFIG_SERIO
-fi
-if [ "$CONFIG_SA1111" = "y" ]; then
-   dep_tristate '  Intel SA1111 keyboard controller' CONFIG_SERIO_SA1111 $CONFIG_SERIO
-fi
diff --git a/drivers/input/touchscreen/Config.help b/drivers/input/touchscreen/Config.help
deleted file mode 100644
index 4a8c1b7809eb..000000000000
--- a/drivers/input/touchscreen/Config.help
+++ /dev/null
@@ -1,26 +0,0 @@
-CONFIG_INPUT_TOUCHSCREEN
-  Say Y here, and a list of supported touchscreens will be displayed.
-  This option doesn't affect the kernel.
-
-  If unsure, say Y.
-
-CONFIG_TOUCHSCREEN_GUNZE
-  Say Y here if you have the Gunze AHL-51 touchscreen connected to
-  your system.
-
-  If unsure, 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 will be called gunze.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
-
-CONFIG_TOUCHSCREEN_BITSY
-  Say Y here if you have the h3600 (Bitsy) touchscreen.
-
-  If unsure, 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 will be called gunze.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>.
diff --git a/drivers/input/touchscreen/Config.in b/drivers/input/touchscreen/Config.in
deleted file mode 100644
index 7e441d44e1e1..000000000000
--- a/drivers/input/touchscreen/Config.in
+++ /dev/null
@@ -1,10 +0,0 @@
-#
-# Mouse driver configuration
-#
-
-bool 'Touchscreens' CONFIG_INPUT_TOUCHSCREEN
-
-if [ "$CONFIG_SA1100_BITSY" = "y" ]; then
-   dep_tristate '  Compaq iPAQ H3600 (Bitsy) touchscreen input driver' CONFIG_TOUCHSCREEN_BITSY $CONFIG_INPUT $CONFIG_INPUT_TOUCHSCREEN $CONFIG_SERIO
-fi
-dep_tristate '  Gunze AHL-51S touchscreen' CONFIG_TOUCHSCREEN_GUNZE $CONFIG_INPUT $CONFIG_INPUT_TOUCHSCREEN $CONFIG_SERIO