X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=drivers%2Fchar%2Fwatchdog%2FKconfig;fp=drivers%2Fchar%2Fwatchdog%2FKconfig;h=c0dfcf273f0a5bd84e3be9dcd4f4a22835dcd198;hb=64ba3f394c830ec48a1c31b53dcae312c56f1604;hp=fff89c2d88fda66ad93bb40e822137b2751477b5;hpb=be1e6109ac94a859551f8e1774eb9a8469fe055c;p=linux-2.6.git

diff --git a/drivers/char/watchdog/Kconfig b/drivers/char/watchdog/Kconfig
index fff89c2d8..c0dfcf273 100644
--- a/drivers/char/watchdog/Kconfig
+++ b/drivers/char/watchdog/Kconfig
@@ -45,7 +45,7 @@ config WATCHDOG_NOWAYOUT
 comment "Watchdog Device Drivers"
 	depends on WATCHDOG
 
-# Architecture Independent
+# Architecture Independant
 
 config SOFT_WATCHDOG
 	tristate "Software watchdog"
@@ -60,13 +60,6 @@ config SOFT_WATCHDOG
 
 # ARM Architecture
 
-config AT91_WATCHDOG
-	tristate "AT91RM9200 watchdog"
-	depends on WATCHDOG && ARCH_AT91RM9200
-	help
-	  Watchdog timer embedded into AT91RM9200 chips. This will reboot your
-	  system when the timeout is reached.
-
 config 21285_WATCHDOG
 	tristate "DC21285 watchdog"
 	depends on WATCHDOG && FOOTBRIDGE
@@ -127,7 +120,7 @@ config S3C2410_WATCHDOG
 	  enabled.
 
 	  The driver is limited by the speed of the system's PCLK
-	  signal, so with reasonably fast systems (PCLK around 50-66MHz)
+	  signal, so with reasonbaly fast systems (PCLK around 50-66MHz)
 	  then watchdog intervals of over approximately 20seconds are
 	  unavailable.
 
@@ -155,16 +148,6 @@ config MPCORE_WATCHDOG
 	  To compile this driver as a module, choose M here: the
 	  module will be called mpcore_wdt.
 
-config EP93XX_WATCHDOG
-	tristate "EP93xx Watchdog"
-	depends on WATCHDOG && ARCH_EP93XX
-	help
-	  Say Y here if to include support for the watchdog timer
-	  embedded in the Cirrus Logic EP93xx family of devices.
-
-	  To compile this driver as a module, choose M here: the
-	  module will be called ep93xx_wdt.
-
 # X86 (i386 + ia64 + x86_64) Architecture
 
 config ACQUIRE_WDT
@@ -423,7 +406,7 @@ config SBC_EPX_C3_WATCHDOG
 	  is no way to know if writing to its IO address will corrupt
 	  your system or have any real effect.  The only way to be sure
 	  that this driver does what you want is to make sure you
-	  are running it on an EPX-C3 from Winsystems with the watchdog
+	  are runnning it on an EPX-C3 from Winsystems with the watchdog
 	  timer at IO address 0x1ee and 0x1ef.  It will write to both those
 	  IO ports.  Basically, the assumption is made that if you compile
 	  this driver into your kernel and/or load it as a module, that you
@@ -472,7 +455,7 @@ config INDYDOG
 	tristate "Indy/I2 Hardware Watchdog"
 	depends on WATCHDOG && SGI_IP22
 	help
-	  Hardware driver for the Indy's/I2's watchdog. This is a
+	  Hardwaredriver for the Indy's/I2's watchdog. This is a
 	  watchdog timer that will reboot the machine after a 60 second
 	  timer expired and no process has written to /dev/watchdog during
 	  that time.