1#
2# Watchdog device configuration
3#
4
5menuconfig WATCHDOG
6	bool "Watchdog Timer Support"
7	---help---
8	  If you say Y here (and to one of the following options) and create a
9	  character special file /dev/watchdog with major number 10 and minor
10	  number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
11	  subsequently opening the file and then failing to write to it for
12	  longer than 1 minute will result in rebooting the machine. This
13	  could be useful for a networked machine that needs to come back
14	  on-line as fast as possible after a lock-up. There's both a watchdog
15	  implementation entirely in software (which can sometimes fail to
16	  reboot the machine) and a driver for hardware watchdog boards, which
17	  are more robust and can also keep track of the temperature inside
18	  your computer. For details, read <file:Documentation/watchdog/watchdog.txt>
19	  in the kernel source.
20
21	  The watchdog is usually used together with the watchdog daemon
22	  which is available from
23	  <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
24	  also monitor NFS connections and can reboot the machine when the process
25	  table is full.
26
27	  If unsure, say N.
28
29if WATCHDOG
30
31config WATCHDOG_NOWAYOUT
32	bool "Disable watchdog shutdown on close"
33	help
34	  The default watchdog behaviour (which you get if you say N here) is
35	  to stop the timer if the process managing it closes the file
36	  /dev/watchdog. It's always remotely possible that this process might
37	  get killed. If you say Y here, the watchdog cannot be stopped once
38	  it has been started.
39
40#
41# General Watchdog drivers
42#
43
44comment "Watchdog Device Drivers"
45
46# Architecture Independent
47
48config SOFT_WATCHDOG
49	tristate "Software watchdog"
50	help
51	  A software monitoring watchdog. This will fail to reboot your system
52	  from some situations that the hardware watchdog will recover
53	  from. Equally it's a lot cheaper to install.
54
55	  To compile this driver as a module, choose M here: the
56	  module will be called softdog.
57
58# ARM Architecture
59
60config AT91RM9200_WATCHDOG
61	tristate "AT91RM9200 watchdog"
62	depends on ARCH_AT91RM9200
63	help
64	  Watchdog timer embedded into AT91RM9200 chips. This will reboot your
65	  system when the timeout is reached.
66
67config 21285_WATCHDOG
68	tristate "DC21285 watchdog"
69	depends on FOOTBRIDGE
70	help
71	  The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
72	  here if you wish to use this. Alternatively say M to compile the
73	  driver as a module, which will be called wdt285.
74
75	  This driver does not work on all machines. In particular, early CATS
76	  boards have hardware problems that will cause the machine to simply
77	  lock up if the watchdog fires.
78
79	  "If in doubt, leave it out" - say N.
80
81config 977_WATCHDOG
82	tristate "NetWinder WB83C977 watchdog"
83	depends on FOOTBRIDGE && ARCH_NETWINDER
84	help
85	  Say Y here to include support for the WB977 watchdog included in
86	  NetWinder machines. Alternatively say M to compile the driver as
87	  a module, which will be called wdt977.
88
89	  Not sure? It's safe to say N.
90
91config IXP2000_WATCHDOG
92	tristate "IXP2000 Watchdog"
93	depends on ARCH_IXP2000
94	help
95	  Say Y here if to include support for the watchdog timer
96	  in the Intel IXP2000(2400, 2800, 2850) network processors.
97	  This driver can be built as a module by choosing M. The module
98	  will be called ixp2000_wdt.
99
100	  Say N if you are unsure.
101
102config IXP4XX_WATCHDOG
103	tristate "IXP4xx Watchdog"
104	depends on ARCH_IXP4XX
105	help
106	  Say Y here if to include support for the watchdog timer
107	  in the Intel IXP4xx network processors. This driver can
108	  be built as a module by choosing M. The module will
109	  be called ixp4xx_wdt.
110
111	  Note: The internal IXP4xx watchdog does a soft CPU reset
112	  which doesn't reset any peripherals. There are circumstances
113	  where the watchdog will fail to reset the board correctly
114	  (e.g., if the boot ROM is in an unreadable state).
115
116	  Say N if you are unsure.
117
118config KS8695_WATCHDOG
119	tristate "KS8695 watchdog"
120	depends on ARCH_KS8695
121	help
122	  Watchdog timer embedded into KS8695 processor. This will reboot your
123	  system when the timeout is reached.
124
125config S3C2410_WATCHDOG
126	tristate "S3C2410 Watchdog"
127	depends on ARCH_S3C2410
128	help
129	  Watchdog timer block in the Samsung S3C2410 chips. This will
130	  reboot the system when the timer expires with the watchdog
131	  enabled.
132
133	  The driver is limited by the speed of the system's PCLK
134	  signal, so with reasonably fast systems (PCLK around 50-66MHz)
135	  then watchdog intervals of over approximately 20seconds are
136	  unavailable.
137
138	  The driver can be built as a module by choosing M, and will
139	  be called s3c2410_wdt
140
141config SA1100_WATCHDOG
142	tristate "SA1100/PXA2xx watchdog"
143	depends on ARCH_SA1100 || ARCH_PXA
144	help
145	  Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
146	  reboot your system when timeout is reached.
147
148	  NOTE: once enabled, this timer cannot be disabled.
149
150	  To compile this driver as a module, choose M here: the
151	  module will be called sa1100_wdt.
152
153config MPCORE_WATCHDOG
154	tristate "MPcore watchdog"
155	depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
156	help
157	  Watchdog timer embedded into the MPcore system.
158
159	  To compile this driver as a module, choose M here: the
160	  module will be called mpcore_wdt.
161
162config EP93XX_WATCHDOG
163	tristate "EP93xx Watchdog"
164	depends on ARCH_EP93XX
165	help
166	  Say Y here if to include support for the watchdog timer
167	  embedded in the Cirrus Logic EP93xx family of devices.
168
169	  To compile this driver as a module, choose M here: the
170	  module will be called ep93xx_wdt.
171
172config OMAP_WATCHDOG
173	tristate "OMAP Watchdog"
174	depends on ARCH_OMAP16XX || ARCH_OMAP24XX
175	help
176	  Support for TI OMAP1610/OMAP1710/OMAP2420 watchdog.  Say 'Y' here to
177	  enable the OMAP1610/OMAP1710 watchdog timer.
178
179config PNX4008_WATCHDOG
180	tristate "PNX4008 Watchdog"
181	depends on ARCH_PNX4008
182	help
183	  Say Y here if to include support for the watchdog timer
184	  in the PNX4008 processor.
185	  This driver can be built as a module by choosing M. The module
186	  will be called pnx4008_wdt.
187
188	  Say N if you are unsure.
189
190# X86 (i386 + ia64 + x86_64) Architecture
191
192config ACQUIRE_WDT
193	tristate "Acquire SBC Watchdog Timer"
194	depends on X86
195	---help---
196	  This is the driver for the hardware watchdog on Single Board
197	  Computers produced by Acquire Inc (and others). This watchdog
198	  simply watches your kernel to make sure it doesn't freeze, and if
199	  it does, it reboots your computer after a certain amount of time.
200
201	  To compile this driver as a module, choose M here: the
202	  module will be called acquirewdt.
203
204	  Most people will say N.
205
206config ADVANTECH_WDT
207	tristate "Advantech SBC Watchdog Timer"
208	depends on X86
209	help
210	  If you are configuring a Linux kernel for the Advantech single-board
211	  computer, say `Y' here to support its built-in watchdog timer
212	  feature. More information can be found at
213	  <http://www.advantech.com.tw/products/>
214
215config ALIM1535_WDT
216	tristate "ALi M1535 PMU Watchdog Timer"
217	depends on X86 && PCI
218	---help---
219	  This is the driver for the hardware watchdog on the ALi M1535 PMU.
220
221	  To compile this driver as a module, choose M here: the
222	  module will be called alim1535_wdt.
223
224	  Most people will say N.
225
226config ALIM7101_WDT
227	tristate "ALi M7101 PMU Computer Watchdog"
228	depends on X86 && PCI
229	help
230	  This is the driver for the hardware watchdog on the ALi M7101 PMU
231	  as used in the x86 Cobalt servers.
232
233	  To compile this driver as a module, choose M here: the
234	  module will be called alim7101_wdt.
235
236	  Most people will say N.
237
238config SC520_WDT
239	tristate "AMD Elan SC520 processor Watchdog"
240	depends on X86
241	help
242	  This is the driver for the hardware watchdog built in to the
243	  AMD "Elan" SC520 microcomputer commonly used in embedded systems.
244	  This watchdog simply watches your kernel to make sure it doesn't
245	  freeze, and if it does, it reboots your computer after a certain
246	  amount of time.
247
248	  You can compile this driver directly into the kernel, or use
249	  it as a module.  The module will be called sc520_wdt.
250
251config EUROTECH_WDT
252	tristate "Eurotech CPU-1220/1410 Watchdog Timer"
253	depends on X86
254	help
255	  Enable support for the watchdog timer on the Eurotech CPU-1220 and
256	  CPU-1410 cards.  These are PC/104 SBCs. Spec sheets and product
257	  information are at <http://www.eurotech.it/>.
258
259config IB700_WDT
260	tristate "IB700 SBC Watchdog Timer"
261	depends on X86
262	---help---
263	  This is the driver for the hardware watchdog on the IB700 Single
264	  Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
265	  simply watches your kernel to make sure it doesn't freeze, and if
266	  it does, it reboots your computer after a certain amount of time.
267
268	  This driver is like the WDT501 driver but for slightly different hardware.
269
270	  To compile this driver as a module, choose M here: the
271	  module will be called ib700wdt.
272
273	  Most people will say N.
274
275config IBMASR
276	tristate "IBM Automatic Server Restart"
277	depends on X86
278	help
279	  This is the driver for the IBM Automatic Server Restart watchdog
280	  timer built-in into some eServer xSeries machines.
281
282	  To compile this driver as a module, choose M here: the
283	  module will be called ibmasr.
284
285config WAFER_WDT
286	tristate "ICP Wafer 5823 Single Board Computer Watchdog"
287	depends on X86
288	help
289	  This is a driver for the hardware watchdog on the ICP Wafer 5823
290	  Single Board Computer (and probably other similar models).
291
292	  To compile this driver as a module, choose M here: the
293	  module will be called wafer5823wdt.
294
295config I6300ESB_WDT
296	tristate "Intel 6300ESB Timer/Watchdog"
297	depends on X86 && PCI
298	---help---
299	  Hardware driver for the watchdog timer built into the Intel
300	  6300ESB controller hub.
301
302	  To compile this driver as a module, choose M here: the
303	  module will be called i6300esb.
304
305config ITCO_WDT
306	tristate "Intel TCO Timer/Watchdog"
307	depends on (X86 || IA64) && PCI
308	---help---
309	  Hardware driver for the intel TCO timer based watchdog devices.
310	  These drivers are included in the Intel 82801 I/O Controller
311	  Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
312	  controller hub.
313
314	  The TCO (Total Cost of Ownership) timer is a watchdog timer
315	  that will reboot the machine after its second expiration. The
316	  expiration time can be configured with the "heartbeat" parameter.
317
318	  On some motherboards the driver may fail to reset the chipset's
319	  NO_REBOOT flag which prevents the watchdog from rebooting the
320	  machine. If this is the case you will get a kernel message like
321	  "failed to reset NO_REBOOT flag, reboot disabled by hardware".
322
323	  To compile this driver as a module, choose M here: the
324	  module will be called iTCO_wdt.
325
326config ITCO_VENDOR_SUPPORT
327	bool "Intel TCO Timer/Watchdog Specific Vendor Support"
328	depends on ITCO_WDT
329	---help---
330	  Add vendor specific support to the intel TCO timer based watchdog
331	  devices. At this moment we only have additional support for some
332	  SuperMicro Inc. motherboards.
333
334config SC1200_WDT
335	tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
336	depends on X86
337	help
338	  This is a driver for National Semiconductor PC87307/PC97307 hardware
339	  watchdog cards as found on the SC1200. This watchdog is mainly used
340	  for power management purposes and can be used to power down the device
341	  during inactivity periods (includes interrupt activity monitoring).
342
343	  To compile this driver as a module, choose M here: the
344	  module will be called sc1200wdt.
345
346	  Most people will say N.
347
348config SCx200_WDT
349	tristate "National Semiconductor SCx200 Watchdog"
350	depends on SCx200 && PCI
351	help
352	  Enable the built-in watchdog timer support on the National
353	  Semiconductor SCx200 processors.
354
355	  If compiled as a module, it will be called scx200_wdt.
356
357config PC87413_WDT
358	tristate "NS PC87413 watchdog"
359	depends on X86
360	---help---
361	  This is the driver for the hardware watchdog on the PC87413 chipset
362	  This watchdog simply watches your kernel to make sure it doesn't
363	  freeze, and if it does, it reboots your computer after a certain
364	  amount of time.
365
366	  To compile this driver as a module, choose M here: the
367	  module will be called pc87413_wdt.
368
369	  Most people will say N.
370 
371config 60XX_WDT
372	tristate "SBC-60XX Watchdog Timer"
373	depends on X86
374	help
375	  This driver can be used with the watchdog timer found on some
376	  single board computers, namely the 6010 PII based computer.
377	  It may well work with other cards.  It reads port 0x443 to enable
378	  and re-set the watchdog timer, and reads port 0x45 to disable
379	  the watchdog.  If you have a card that behave in similar ways,
380	  you can probably make this driver work with your card as well.
381
382	  You can compile this driver directly into the kernel, or use
383	  it as a module.  The module will be called sbc60xxwdt.
384
385config SBC8360_WDT
386	tristate "SBC8360 Watchdog Timer"
387	depends on X86
388	---help---
389
390	  This is the driver for the hardware watchdog on the SBC8360 Single
391	  Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
392
393	  To compile this driver as a module, choose M here: the
394	  module will be called sbc8360.ko.
395
396	  Most people will say N.
397
398config CPU5_WDT
399	tristate "SMA CPU5 Watchdog"
400	depends on X86
401	---help---
402	  TBD.
403	  To compile this driver as a module, choose M here: the
404	  module will be called cpu5wdt.
405
406config SMSC37B787_WDT
407	tristate "Winbond SMsC37B787 Watchdog Timer"
408	depends on X86
409	---help---
410	  This is the driver for the hardware watchdog component on the
411	  Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
412	  from Vision Systems and maybe others.
413
414	  This watchdog simply watches your kernel to make sure it doesn't
415	  freeze, and if it does, it reboots your computer after a certain
416	  amount of time.
417
418	  Usually a userspace daemon will notify the kernel WDT driver that
419	  userspace is still alive, at regular intervals.
420
421	  To compile this driver as a module, choose M here: the
422	  module will be called smsc37b787_wdt.
423
424	  Most people will say N.
425
426config W83627HF_WDT
427	tristate "W83627HF Watchdog Timer"
428	depends on X86
429	---help---
430	  This is the driver for the hardware watchdog on the W83627HF chipset
431	  as used in Advantech PC-9578 and Tyan S2721-533 motherboards
432	  (and likely others).  This watchdog simply watches your kernel to
433	  make sure it doesn't freeze, and if it does, it reboots your computer
434	  after a certain amount of time.
435
436	  To compile this driver as a module, choose M here: the
437	  module will be called w83627hf_wdt.
438
439	  Most people will say N.
440
441config W83697HF_WDT
442	tristate "W83697HF/W83697HG Watchdog Timer"
443	depends on X86
444	---help---
445	  This is the driver for the hardware watchdog on the W83697HF/HG
446	  chipset as used in Dedibox/VIA motherboards (and likely others).
447	  This watchdog simply watches your kernel to make sure it doesn't
448	  freeze, and if it does, it reboots your computer after a certain
449	  amount of time.
450
451	  To compile this driver as a module, choose M here: the
452	  module will be called w83697hf_wdt.
453
454	  Most people will say N.
455
456config W83877F_WDT
457	tristate "W83877F (EMACS) Watchdog Timer"
458	depends on X86
459	---help---
460	  This is the driver for the hardware watchdog on the W83877F chipset
461	  as used in EMACS PC-104 motherboards (and likely others).  This
462	  watchdog simply watches your kernel to make sure it doesn't freeze,
463	  and if it does, it reboots your computer after a certain amount of
464	  time.
465
466	  To compile this driver as a module, choose M here: the
467	  module will be called w83877f_wdt.
468
469	  Most people will say N.
470
471config W83977F_WDT
472	tristate "W83977F (PCM-5335) Watchdog Timer"
473	depends on X86
474	---help---
475	  This is the driver for the hardware watchdog on the W83977F I/O chip
476	  as used in AAEON's PCM-5335 SBC (and likely others).  This
477	  watchdog simply watches your kernel to make sure it doesn't freeze,
478	  and if it does, it reboots your computer after a certain amount of
479	  time.
480
481	  To compile this driver as a module, choose M here: the
482	  module will be called w83977f_wdt.
483
484config MACHZ_WDT
485	tristate "ZF MachZ Watchdog"
486	depends on X86
487	---help---
488	  If you are using a ZF Micro MachZ processor, say Y here, otherwise
489	  N.  This is the driver for the watchdog timer built-in on that
490	  processor using ZF-Logic interface.  This watchdog simply watches
491	  your kernel to make sure it doesn't freeze, and if it does, it
492	  reboots your computer after a certain amount of time.
493
494	  To compile this driver as a module, choose M here: the
495	  module will be called machzwd.
496
497config SBC_EPX_C3_WATCHDOG
498	tristate "Winsystems SBC EPX-C3 watchdog"
499	depends on X86
500	---help---
501	  This is the driver for the built-in watchdog timer on the EPX-C3
502	  Single-board computer made by Winsystems, Inc.
503
504	  *Note*: This hardware watchdog is not probeable and thus there
505	  is no way to know if writing to its IO address will corrupt
506	  your system or have any real effect.  The only way to be sure
507	  that this driver does what you want is to make sure you
508	  are running it on an EPX-C3 from Winsystems with the watchdog
509	  timer at IO address 0x1ee and 0x1ef.  It will write to both those
510	  IO ports.  Basically, the assumption is made that if you compile
511	  this driver into your kernel and/or load it as a module, that you
512	  know what you are doing and that you are in fact running on an
513	  EPX-C3 board!
514
515	  To compile this driver as a module, choose M here: the
516	  module will be called sbc_epx_c3.
517
518# PowerPC Architecture
519
520config 8xx_WDT
521	tristate "MPC8xx Watchdog Timer"
522	depends on 8xx
523
524config 83xx_WDT
525	tristate "MPC83xx Watchdog Timer"
526	depends on PPC_83xx
527
528config MV64X60_WDT
529	tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
530	depends on MV64X60
531
532config BOOKE_WDT
533	bool "PowerPC Book-E Watchdog Timer"
534	depends on BOOKE || 4xx
535	---help---
536	  Please see Documentation/watchdog/watchdog-api.txt for
537	  more information.
538
539# PPC64 Architecture
540
541config WATCHDOG_RTAS
542	tristate "RTAS watchdog"
543	depends on PPC_RTAS
544	help
545	  This driver adds watchdog support for the RTAS watchdog.
546
547	  To compile this driver as a module, choose M here. The module
548	  will be called wdrtas.
549
550# MIPS Architecture
551
552config INDYDOG
553	tristate "Indy/I2 Hardware Watchdog"
554	depends on SGI_IP22
555	help
556	  Hardware driver for the Indy's/I2's watchdog. This is a
557	  watchdog timer that will reboot the machine after a 60 second
558	  timer expired and no process has written to /dev/watchdog during
559	  that time.
560
561config WDT_MTX1
562	tristate "MTX-1 Hardware Watchdog"
563	depends on MIPS_MTX1
564	help
565	  Hardware driver for the MTX-1 boards. This is a watchdog timer that
566	  will reboot the machine after a 100 seconds timer expired.
567
568config WDT_RM9K_GPI
569	tristate "RM9000/GPI hardware watchdog"
570	depends on CPU_RM9000
571	help
572	  Watchdog implementation using the GPI hardware found on
573	  PMC-Sierra RM9xxx CPUs.
574
575	  To compile this driver as a module, choose M here: the
576	  module will be called rm9k_wdt.
577
578# S390 Architecture
579
580config ZVM_WATCHDOG
581	tristate "z/VM Watchdog Timer"
582	depends on S390
583	help
584	  IBM s/390 and zSeries machines running under z/VM 5.1 or later
585	  provide a virtual watchdog timer to their guest that cause a
586	  user define Control Program command to be executed after a
587	  timeout.
588
589	  To compile this driver as a module, choose M here. The module
590	  will be called vmwatchdog.
591
592# SUPERH Architecture
593
594config SH_WDT
595	tristate "SuperH Watchdog"
596	depends on SUPERH
597	help
598	  This driver adds watchdog support for the integrated watchdog in the
599	  SuperH processors. If you have one of these processors and wish
600	  to have watchdog support enabled, say Y, otherwise say N.
601
602	  As a side note, saying Y here will automatically boost HZ to 1000
603	  so that the timer has a chance to clear the overflow counter. On
604	  slower systems (such as the SH-2 and SH-3) this will likely yield
605	  some performance issues. As such, the WDT should be avoided here
606	  unless it is absolutely necessary.
607
608	  To compile this driver as a module, choose M here: the
609	  module will be called shwdt.
610
611config SH_WDT_MMAP
612	bool "Allow mmap of SH WDT"
613	default n
614	depends on SH_WDT
615	help
616	  If you say Y here, user applications will be able to mmap the
617	  WDT/CPG registers.
618
619# SPARC64 Architecture
620
621config WATCHDOG_CP1XXX
622	tristate "CP1XXX Hardware Watchdog support"
623	depends on SPARC64 && PCI
624	---help---
625	  This is the driver for the hardware watchdog timers present on
626	  Sun Microsystems CompactPCI models CP1400 and CP1500.
627
628	  To compile this driver as a module, choose M here: the
629	  module will be called cpwatchdog.
630
631	  If you do not have a CompactPCI model CP1400 or CP1500, or
632	  another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
633	  you should say N to this option.
634
635config WATCHDOG_RIO
636	tristate "RIO Hardware Watchdog support"
637	depends on SPARC64 && PCI
638	help
639	  Say Y here to support the hardware watchdog capability on Sun RIO
640	  machines.  The watchdog timeout period is normally one minute but
641	  can be changed with a boot-time parameter.
642
643#
644# ISA-based Watchdog Cards
645#
646
647comment "ISA-based Watchdog Cards"
648	depends on ISA
649
650config PCWATCHDOG
651	tristate "Berkshire Products ISA-PC Watchdog"
652	depends on ISA
653	---help---
654	  This is the driver for the Berkshire Products ISA-PC Watchdog card.
655	  This card simply watches your kernel to make sure it doesn't freeze,
656	  and if it does, it reboots your computer after a certain amount of
657	  time. This driver is like the WDT501 driver but for different
658	  hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
659	  watchdog cards can be ordered from <http://www.berkprod.com/>.
660
661	  To compile this driver as a module, choose M here: the
662	  module will be called pcwd.
663
664	  Most people will say N.
665
666config MIXCOMWD
667	tristate "Mixcom Watchdog"
668	depends on ISA
669	---help---
670	  This is a driver for the Mixcom hardware watchdog cards.  This
671	  watchdog simply watches your kernel to make sure it doesn't freeze,
672	  and if it does, it reboots your computer after a certain amount of
673	  time.
674
675	  To compile this driver as a module, choose M here: the
676	  module will be called mixcomwd.
677
678	  Most people will say N.
679
680config WDT
681	tristate "WDT Watchdog timer"
682	depends on ISA
683	---help---
684	  If you have a WDT500P or WDT501P watchdog board, say Y here,
685	  otherwise N. It is not possible to probe for this board, which means
686	  that you have to inform the kernel about the IO port and IRQ that
687	  is needed (you can do this via the io and irq parameters)
688
689	  To compile this driver as a module, choose M here: the
690	  module will be called wdt.
691
692config WDT_501
693	bool "WDT501 features"
694	depends on WDT
695	help
696	  Saying Y here and creating a character special file /dev/temperature
697	  with major number 10 and minor number 131 ("man mknod") will give
698	  you a thermometer inside your computer: reading from
699	  /dev/temperature yields one byte, the temperature in degrees
700	  Fahrenheit. This works only if you have a WDT501P watchdog board
701	  installed.
702
703	  If you want to enable the Fan Tachometer on the WDT501P, then you
704	  can do this via the tachometer parameter. Only do this if you have a
705	  fan tachometer actually set up.
706
707#
708# PCI-based Watchdog Cards
709#
710
711comment "PCI-based Watchdog Cards"
712	depends on PCI
713
714config PCIPCWATCHDOG
715	tristate "Berkshire Products PCI-PC Watchdog"
716	depends on PCI
717	---help---
718	  This is the driver for the Berkshire Products PCI-PC Watchdog card.
719	  This card simply watches your kernel to make sure it doesn't freeze,
720	  and if it does, it reboots your computer after a certain amount of
721	  time. The card can also monitor the internal temperature of the PC.
722	  More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
723
724	  To compile this driver as a module, choose M here: the
725	  module will be called pcwd_pci.
726
727	  Most people will say N.
728
729config WDTPCI
730	tristate "PCI-WDT500/501 Watchdog timer"
731	depends on PCI
732	---help---
733	  If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
734
735	  To compile this driver as a module, choose M here: the
736	  module will be called wdt_pci.
737
738config WDT_501_PCI
739	bool "PCI-WDT501 features"
740	depends on WDTPCI
741	help
742	  Saying Y here and creating a character special file /dev/temperature
743	  with major number 10 and minor number 131 ("man mknod") will give
744	  you a thermometer inside your computer: reading from
745	  /dev/temperature yields one byte, the temperature in degrees
746	  Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
747	  installed.
748
749	  If you want to enable the Fan Tachometer on the PCI-WDT501, then you
750	  can do this via the tachometer parameter. Only do this if you have a
751	  fan tachometer actually set up.
752
753#
754# USB-based Watchdog Cards
755#
756
757comment "USB-based Watchdog Cards"
758	depends on USB
759
760config USBPCWATCHDOG
761	tristate "Berkshire Products USB-PC Watchdog"
762	depends on USB
763	---help---
764	  This is the driver for the Berkshire Products USB-PC Watchdog card.
765	  This card simply watches your kernel to make sure it doesn't freeze,
766	  and if it does, it reboots your computer after a certain amount of
767	  time. The card can also monitor the internal temperature of the PC.
768	  More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
769
770	  To compile this driver as a module, choose M here: the
771	  module will be called pcwd_usb.
772
773	  Most people will say N.
774
775endif # WATCHDOG
776