Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # Watchdog device configuration |
| 3 | # |
| 4 | |
| 5 | menu "Watchdog Cards" |
| 6 | |
| 7 | config WATCHDOG |
| 8 | bool "Watchdog Timer Support" |
| 9 | ---help--- |
| 10 | If you say Y here (and to one of the following options) and create a |
| 11 | character special file /dev/watchdog with major number 10 and minor |
| 12 | number 130 using mknod ("man mknod"), you will get a watchdog, i.e.: |
| 13 | subsequently opening the file and then failing to write to it for |
| 14 | longer than 1 minute will result in rebooting the machine. This |
| 15 | could be useful for a networked machine that needs to come back |
| 16 | online as fast as possible after a lock-up. There's both a watchdog |
| 17 | implementation entirely in software (which can sometimes fail to |
| 18 | reboot the machine) and a driver for hardware watchdog boards, which |
| 19 | are more robust and can also keep track of the temperature inside |
| 20 | your computer. For details, read <file:Documentation/watchdog/watchdog.txt> |
| 21 | in the kernel source. |
| 22 | |
| 23 | The watchdog is usually used together with the watchdog daemon |
| 24 | which is available from |
| 25 | <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can |
| 26 | also monitor NFS connections and can reboot the machine when the process |
| 27 | table is full. |
| 28 | |
| 29 | If unsure, say N. |
| 30 | |
| 31 | config WATCHDOG_NOWAYOUT |
| 32 | bool "Disable watchdog shutdown on close" |
| 33 | depends on WATCHDOG |
| 34 | help |
| 35 | The default watchdog behaviour (which you get if you say N here) is |
| 36 | to stop the timer if the process managing it closes the file |
| 37 | /dev/watchdog. It's always remotely possible that this process might |
| 38 | get killed. If you say Y here, the watchdog cannot be stopped once |
| 39 | it has been started. |
| 40 | |
| 41 | # |
| 42 | # General Watchdog drivers |
| 43 | # |
| 44 | |
| 45 | comment "Watchdog Device Drivers" |
| 46 | depends on WATCHDOG |
| 47 | |
| 48 | # Architecture Independant |
| 49 | |
| 50 | config SOFT_WATCHDOG |
| 51 | tristate "Software watchdog" |
| 52 | depends on WATCHDOG |
| 53 | help |
| 54 | A software monitoring watchdog. This will fail to reboot your system |
| 55 | from some situations that the hardware watchdog will recover |
| 56 | from. Equally it's a lot cheaper to install. |
| 57 | |
| 58 | To compile this driver as a module, choose M here: the |
| 59 | module will be called softdog. |
| 60 | |
| 61 | # ARM Architecture |
| 62 | |
| 63 | config 21285_WATCHDOG |
| 64 | tristate "DC21285 watchdog" |
| 65 | depends on WATCHDOG && FOOTBRIDGE |
| 66 | help |
| 67 | The Intel Footbridge chip contains a builtin watchdog circuit. Say Y |
| 68 | here if you wish to use this. Alternatively say M to compile the |
| 69 | driver as a module, which will be called wdt285. |
| 70 | |
| 71 | This driver does not work on all machines. In particular, early CATS |
| 72 | boards have hardware problems that will cause the machine to simply |
| 73 | lock up if the watchdog fires. |
| 74 | |
| 75 | "If in doubt, leave it out" - say N. |
| 76 | |
| 77 | config 977_WATCHDOG |
| 78 | tristate "NetWinder WB83C977 watchdog" |
| 79 | depends on WATCHDOG && FOOTBRIDGE && ARCH_NETWINDER |
| 80 | help |
| 81 | Say Y here to include support for the WB977 watchdog included in |
| 82 | NetWinder machines. Alternatively say M to compile the driver as |
| 83 | a module, which will be called wdt977. |
| 84 | |
| 85 | Not sure? It's safe to say N. |
| 86 | |
Wim Van Sebroeck | 180536f | 2005-09-10 20:53:57 +0200 | [diff] [blame] | 87 | config IXP2000_WATCHDOG |
| 88 | tristate "IXP2000 Watchdog" |
| 89 | depends on WATCHDOG && ARCH_IXP2000 |
| 90 | help |
| 91 | Say Y here if to include support for the watchdog timer |
| 92 | in the Intel IXP2000(2400, 2800, 2850) network processors. |
| 93 | This driver can be built as a module by choosing M. The module |
| 94 | will be called ixp2000_wdt. |
| 95 | |
| 96 | Say N if you are unsure. |
| 97 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 98 | config IXP4XX_WATCHDOG |
| 99 | tristate "IXP4xx Watchdog" |
| 100 | depends on WATCHDOG && ARCH_IXP4XX |
| 101 | help |
| 102 | Say Y here if to include support for the watchdog timer |
| 103 | in the Intel IXP4xx network processors. This driver can |
| 104 | be built as a module by choosing M. The module will |
| 105 | be called ixp4xx_wdt. |
| 106 | |
| 107 | Note: The internal IXP4xx watchdog does a soft CPU reset |
| 108 | which doesn't reset any peripherals. There are circumstances |
| 109 | where the watchdog will fail to reset the board correctly |
| 110 | (e.g., if the boot ROM is in an unreadable state). |
| 111 | |
| 112 | Say N if you are unsure. |
| 113 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 114 | config S3C2410_WATCHDOG |
| 115 | tristate "S3C2410 Watchdog" |
| 116 | depends on WATCHDOG && ARCH_S3C2410 |
| 117 | help |
| 118 | Watchdog timer block in the Samsung S3C2410 chips. This will |
| 119 | reboot the system when the timer expires with the watchdog |
| 120 | enabled. |
| 121 | |
| 122 | The driver is limited by the speed of the system's PCLK |
| 123 | signal, so with reasonbaly fast systems (PCLK around 50-66MHz) |
| 124 | then watchdog intervals of over approximately 20seconds are |
| 125 | unavailable. |
| 126 | |
| 127 | The driver can be built as a module by choosing M, and will |
| 128 | be called s3c2410_wdt |
| 129 | |
| 130 | config SA1100_WATCHDOG |
| 131 | tristate "SA1100/PXA2xx watchdog" |
| 132 | depends on WATCHDOG && ( ARCH_SA1100 || ARCH_PXA ) |
| 133 | help |
| 134 | Watchdog timer embedded into SA11x0 and PXA2xx chips. This will |
| 135 | reboot your system when timeout is reached. |
| 136 | |
| 137 | NOTE: once enabled, this timer cannot be disabled. |
| 138 | |
| 139 | To compile this driver as a module, choose M here: the |
| 140 | module will be called sa1100_wdt. |
| 141 | |
| 142 | # X86 (i386 + ia64 + x86_64) Architecture |
| 143 | |
| 144 | config ACQUIRE_WDT |
| 145 | tristate "Acquire SBC Watchdog Timer" |
| 146 | depends on WATCHDOG && X86 |
| 147 | ---help--- |
| 148 | This is the driver for the hardware watchdog on Single Board |
| 149 | Computers produced by Acquire Inc (and others). This watchdog |
| 150 | simply watches your kernel to make sure it doesn't freeze, and if |
| 151 | it does, it reboots your computer after a certain amount of time. |
| 152 | |
| 153 | To compile this driver as a module, choose M here: the |
| 154 | module will be called acquirewdt. |
| 155 | |
| 156 | Most people will say N. |
| 157 | |
| 158 | config ADVANTECH_WDT |
| 159 | tristate "Advantech SBC Watchdog Timer" |
| 160 | depends on WATCHDOG && X86 |
| 161 | help |
| 162 | If you are configuring a Linux kernel for the Advantech single-board |
| 163 | computer, say `Y' here to support its built-in watchdog timer |
| 164 | feature. More information can be found at |
| 165 | <http://www.advantech.com.tw/products/> |
| 166 | |
| 167 | config ALIM1535_WDT |
| 168 | tristate "ALi M1535 PMU Watchdog Timer" |
| 169 | depends on WATCHDOG && X86 && PCI |
| 170 | ---help--- |
| 171 | This is the driver for the hardware watchdog on the ALi M1535 PMU. |
| 172 | |
| 173 | To compile this driver as a module, choose M here: the |
| 174 | module will be called alim1535_wdt. |
| 175 | |
| 176 | Most people will say N. |
| 177 | |
| 178 | config ALIM7101_WDT |
| 179 | tristate "ALi M7101 PMU Computer Watchdog" |
| 180 | depends on WATCHDOG && X86 && PCI |
| 181 | help |
| 182 | This is the driver for the hardware watchdog on the ALi M7101 PMU |
| 183 | as used in the x86 Cobalt servers. |
| 184 | |
| 185 | To compile this driver as a module, choose M here: the |
| 186 | module will be called alim7101_wdt. |
| 187 | |
| 188 | Most people will say N. |
| 189 | |
| 190 | config SC520_WDT |
| 191 | tristate "AMD Elan SC520 processor Watchdog" |
| 192 | depends on WATCHDOG && X86 |
| 193 | help |
| 194 | This is the driver for the hardware watchdog built in to the |
| 195 | AMD "Elan" SC520 microcomputer commonly used in embedded systems. |
| 196 | This watchdog simply watches your kernel to make sure it doesn't |
| 197 | freeze, and if it does, it reboots your computer after a certain |
| 198 | amount of time. |
| 199 | |
| 200 | You can compile this driver directly into the kernel, or use |
| 201 | it as a module. The module will be called sc520_wdt. |
| 202 | |
| 203 | config EUROTECH_WDT |
| 204 | tristate "Eurotech CPU-1220/1410 Watchdog Timer" |
| 205 | depends on WATCHDOG && X86 |
| 206 | help |
| 207 | Enable support for the watchdog timer on the Eurotech CPU-1220 and |
| 208 | CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product |
| 209 | information are at <http://www.eurotech.it/>. |
| 210 | |
| 211 | config IB700_WDT |
| 212 | tristate "IB700 SBC Watchdog Timer" |
| 213 | depends on WATCHDOG && X86 |
| 214 | ---help--- |
| 215 | This is the driver for the hardware watchdog on the IB700 Single |
| 216 | Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog |
| 217 | simply watches your kernel to make sure it doesn't freeze, and if |
| 218 | it does, it reboots your computer after a certain amount of time. |
| 219 | |
| 220 | This driver is like the WDT501 driver but for slightly different hardware. |
| 221 | |
| 222 | To compile this driver as a module, choose M here: the |
| 223 | module will be called ib700wdt. |
| 224 | |
| 225 | Most people will say N. |
| 226 | |
Andrey Panin | d532134 | 2005-08-19 23:15:11 +0200 | [diff] [blame] | 227 | config IBMASR |
| 228 | tristate "IBM Automatic Server Restart" |
| 229 | depends on WATCHDOG && X86 |
| 230 | help |
| 231 | This is the driver for the IBM Automatic Server Restart watchdog |
| 232 | timer builtin into some eServer xSeries machines. |
| 233 | |
| 234 | To compile this driver as a module, choose M here: the |
| 235 | module will be called ibmasr. |
| 236 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 237 | config WAFER_WDT |
| 238 | tristate "ICP Wafer 5823 Single Board Computer Watchdog" |
| 239 | depends on WATCHDOG && X86 |
| 240 | help |
| 241 | This is a driver for the hardware watchdog on the ICP Wafer 5823 |
| 242 | Single Board Computer (and probably other similar models). |
| 243 | |
| 244 | To compile this driver as a module, choose M here: the |
| 245 | module will be called wafer5823wdt. |
| 246 | |
David Hardeman | cc90ef0 | 2005-08-17 09:07:44 +0200 | [diff] [blame] | 247 | config I6300ESB_WDT |
| 248 | tristate "Intel 6300ESB Timer/Watchdog" |
| 249 | depends on WATCHDOG && X86 && PCI |
| 250 | ---help--- |
| 251 | Hardware driver for the watchdog timer built into the Intel |
| 252 | 6300ESB controller hub. |
| 253 | |
| 254 | To compile this driver as a module, choose M here: the |
| 255 | module will be called i6300esb. |
| 256 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 257 | config I8XX_TCO |
| 258 | tristate "Intel i8xx TCO Timer/Watchdog" |
| 259 | depends on WATCHDOG && (X86 || IA64) && PCI |
| 260 | ---help--- |
| 261 | Hardware driver for the TCO timer built into the Intel 82801 |
| 262 | I/O Controller Hub family. The TCO (Total Cost of Ownership) |
| 263 | timer is a watchdog timer that will reboot the machine after |
| 264 | its second expiration. The expiration time can be configured |
| 265 | with the "heartbeat" parameter. |
| 266 | |
| 267 | On some motherboards the driver may fail to reset the chipset's |
| 268 | NO_REBOOT flag which prevents the watchdog from rebooting the |
| 269 | machine. If this is the case you will get a kernel message like |
| 270 | "failed to reset NO_REBOOT flag, reboot disabled by hardware". |
| 271 | |
| 272 | To compile this driver as a module, choose M here: the |
| 273 | module will be called i8xx_tco. |
| 274 | |
| 275 | config SC1200_WDT |
| 276 | tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog" |
| 277 | depends on WATCHDOG && X86 |
| 278 | help |
| 279 | This is a driver for National Semiconductor PC87307/PC97307 hardware |
| 280 | watchdog cards as found on the SC1200. This watchdog is mainly used |
| 281 | for power management purposes and can be used to power down the device |
| 282 | during inactivity periods (includes interrupt activity monitoring). |
| 283 | |
| 284 | To compile this driver as a module, choose M here: the |
| 285 | module will be called sc1200wdt. |
| 286 | |
| 287 | Most people will say N. |
| 288 | |
| 289 | config SCx200_WDT |
| 290 | tristate "National Semiconductor SCx200 Watchdog" |
| 291 | depends on WATCHDOG && SCx200 && PCI |
| 292 | help |
| 293 | Enable the built-in watchdog timer support on the National |
| 294 | Semiconductor SCx200 processors. |
| 295 | |
| 296 | If compiled as a module, it will be called scx200_wdt. |
| 297 | |
| 298 | config 60XX_WDT |
| 299 | tristate "SBC-60XX Watchdog Timer" |
| 300 | depends on WATCHDOG && X86 |
| 301 | help |
| 302 | This driver can be used with the watchdog timer found on some |
| 303 | single board computers, namely the 6010 PII based computer. |
| 304 | It may well work with other cards. It reads port 0x443 to enable |
| 305 | and re-set the watchdog timer, and reads port 0x45 to disable |
| 306 | the watchdog. If you have a card that behave in similar ways, |
| 307 | you can probably make this driver work with your card as well. |
| 308 | |
| 309 | You can compile this driver directly into the kernel, or use |
| 310 | it as a module. The module will be called sbc60xxwdt. |
| 311 | |
Ian E. Morgan | 3809ad3 | 2005-09-01 22:49:17 +0200 | [diff] [blame^] | 312 | config SBC8360_WDT |
| 313 | tristate "SBC8360 Watchdog Timer" |
| 314 | depends on WATCHDOG && X86 |
| 315 | ---help--- |
| 316 | |
| 317 | This is the driver for the hardware watchdog on the SBC8360 Single |
| 318 | Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com). |
| 319 | |
| 320 | To compile this driver as a module, choose M here: the |
| 321 | module will be called sbc8360.ko. |
| 322 | |
| 323 | Most people will say N. |
| 324 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 325 | config CPU5_WDT |
| 326 | tristate "SMA CPU5 Watchdog" |
| 327 | depends on WATCHDOG && X86 |
| 328 | ---help--- |
| 329 | TBD. |
| 330 | To compile this driver as a module, choose M here: the |
| 331 | module will be called cpu5wdt. |
| 332 | |
| 333 | config W83627HF_WDT |
| 334 | tristate "W83627HF Watchdog Timer" |
| 335 | depends on WATCHDOG && X86 |
| 336 | ---help--- |
| 337 | This is the driver for the hardware watchdog on the W83627HF chipset |
| 338 | as used in Advantech PC-9578 and Tyan S2721-533 motherboards |
| 339 | (and likely others). This watchdog simply watches your kernel to |
| 340 | make sure it doesn't freeze, and if it does, it reboots your computer |
| 341 | after a certain amount of time. |
| 342 | |
| 343 | To compile this driver as a module, choose M here: the |
| 344 | module will be called w83627hf_wdt. |
| 345 | |
| 346 | Most people will say N. |
| 347 | |
| 348 | config W83877F_WDT |
| 349 | tristate "W83877F (EMACS) Watchdog Timer" |
| 350 | depends on WATCHDOG && X86 |
| 351 | ---help--- |
| 352 | This is the driver for the hardware watchdog on the W83877F chipset |
| 353 | as used in EMACS PC-104 motherboards (and likely others). This |
| 354 | watchdog simply watches your kernel to make sure it doesn't freeze, |
| 355 | and if it does, it reboots your computer after a certain amount of |
| 356 | time. |
| 357 | |
| 358 | To compile this driver as a module, choose M here: the |
| 359 | module will be called w83877f_wdt. |
| 360 | |
| 361 | Most people will say N. |
| 362 | |
| 363 | config MACHZ_WDT |
| 364 | tristate "ZF MachZ Watchdog" |
| 365 | depends on WATCHDOG && X86 |
| 366 | ---help--- |
| 367 | If you are using a ZF Micro MachZ processor, say Y here, otherwise |
| 368 | N. This is the driver for the watchdog timer builtin on that |
| 369 | processor using ZF-Logic interface. This watchdog simply watches |
| 370 | your kernel to make sure it doesn't freeze, and if it does, it |
| 371 | reboots your computer after a certain amount of time. |
| 372 | |
| 373 | To compile this driver as a module, choose M here: the |
| 374 | module will be called machzwd. |
| 375 | |
| 376 | # PowerPC Architecture |
| 377 | |
| 378 | config 8xx_WDT |
| 379 | tristate "MPC8xx Watchdog Timer" |
| 380 | depends on WATCHDOG && 8xx |
| 381 | |
James Chapman | 3be1021 | 2005-08-17 09:01:33 +0200 | [diff] [blame] | 382 | config MV64X60_WDT |
| 383 | tristate "MV64X60 (Marvell Discovery) Watchdog Timer" |
| 384 | depends on WATCHDOG && MV64X60 |
| 385 | |
Kumar Gala | a2f40cc | 2005-09-03 15:55:33 -0700 | [diff] [blame] | 386 | config BOOKE_WDT |
| 387 | tristate "PowerPC Book-E Watchdog Timer" |
| 388 | depends on WATCHDOG && (BOOKE || 4xx) |
Kumar Gala | 39cdc4b | 2005-09-03 15:55:39 -0700 | [diff] [blame] | 389 | ---help--- |
| 390 | Please see Documentation/watchdog/watchdog-api.txt for |
| 391 | more information. |
Kumar Gala | a2f40cc | 2005-09-03 15:55:33 -0700 | [diff] [blame] | 392 | |
Wim Van Sebroeck | 180536f | 2005-09-10 20:53:57 +0200 | [diff] [blame] | 393 | # PPC64 Architecture |
| 394 | |
| 395 | config WATCHDOG_RTAS |
| 396 | tristate "RTAS watchdog" |
| 397 | depends on WATCHDOG && PPC_RTAS |
| 398 | help |
| 399 | This driver adds watchdog support for the RTAS watchdog. |
| 400 | |
| 401 | To compile this driver as a module, choose M here. The module |
| 402 | will be called wdrtas. |
| 403 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 404 | # MIPS Architecture |
| 405 | |
| 406 | config INDYDOG |
| 407 | tristate "Indy/I2 Hardware Watchdog" |
| 408 | depends on WATCHDOG && SGI_IP22 |
| 409 | help |
| 410 | Hardwaredriver for the Indy's/I2's watchdog. This is a |
| 411 | watchdog timer that will reboot the machine after a 60 second |
| 412 | timer expired and no process has written to /dev/watchdog during |
| 413 | that time. |
| 414 | |
| 415 | # S390 Architecture |
| 416 | |
| 417 | config ZVM_WATCHDOG |
| 418 | tristate "z/VM Watchdog Timer" |
| 419 | depends on WATCHDOG && ARCH_S390 |
| 420 | help |
| 421 | IBM s/390 and zSeries machines running under z/VM 5.1 or later |
| 422 | provide a virtual watchdog timer to their guest that cause a |
| 423 | user define Control Program command to be executed after a |
| 424 | timeout. |
| 425 | |
| 426 | To compile this driver as a module, choose M here. The module |
| 427 | will be called vmwatchdog. |
| 428 | |
| 429 | # SUPERH Architecture |
| 430 | |
| 431 | config SH_WDT |
| 432 | tristate "SuperH Watchdog" |
| 433 | depends on WATCHDOG && SUPERH |
| 434 | help |
| 435 | This driver adds watchdog support for the integrated watchdog in the |
| 436 | SuperH processors. If you have one of these processors and wish |
| 437 | to have watchdog support enabled, say Y, otherwise say N. |
| 438 | |
| 439 | As a side note, saying Y here will automatically boost HZ to 1000 |
| 440 | so that the timer has a chance to clear the overflow counter. On |
| 441 | slower systems (such as the SH-2 and SH-3) this will likely yield |
| 442 | some performance issues. As such, the WDT should be avoided here |
| 443 | unless it is absolutely necessary. |
| 444 | |
| 445 | To compile this driver as a module, choose M here: the |
| 446 | module will be called shwdt. |
| 447 | |
| 448 | # SPARC64 Architecture |
| 449 | |
| 450 | config WATCHDOG_CP1XXX |
| 451 | tristate "CP1XXX Hardware Watchdog support" |
| 452 | depends on WATCHDOG && SPARC64 && PCI |
| 453 | ---help--- |
| 454 | This is the driver for the hardware watchdog timers present on |
| 455 | Sun Microsystems CompactPCI models CP1400 and CP1500. |
| 456 | |
| 457 | To compile this driver as a module, choose M here: the |
| 458 | module will be called cpwatchdog. |
| 459 | |
| 460 | If you do not have a CompactPCI model CP1400 or CP1500, or |
| 461 | another UltraSPARC-IIi-cEngine boardset with hardware watchdog, |
| 462 | you should say N to this option. |
| 463 | |
| 464 | config WATCHDOG_RIO |
| 465 | tristate "RIO Hardware Watchdog support" |
| 466 | depends on WATCHDOG && SPARC64 && PCI |
| 467 | help |
| 468 | Say Y here to support the hardware watchdog capability on Sun RIO |
| 469 | machines. The watchdog timeout period is normally one minute but |
| 470 | can be changed with a boot-time parameter. |
| 471 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 472 | # |
| 473 | # ISA-based Watchdog Cards |
| 474 | # |
| 475 | |
| 476 | comment "ISA-based Watchdog Cards" |
| 477 | depends on WATCHDOG && ISA |
| 478 | |
| 479 | config PCWATCHDOG |
| 480 | tristate "Berkshire Products ISA-PC Watchdog" |
| 481 | depends on WATCHDOG && ISA |
| 482 | ---help--- |
| 483 | This is the driver for the Berkshire Products ISA-PC Watchdog card. |
| 484 | This card simply watches your kernel to make sure it doesn't freeze, |
| 485 | and if it does, it reboots your computer after a certain amount of |
| 486 | time. This driver is like the WDT501 driver but for different |
| 487 | hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC |
| 488 | watchdog cards can be ordered from <http://www.berkprod.com/>. |
| 489 | |
| 490 | To compile this driver as a module, choose M here: the |
| 491 | module will be called pcwd. |
| 492 | |
| 493 | Most people will say N. |
| 494 | |
| 495 | config MIXCOMWD |
| 496 | tristate "Mixcom Watchdog" |
| 497 | depends on WATCHDOG && ISA |
| 498 | ---help--- |
| 499 | This is a driver for the Mixcom hardware watchdog cards. This |
| 500 | watchdog simply watches your kernel to make sure it doesn't freeze, |
| 501 | and if it does, it reboots your computer after a certain amount of |
| 502 | time. |
| 503 | |
| 504 | To compile this driver as a module, choose M here: the |
| 505 | module will be called mixcomwd. |
| 506 | |
| 507 | Most people will say N. |
| 508 | |
| 509 | config WDT |
| 510 | tristate "WDT Watchdog timer" |
| 511 | depends on WATCHDOG && ISA |
| 512 | ---help--- |
| 513 | If you have a WDT500P or WDT501P watchdog board, say Y here, |
| 514 | otherwise N. It is not possible to probe for this board, which means |
| 515 | that you have to inform the kernel about the IO port and IRQ that |
| 516 | is needed (you can do this via the io and irq parameters) |
| 517 | |
| 518 | To compile this driver as a module, choose M here: the |
| 519 | module will be called wdt. |
| 520 | |
| 521 | config WDT_501 |
| 522 | bool "WDT501 features" |
| 523 | depends on WDT |
| 524 | help |
| 525 | Saying Y here and creating a character special file /dev/temperature |
| 526 | with major number 10 and minor number 131 ("man mknod") will give |
| 527 | you a thermometer inside your computer: reading from |
| 528 | /dev/temperature yields one byte, the temperature in degrees |
| 529 | Fahrenheit. This works only if you have a WDT501P watchdog board |
| 530 | installed. |
| 531 | |
| 532 | If you want to enable the Fan Tachometer on the WDT501P, then you |
| 533 | can do this via the tachometer parameter. Only do this if you have a |
| 534 | fan tachometer actually set up. |
| 535 | |
| 536 | # |
| 537 | # PCI-based Watchdog Cards |
| 538 | # |
| 539 | |
| 540 | comment "PCI-based Watchdog Cards" |
| 541 | depends on WATCHDOG && PCI |
| 542 | |
| 543 | config PCIPCWATCHDOG |
| 544 | tristate "Berkshire Products PCI-PC Watchdog" |
| 545 | depends on WATCHDOG && PCI |
| 546 | ---help--- |
| 547 | This is the driver for the Berkshire Products PCI-PC Watchdog card. |
| 548 | This card simply watches your kernel to make sure it doesn't freeze, |
| 549 | and if it does, it reboots your computer after a certain amount of |
| 550 | time. The card can also monitor the internal temperature of the PC. |
| 551 | More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>. |
| 552 | |
| 553 | To compile this driver as a module, choose M here: the |
| 554 | module will be called pcwd_pci. |
| 555 | |
| 556 | Most people will say N. |
| 557 | |
| 558 | config WDTPCI |
| 559 | tristate "PCI-WDT500/501 Watchdog timer" |
| 560 | depends on WATCHDOG && PCI |
| 561 | ---help--- |
| 562 | If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N. |
| 563 | |
| 564 | To compile this driver as a module, choose M here: the |
| 565 | module will be called wdt_pci. |
| 566 | |
| 567 | config WDT_501_PCI |
| 568 | bool "PCI-WDT501 features" |
| 569 | depends on WDTPCI |
| 570 | help |
| 571 | Saying Y here and creating a character special file /dev/temperature |
| 572 | with major number 10 and minor number 131 ("man mknod") will give |
| 573 | you a thermometer inside your computer: reading from |
| 574 | /dev/temperature yields one byte, the temperature in degrees |
| 575 | Fahrenheit. This works only if you have a PCI-WDT501 watchdog board |
| 576 | installed. |
| 577 | |
| 578 | If you want to enable the Fan Tachometer on the PCI-WDT501, then you |
| 579 | can do this via the tachometer parameter. Only do this if you have a |
| 580 | fan tachometer actually set up. |
| 581 | |
| 582 | # |
| 583 | # USB-based Watchdog Cards |
| 584 | # |
| 585 | |
| 586 | comment "USB-based Watchdog Cards" |
| 587 | depends on WATCHDOG && USB |
| 588 | |
| 589 | config USBPCWATCHDOG |
| 590 | tristate "Berkshire Products USB-PC Watchdog" |
| 591 | depends on WATCHDOG && USB |
| 592 | ---help--- |
| 593 | This is the driver for the Berkshire Products USB-PC Watchdog card. |
| 594 | This card simply watches your kernel to make sure it doesn't freeze, |
| 595 | and if it does, it reboots your computer after a certain amount of |
| 596 | time. The card can also monitor the internal temperature of the PC. |
| 597 | More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>. |
| 598 | |
| 599 | To compile this driver as a module, choose M here: the |
| 600 | module will be called pcwd_usb. |
| 601 | |
| 602 | Most people will say N. |
| 603 | |
| 604 | endmenu |