diff options
| author | Matt LaPlante <kernel1@cyberdogtech.com> | 2006-07-04 21:20:51 -0400 |
|---|---|---|
| committer | Wim Van Sebroeck <wim@iguana.be> | 2006-08-15 05:17:22 -0400 |
| commit | 2621e2a155140b01c6ff57b3863cda2922c2c8bd (patch) | |
| tree | e66b4cffbd870e4e9244a4b48442b4908255a9ff | |
| parent | 9f737633e6ee54fc174282d49b2559bd2208391d (diff) | |
[WATCHDOG] Kconfig typos fix.
Three typos in drivers/char/watchdog/Kconfig...
Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Signed-off-by: Wim Van Sebroeck <wim@iguana.be>
| -rw-r--r-- | drivers/char/watchdog/Kconfig | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/drivers/char/watchdog/Kconfig b/drivers/char/watchdog/Kconfig index d53f664a4dd8..fff89c2d88fd 100644 --- a/drivers/char/watchdog/Kconfig +++ b/drivers/char/watchdog/Kconfig | |||
| @@ -45,7 +45,7 @@ config WATCHDOG_NOWAYOUT | |||
| 45 | comment "Watchdog Device Drivers" | 45 | comment "Watchdog Device Drivers" |
| 46 | depends on WATCHDOG | 46 | depends on WATCHDOG |
| 47 | 47 | ||
| 48 | # Architecture Independant | 48 | # Architecture Independent |
| 49 | 49 | ||
| 50 | config SOFT_WATCHDOG | 50 | config SOFT_WATCHDOG |
| 51 | tristate "Software watchdog" | 51 | tristate "Software watchdog" |
| @@ -127,7 +127,7 @@ config S3C2410_WATCHDOG | |||
| 127 | enabled. | 127 | enabled. |
| 128 | 128 | ||
| 129 | The driver is limited by the speed of the system's PCLK | 129 | The driver is limited by the speed of the system's PCLK |
| 130 | signal, so with reasonbaly fast systems (PCLK around 50-66MHz) | 130 | signal, so with reasonably fast systems (PCLK around 50-66MHz) |
| 131 | then watchdog intervals of over approximately 20seconds are | 131 | then watchdog intervals of over approximately 20seconds are |
| 132 | unavailable. | 132 | unavailable. |
| 133 | 133 | ||
| @@ -423,7 +423,7 @@ config SBC_EPX_C3_WATCHDOG | |||
| 423 | is no way to know if writing to its IO address will corrupt | 423 | is no way to know if writing to its IO address will corrupt |
| 424 | your system or have any real effect. The only way to be sure | 424 | your system or have any real effect. The only way to be sure |
| 425 | that this driver does what you want is to make sure you | 425 | that this driver does what you want is to make sure you |
| 426 | are runnning it on an EPX-C3 from Winsystems with the watchdog | 426 | are running it on an EPX-C3 from Winsystems with the watchdog |
| 427 | timer at IO address 0x1ee and 0x1ef. It will write to both those | 427 | timer at IO address 0x1ee and 0x1ef. It will write to both those |
| 428 | IO ports. Basically, the assumption is made that if you compile | 428 | IO ports. Basically, the assumption is made that if you compile |
| 429 | this driver into your kernel and/or load it as a module, that you | 429 | this driver into your kernel and/or load it as a module, that you |
| @@ -472,7 +472,7 @@ config INDYDOG | |||
| 472 | tristate "Indy/I2 Hardware Watchdog" | 472 | tristate "Indy/I2 Hardware Watchdog" |
| 473 | depends on WATCHDOG && SGI_IP22 | 473 | depends on WATCHDOG && SGI_IP22 |
| 474 | help | 474 | help |
| 475 | Hardwaredriver for the Indy's/I2's watchdog. This is a | 475 | Hardware driver for the Indy's/I2's watchdog. This is a |
| 476 | watchdog timer that will reboot the machine after a 60 second | 476 | watchdog timer that will reboot the machine after a 60 second |
| 477 | timer expired and no process has written to /dev/watchdog during | 477 | timer expired and no process has written to /dev/watchdog during |
| 478 | that time. | 478 | that time. |