]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
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 | ||
180536f8 WVS |
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 | ||
1da177e4 LT |
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 | ||
1da177e4 LT |
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 | ||
b9d36b85 RK |
142 | config MPCORE_WATCHDOG |
143 | tristate "MPcore watchdog" | |
144 | depends on WATCHDOG && ARM_MPCORE_PLATFORM && LOCAL_TIMERS | |
145 | help | |
146 | Watchdog timer embedded into the MPcore system. | |
147 | ||
148 | To compile this driver as a module, choose M here: the | |
149 | module will be called mpcore_wdt. | |
150 | ||
1da177e4 LT |
151 | # X86 (i386 + ia64 + x86_64) Architecture |
152 | ||
153 | config ACQUIRE_WDT | |
154 | tristate "Acquire SBC Watchdog Timer" | |
155 | depends on WATCHDOG && X86 | |
156 | ---help--- | |
157 | This is the driver for the hardware watchdog on Single Board | |
158 | Computers produced by Acquire Inc (and others). This watchdog | |
159 | simply watches your kernel to make sure it doesn't freeze, and if | |
160 | it does, it reboots your computer after a certain amount of time. | |
161 | ||
162 | To compile this driver as a module, choose M here: the | |
163 | module will be called acquirewdt. | |
164 | ||
165 | Most people will say N. | |
166 | ||
167 | config ADVANTECH_WDT | |
168 | tristate "Advantech SBC Watchdog Timer" | |
169 | depends on WATCHDOG && X86 | |
170 | help | |
171 | If you are configuring a Linux kernel for the Advantech single-board | |
172 | computer, say `Y' here to support its built-in watchdog timer | |
173 | feature. More information can be found at | |
174 | <http://www.advantech.com.tw/products/> | |
175 | ||
176 | config ALIM1535_WDT | |
177 | tristate "ALi M1535 PMU Watchdog Timer" | |
178 | depends on WATCHDOG && X86 && PCI | |
179 | ---help--- | |
180 | This is the driver for the hardware watchdog on the ALi M1535 PMU. | |
181 | ||
182 | To compile this driver as a module, choose M here: the | |
183 | module will be called alim1535_wdt. | |
184 | ||
185 | Most people will say N. | |
186 | ||
187 | config ALIM7101_WDT | |
188 | tristate "ALi M7101 PMU Computer Watchdog" | |
189 | depends on WATCHDOG && X86 && PCI | |
190 | help | |
191 | This is the driver for the hardware watchdog on the ALi M7101 PMU | |
192 | as used in the x86 Cobalt servers. | |
193 | ||
194 | To compile this driver as a module, choose M here: the | |
195 | module will be called alim7101_wdt. | |
196 | ||
197 | Most people will say N. | |
198 | ||
199 | config SC520_WDT | |
200 | tristate "AMD Elan SC520 processor Watchdog" | |
201 | depends on WATCHDOG && X86 | |
202 | help | |
203 | This is the driver for the hardware watchdog built in to the | |
204 | AMD "Elan" SC520 microcomputer commonly used in embedded systems. | |
205 | This watchdog simply watches your kernel to make sure it doesn't | |
206 | freeze, and if it does, it reboots your computer after a certain | |
207 | amount of time. | |
208 | ||
209 | You can compile this driver directly into the kernel, or use | |
210 | it as a module. The module will be called sc520_wdt. | |
211 | ||
212 | config EUROTECH_WDT | |
213 | tristate "Eurotech CPU-1220/1410 Watchdog Timer" | |
214 | depends on WATCHDOG && X86 | |
215 | help | |
216 | Enable support for the watchdog timer on the Eurotech CPU-1220 and | |
217 | CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product | |
218 | information are at <http://www.eurotech.it/>. | |
219 | ||
220 | config IB700_WDT | |
221 | tristate "IB700 SBC Watchdog Timer" | |
222 | depends on WATCHDOG && X86 | |
223 | ---help--- | |
224 | This is the driver for the hardware watchdog on the IB700 Single | |
225 | Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog | |
226 | simply watches your kernel to make sure it doesn't freeze, and if | |
227 | it does, it reboots your computer after a certain amount of time. | |
228 | ||
229 | This driver is like the WDT501 driver but for slightly different hardware. | |
230 | ||
231 | To compile this driver as a module, choose M here: the | |
232 | module will be called ib700wdt. | |
233 | ||
234 | Most people will say N. | |
235 | ||
d532134d AP |
236 | config IBMASR |
237 | tristate "IBM Automatic Server Restart" | |
238 | depends on WATCHDOG && X86 | |
239 | help | |
240 | This is the driver for the IBM Automatic Server Restart watchdog | |
241 | timer builtin into some eServer xSeries machines. | |
242 | ||
243 | To compile this driver as a module, choose M here: the | |
244 | module will be called ibmasr. | |
245 | ||
1da177e4 LT |
246 | config WAFER_WDT |
247 | tristate "ICP Wafer 5823 Single Board Computer Watchdog" | |
248 | depends on WATCHDOG && X86 | |
249 | help | |
250 | This is a driver for the hardware watchdog on the ICP Wafer 5823 | |
251 | Single Board Computer (and probably other similar models). | |
252 | ||
253 | To compile this driver as a module, choose M here: the | |
254 | module will be called wafer5823wdt. | |
255 | ||
cc90ef0f DH |
256 | config I6300ESB_WDT |
257 | tristate "Intel 6300ESB Timer/Watchdog" | |
258 | depends on WATCHDOG && X86 && PCI | |
259 | ---help--- | |
260 | Hardware driver for the watchdog timer built into the Intel | |
261 | 6300ESB controller hub. | |
262 | ||
263 | To compile this driver as a module, choose M here: the | |
264 | module will be called i6300esb. | |
265 | ||
1da177e4 LT |
266 | config I8XX_TCO |
267 | tristate "Intel i8xx TCO Timer/Watchdog" | |
268 | depends on WATCHDOG && (X86 || IA64) && PCI | |
269 | ---help--- | |
270 | Hardware driver for the TCO timer built into the Intel 82801 | |
271 | I/O Controller Hub family. The TCO (Total Cost of Ownership) | |
272 | timer is a watchdog timer that will reboot the machine after | |
273 | its second expiration. The expiration time can be configured | |
274 | with the "heartbeat" parameter. | |
275 | ||
276 | On some motherboards the driver may fail to reset the chipset's | |
277 | NO_REBOOT flag which prevents the watchdog from rebooting the | |
278 | machine. If this is the case you will get a kernel message like | |
279 | "failed to reset NO_REBOOT flag, reboot disabled by hardware". | |
280 | ||
281 | To compile this driver as a module, choose M here: the | |
282 | module will be called i8xx_tco. | |
283 | ||
284 | config SC1200_WDT | |
285 | tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog" | |
286 | depends on WATCHDOG && X86 | |
287 | help | |
288 | This is a driver for National Semiconductor PC87307/PC97307 hardware | |
289 | watchdog cards as found on the SC1200. This watchdog is mainly used | |
290 | for power management purposes and can be used to power down the device | |
291 | during inactivity periods (includes interrupt activity monitoring). | |
292 | ||
293 | To compile this driver as a module, choose M here: the | |
294 | module will be called sc1200wdt. | |
295 | ||
296 | Most people will say N. | |
297 | ||
298 | config SCx200_WDT | |
299 | tristate "National Semiconductor SCx200 Watchdog" | |
300 | depends on WATCHDOG && SCx200 && PCI | |
301 | help | |
302 | Enable the built-in watchdog timer support on the National | |
303 | Semiconductor SCx200 processors. | |
304 | ||
305 | If compiled as a module, it will be called scx200_wdt. | |
306 | ||
307 | config 60XX_WDT | |
308 | tristate "SBC-60XX Watchdog Timer" | |
309 | depends on WATCHDOG && X86 | |
310 | help | |
311 | This driver can be used with the watchdog timer found on some | |
312 | single board computers, namely the 6010 PII based computer. | |
313 | It may well work with other cards. It reads port 0x443 to enable | |
314 | and re-set the watchdog timer, and reads port 0x45 to disable | |
315 | the watchdog. If you have a card that behave in similar ways, | |
316 | you can probably make this driver work with your card as well. | |
317 | ||
318 | You can compile this driver directly into the kernel, or use | |
319 | it as a module. The module will be called sbc60xxwdt. | |
320 | ||
3809ad38 IM |
321 | config SBC8360_WDT |
322 | tristate "SBC8360 Watchdog Timer" | |
323 | depends on WATCHDOG && X86 | |
324 | ---help--- | |
325 | ||
326 | This is the driver for the hardware watchdog on the SBC8360 Single | |
327 | Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com). | |
328 | ||
329 | To compile this driver as a module, choose M here: the | |
330 | module will be called sbc8360.ko. | |
331 | ||
332 | Most people will say N. | |
333 | ||
1da177e4 LT |
334 | config CPU5_WDT |
335 | tristate "SMA CPU5 Watchdog" | |
336 | depends on WATCHDOG && X86 | |
337 | ---help--- | |
338 | TBD. | |
339 | To compile this driver as a module, choose M here: the | |
340 | module will be called cpu5wdt. | |
341 | ||
342 | config W83627HF_WDT | |
343 | tristate "W83627HF Watchdog Timer" | |
344 | depends on WATCHDOG && X86 | |
345 | ---help--- | |
346 | This is the driver for the hardware watchdog on the W83627HF chipset | |
347 | as used in Advantech PC-9578 and Tyan S2721-533 motherboards | |
348 | (and likely others). This watchdog simply watches your kernel to | |
349 | make sure it doesn't freeze, and if it does, it reboots your computer | |
350 | after a certain amount of time. | |
351 | ||
352 | To compile this driver as a module, choose M here: the | |
353 | module will be called w83627hf_wdt. | |
354 | ||
355 | Most people will say N. | |
356 | ||
357 | config W83877F_WDT | |
358 | tristate "W83877F (EMACS) Watchdog Timer" | |
359 | depends on WATCHDOG && X86 | |
360 | ---help--- | |
361 | This is the driver for the hardware watchdog on the W83877F chipset | |
362 | as used in EMACS PC-104 motherboards (and likely others). This | |
363 | watchdog simply watches your kernel to make sure it doesn't freeze, | |
364 | and if it does, it reboots your computer after a certain amount of | |
365 | time. | |
366 | ||
367 | To compile this driver as a module, choose M here: the | |
368 | module will be called w83877f_wdt. | |
369 | ||
370 | Most people will say N. | |
371 | ||
b4cc4aa2 JMG |
372 | config W83977F_WDT |
373 | tristate "W83977F (PCM-5335) Watchdog Timer" | |
374 | depends on WATCHDOG && X86 | |
375 | ---help--- | |
376 | This is the driver for the hardware watchdog on the W83977F I/O chip | |
377 | as used in AAEON's PCM-5335 SBC (and likely others). This | |
378 | watchdog simply watches your kernel to make sure it doesn't freeze, | |
379 | and if it does, it reboots your computer after a certain amount of | |
380 | time. | |
381 | ||
382 | To compile this driver as a module, choose M here: the | |
383 | module will be called w83977f_wdt. | |
384 | ||
1da177e4 LT |
385 | config MACHZ_WDT |
386 | tristate "ZF MachZ Watchdog" | |
387 | depends on WATCHDOG && X86 | |
388 | ---help--- | |
389 | If you are using a ZF Micro MachZ processor, say Y here, otherwise | |
390 | N. This is the driver for the watchdog timer builtin on that | |
391 | processor using ZF-Logic interface. This watchdog simply watches | |
392 | your kernel to make sure it doesn't freeze, and if it does, it | |
393 | reboots your computer after a certain amount of time. | |
394 | ||
395 | To compile this driver as a module, choose M here: the | |
396 | module will be called machzwd. | |
397 | ||
eed6565f CC |
398 | config SBC_EPX_C3_WATCHDOG |
399 | tristate "Winsystems SBC EPX-C3 watchdog" | |
400 | depends on WATCHDOG && X86 | |
401 | ---help--- | |
402 | This is the driver for the built-in watchdog timer on the EPX-C3 | |
403 | Single-board computer made by Winsystems, Inc. | |
404 | ||
405 | *Note*: This hardware watchdog is not probeable and thus there | |
406 | is no way to know if writing to its IO address will corrupt | |
407 | your system or have any real effect. The only way to be sure | |
408 | that this driver does what you want is to make sure you | |
409 | are runnning it on an EPX-C3 from Winsystems with the watchdog | |
410 | timer at IO address 0x1ee and 0x1ef. It will write to both those | |
411 | IO ports. Basically, the assumption is made that if you compile | |
412 | this driver into your kernel and/or load it as a module, that you | |
413 | know what you are doing and that you are in fact running on an | |
414 | EPX-C3 board! | |
415 | ||
416 | To compile this driver as a module, choose M here: the | |
417 | module will be called sbc_epx_c3. | |
418 | ||
419 | ||
1da177e4 LT |
420 | # PowerPC Architecture |
421 | ||
422 | config 8xx_WDT | |
423 | tristate "MPC8xx Watchdog Timer" | |
424 | depends on WATCHDOG && 8xx | |
425 | ||
3be10211 JC |
426 | config MV64X60_WDT |
427 | tristate "MV64X60 (Marvell Discovery) Watchdog Timer" | |
428 | depends on WATCHDOG && MV64X60 | |
429 | ||
a2f40ccd KG |
430 | config BOOKE_WDT |
431 | tristate "PowerPC Book-E Watchdog Timer" | |
432 | depends on WATCHDOG && (BOOKE || 4xx) | |
39cdc4bf KG |
433 | ---help--- |
434 | Please see Documentation/watchdog/watchdog-api.txt for | |
435 | more information. | |
a2f40ccd | 436 | |
180536f8 WVS |
437 | # PPC64 Architecture |
438 | ||
439 | config WATCHDOG_RTAS | |
440 | tristate "RTAS watchdog" | |
441 | depends on WATCHDOG && PPC_RTAS | |
442 | help | |
443 | This driver adds watchdog support for the RTAS watchdog. | |
444 | ||
445 | To compile this driver as a module, choose M here. The module | |
446 | will be called wdrtas. | |
447 | ||
1da177e4 LT |
448 | # MIPS Architecture |
449 | ||
450 | config INDYDOG | |
451 | tristate "Indy/I2 Hardware Watchdog" | |
452 | depends on WATCHDOG && SGI_IP22 | |
453 | help | |
454 | Hardwaredriver for the Indy's/I2's watchdog. This is a | |
455 | watchdog timer that will reboot the machine after a 60 second | |
456 | timer expired and no process has written to /dev/watchdog during | |
457 | that time. | |
458 | ||
459 | # S390 Architecture | |
460 | ||
461 | config ZVM_WATCHDOG | |
462 | tristate "z/VM Watchdog Timer" | |
347a8dc3 | 463 | depends on WATCHDOG && S390 |
1da177e4 LT |
464 | help |
465 | IBM s/390 and zSeries machines running under z/VM 5.1 or later | |
466 | provide a virtual watchdog timer to their guest that cause a | |
467 | user define Control Program command to be executed after a | |
468 | timeout. | |
469 | ||
470 | To compile this driver as a module, choose M here. The module | |
471 | will be called vmwatchdog. | |
472 | ||
473 | # SUPERH Architecture | |
474 | ||
475 | config SH_WDT | |
476 | tristate "SuperH Watchdog" | |
477 | depends on WATCHDOG && SUPERH | |
478 | help | |
479 | This driver adds watchdog support for the integrated watchdog in the | |
480 | SuperH processors. If you have one of these processors and wish | |
481 | to have watchdog support enabled, say Y, otherwise say N. | |
482 | ||
483 | As a side note, saying Y here will automatically boost HZ to 1000 | |
484 | so that the timer has a chance to clear the overflow counter. On | |
485 | slower systems (such as the SH-2 and SH-3) this will likely yield | |
486 | some performance issues. As such, the WDT should be avoided here | |
487 | unless it is absolutely necessary. | |
488 | ||
489 | To compile this driver as a module, choose M here: the | |
490 | module will be called shwdt. | |
491 | ||
492 | # SPARC64 Architecture | |
493 | ||
494 | config WATCHDOG_CP1XXX | |
495 | tristate "CP1XXX Hardware Watchdog support" | |
496 | depends on WATCHDOG && SPARC64 && PCI | |
497 | ---help--- | |
498 | This is the driver for the hardware watchdog timers present on | |
499 | Sun Microsystems CompactPCI models CP1400 and CP1500. | |
500 | ||
501 | To compile this driver as a module, choose M here: the | |
502 | module will be called cpwatchdog. | |
503 | ||
504 | If you do not have a CompactPCI model CP1400 or CP1500, or | |
505 | another UltraSPARC-IIi-cEngine boardset with hardware watchdog, | |
506 | you should say N to this option. | |
507 | ||
508 | config WATCHDOG_RIO | |
509 | tristate "RIO Hardware Watchdog support" | |
510 | depends on WATCHDOG && SPARC64 && PCI | |
511 | help | |
512 | Say Y here to support the hardware watchdog capability on Sun RIO | |
513 | machines. The watchdog timeout period is normally one minute but | |
514 | can be changed with a boot-time parameter. | |
515 | ||
516 | # | |
517 | # ISA-based Watchdog Cards | |
518 | # | |
519 | ||
520 | comment "ISA-based Watchdog Cards" | |
521 | depends on WATCHDOG && ISA | |
522 | ||
523 | config PCWATCHDOG | |
524 | tristate "Berkshire Products ISA-PC Watchdog" | |
525 | depends on WATCHDOG && ISA | |
526 | ---help--- | |
527 | This is the driver for the Berkshire Products ISA-PC Watchdog card. | |
528 | This card simply watches your kernel to make sure it doesn't freeze, | |
529 | and if it does, it reboots your computer after a certain amount of | |
530 | time. This driver is like the WDT501 driver but for different | |
531 | hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC | |
532 | watchdog cards can be ordered from <http://www.berkprod.com/>. | |
533 | ||
534 | To compile this driver as a module, choose M here: the | |
535 | module will be called pcwd. | |
536 | ||
537 | Most people will say N. | |
538 | ||
539 | config MIXCOMWD | |
540 | tristate "Mixcom Watchdog" | |
541 | depends on WATCHDOG && ISA | |
542 | ---help--- | |
543 | This is a driver for the Mixcom hardware watchdog cards. This | |
544 | watchdog simply watches your kernel to make sure it doesn't freeze, | |
545 | and if it does, it reboots your computer after a certain amount of | |
546 | time. | |
547 | ||
548 | To compile this driver as a module, choose M here: the | |
549 | module will be called mixcomwd. | |
550 | ||
551 | Most people will say N. | |
552 | ||
553 | config WDT | |
554 | tristate "WDT Watchdog timer" | |
555 | depends on WATCHDOG && ISA | |
556 | ---help--- | |
557 | If you have a WDT500P or WDT501P watchdog board, say Y here, | |
558 | otherwise N. It is not possible to probe for this board, which means | |
559 | that you have to inform the kernel about the IO port and IRQ that | |
560 | is needed (you can do this via the io and irq parameters) | |
561 | ||
562 | To compile this driver as a module, choose M here: the | |
563 | module will be called wdt. | |
564 | ||
565 | config WDT_501 | |
566 | bool "WDT501 features" | |
567 | depends on WDT | |
568 | help | |
569 | Saying Y here and creating a character special file /dev/temperature | |
570 | with major number 10 and minor number 131 ("man mknod") will give | |
571 | you a thermometer inside your computer: reading from | |
572 | /dev/temperature yields one byte, the temperature in degrees | |
573 | Fahrenheit. This works only if you have a WDT501P watchdog board | |
574 | installed. | |
575 | ||
576 | If you want to enable the Fan Tachometer on the WDT501P, then you | |
577 | can do this via the tachometer parameter. Only do this if you have a | |
578 | fan tachometer actually set up. | |
579 | ||
580 | # | |
581 | # PCI-based Watchdog Cards | |
582 | # | |
583 | ||
584 | comment "PCI-based Watchdog Cards" | |
585 | depends on WATCHDOG && PCI | |
586 | ||
587 | config PCIPCWATCHDOG | |
588 | tristate "Berkshire Products PCI-PC Watchdog" | |
589 | depends on WATCHDOG && PCI | |
590 | ---help--- | |
591 | This is the driver for the Berkshire Products PCI-PC Watchdog card. | |
592 | This card simply watches your kernel to make sure it doesn't freeze, | |
593 | and if it does, it reboots your computer after a certain amount of | |
594 | time. The card can also monitor the internal temperature of the PC. | |
595 | More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>. | |
596 | ||
597 | To compile this driver as a module, choose M here: the | |
598 | module will be called pcwd_pci. | |
599 | ||
600 | Most people will say N. | |
601 | ||
602 | config WDTPCI | |
603 | tristate "PCI-WDT500/501 Watchdog timer" | |
604 | depends on WATCHDOG && PCI | |
605 | ---help--- | |
606 | If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N. | |
607 | ||
608 | To compile this driver as a module, choose M here: the | |
609 | module will be called wdt_pci. | |
610 | ||
611 | config WDT_501_PCI | |
612 | bool "PCI-WDT501 features" | |
613 | depends on WDTPCI | |
614 | help | |
615 | Saying Y here and creating a character special file /dev/temperature | |
616 | with major number 10 and minor number 131 ("man mknod") will give | |
617 | you a thermometer inside your computer: reading from | |
618 | /dev/temperature yields one byte, the temperature in degrees | |
619 | Fahrenheit. This works only if you have a PCI-WDT501 watchdog board | |
620 | installed. | |
621 | ||
622 | If you want to enable the Fan Tachometer on the PCI-WDT501, then you | |
623 | can do this via the tachometer parameter. Only do this if you have a | |
624 | fan tachometer actually set up. | |
625 | ||
626 | # | |
627 | # USB-based Watchdog Cards | |
628 | # | |
629 | ||
630 | comment "USB-based Watchdog Cards" | |
631 | depends on WATCHDOG && USB | |
632 | ||
633 | config USBPCWATCHDOG | |
634 | tristate "Berkshire Products USB-PC Watchdog" | |
635 | depends on WATCHDOG && USB | |
636 | ---help--- | |
637 | This is the driver for the Berkshire Products USB-PC Watchdog card. | |
638 | This card simply watches your kernel to make sure it doesn't freeze, | |
639 | and if it does, it reboots your computer after a certain amount of | |
640 | time. The card can also monitor the internal temperature of the PC. | |
641 | More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>. | |
642 | ||
643 | To compile this driver as a module, choose M here: the | |
644 | module will be called pcwd_usb. | |
645 | ||
646 | Most people will say N. | |
647 | ||
648 | endmenu |