2 # Watchdog device configuration
6 bool "Watchdog Timer Support"
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
19 <file:Documentation/watchdog/watchdog-api.txt> in the kernel source.
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
31 config WATCHDOG_NOWAYOUT
32 bool "Disable watchdog shutdown on close"
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
41 # General Watchdog drivers
44 comment "Watchdog Device Drivers"
46 # Architecture Independent
49 tristate "Software watchdog"
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.
55 To compile this driver as a module, choose M here: the
56 module will be called softdog.
62 config AT91RM9200_WATCHDOG
63 tristate "AT91RM9200 watchdog"
64 depends on ARCH_AT91RM9200
66 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
67 system when the timeout is reached.
70 tristate "DC21285 watchdog"
73 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
74 here if you wish to use this. Alternatively say M to compile the
75 driver as a module, which will be called wdt285.
77 This driver does not work on all machines. In particular, early CATS
78 boards have hardware problems that will cause the machine to simply
79 lock up if the watchdog fires.
81 "If in doubt, leave it out" - say N.
84 tristate "NetWinder WB83C977 watchdog"
85 depends on FOOTBRIDGE && ARCH_NETWINDER
87 Say Y here to include support for the WB977 watchdog included in
88 NetWinder machines. Alternatively say M to compile the driver as
89 a module, which will be called wdt977.
91 Not sure? It's safe to say N.
93 config IXP2000_WATCHDOG
94 tristate "IXP2000 Watchdog"
95 depends on ARCH_IXP2000
97 Say Y here if to include support for the watchdog timer
98 in the Intel IXP2000(2400, 2800, 2850) network processors.
99 This driver can be built as a module by choosing M. The module
100 will be called ixp2000_wdt.
102 Say N if you are unsure.
104 config IXP4XX_WATCHDOG
105 tristate "IXP4xx Watchdog"
106 depends on ARCH_IXP4XX
108 Say Y here if to include support for the watchdog timer
109 in the Intel IXP4xx network processors. This driver can
110 be built as a module by choosing M. The module will
111 be called ixp4xx_wdt.
113 Note: The internal IXP4xx watchdog does a soft CPU reset
114 which doesn't reset any peripherals. There are circumstances
115 where the watchdog will fail to reset the board correctly
116 (e.g., if the boot ROM is in an unreadable state).
118 Say N if you are unsure.
120 config KS8695_WATCHDOG
121 tristate "KS8695 watchdog"
122 depends on ARCH_KS8695
124 Watchdog timer embedded into KS8695 processor. This will reboot your
125 system when the timeout is reached.
127 config S3C2410_WATCHDOG
128 tristate "S3C2410 Watchdog"
129 depends on ARCH_S3C2410
131 Watchdog timer block in the Samsung S3C2410 chips. This will
132 reboot the system when the timer expires with the watchdog
135 The driver is limited by the speed of the system's PCLK
136 signal, so with reasonably fast systems (PCLK around 50-66MHz)
137 then watchdog intervals of over approximately 20seconds are
140 The driver can be built as a module by choosing M, and will
141 be called s3c2410_wdt
143 config SA1100_WATCHDOG
144 tristate "SA1100/PXA2xx watchdog"
145 depends on ARCH_SA1100 || ARCH_PXA
147 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
148 reboot your system when timeout is reached.
150 NOTE: once enabled, this timer cannot be disabled.
152 To compile this driver as a module, choose M here: the
153 module will be called sa1100_wdt.
155 config MPCORE_WATCHDOG
156 tristate "MPcore watchdog"
157 depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
159 Watchdog timer embedded into the MPcore system.
161 To compile this driver as a module, choose M here: the
162 module will be called mpcore_wdt.
164 config EP93XX_WATCHDOG
165 tristate "EP93xx Watchdog"
166 depends on ARCH_EP93XX
168 Say Y here if to include support for the watchdog timer
169 embedded in the Cirrus Logic EP93xx family of devices.
171 To compile this driver as a module, choose M here: the
172 module will be called ep93xx_wdt.
175 tristate "OMAP Watchdog"
176 depends on ARCH_OMAP16XX || ARCH_OMAP24XX
178 Support for TI OMAP1610/OMAP1710/OMAP2420 watchdog. Say 'Y' here to
179 enable the OMAP1610/OMAP1710 watchdog timer.
181 config PNX4008_WATCHDOG
182 tristate "PNX4008 Watchdog"
183 depends on ARCH_PNX4008
185 Say Y here if to include support for the watchdog timer
186 in the PNX4008 processor.
187 This driver can be built as a module by choosing M. The module
188 will be called pnx4008_wdt.
190 Say N if you are unsure.
193 tristate "IOP Watchdog"
195 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
197 Say Y here if to include support for the watchdog timer
198 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
199 be built as a module by choosing M. The module will
202 Note: The IOP13XX watchdog does an Internal Bus Reset which will
203 affect both cores and the peripherals of the IOP. The ATU-X
204 and/or ATUe configuration registers will remain intact, but if
205 operating as an Root Complex and/or Central Resource, the PCI-X
206 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
208 config DAVINCI_WATCHDOG
209 tristate "DaVinci watchdog"
210 depends on ARCH_DAVINCI
212 Say Y here if to include support for the watchdog timer
213 in the DaVinci DM644x/DM646x processors.
214 To compile this driver as a module, choose M here: the
215 module will be called davinci_wdt.
217 NOTE: once enabled, this timer cannot be disabled.
218 Say N if you are unsure.
224 config AT32AP700X_WDT
225 tristate "AT32AP700x watchdog"
226 depends on CPU_AT32AP700X
228 Watchdog timer embedded into AT32AP700x devices. This will reboot
229 your system when the timeout is reached.
231 # BLACKFIN Architecture
234 tristate "Blackfin On-Chip Watchdog Timer"
237 If you say yes here you will get support for the Blackfin On-Chip
238 Watchdog Timer. If you have one of these processors and wish to
239 have watchdog support enabled, say Y, otherwise say N.
241 To compile this driver as a module, choose M here: the
242 module will be called bfin_wdt.
250 # X86 (i386 + ia64 + x86_64) Architecture
253 tristate "Acquire SBC Watchdog Timer"
256 This is the driver for the hardware watchdog on Single Board
257 Computers produced by Acquire Inc (and others). This watchdog
258 simply watches your kernel to make sure it doesn't freeze, and if
259 it does, it reboots your computer after a certain amount of time.
261 To compile this driver as a module, choose M here: the
262 module will be called acquirewdt.
264 Most people will say N.
267 tristate "Advantech SBC Watchdog Timer"
270 If you are configuring a Linux kernel for the Advantech single-board
271 computer, say `Y' here to support its built-in watchdog timer
272 feature. More information can be found at
273 <http://www.advantech.com.tw/products/>
276 tristate "ALi M1535 PMU Watchdog Timer"
277 depends on X86 && PCI
279 This is the driver for the hardware watchdog on the ALi M1535 PMU.
281 To compile this driver as a module, choose M here: the
282 module will be called alim1535_wdt.
284 Most people will say N.
287 tristate "ALi M7101 PMU Computer Watchdog"
290 This is the driver for the hardware watchdog on the ALi M7101 PMU
291 as used in the x86 Cobalt servers and also found in some
292 SPARC Netra servers too.
294 To compile this driver as a module, choose M here: the
295 module will be called alim7101_wdt.
297 Most people will say N.
300 tristate "AMD Geode CS5535/CS5536 Watchdog"
303 This driver enables a watchdog capability built into the
304 CS5535/CS5536 companion chips for the AMD Geode GX and LX
305 processors. This watchdog watches your kernel to make sure
306 it doesn't freeze, and if it does, it reboots your computer after
307 a certain amount of time.
309 You can compile this driver directly into the kernel, or use
310 it as a module. The module will be called geodewdt.
313 tristate "AMD Elan SC520 processor Watchdog"
316 This is the driver for the hardware watchdog built in to the
317 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
318 This watchdog simply watches your kernel to make sure it doesn't
319 freeze, and if it does, it reboots your computer after a certain
322 You can compile this driver directly into the kernel, or use
323 it as a module. The module will be called sc520_wdt.
326 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
329 Enable support for the watchdog timer on the Eurotech CPU-1220 and
330 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
331 information are at <http://www.eurotech.it/>.
334 tristate "IB700 SBC Watchdog Timer"
337 This is the driver for the hardware watchdog on the IB700 Single
338 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
339 simply watches your kernel to make sure it doesn't freeze, and if
340 it does, it reboots your computer after a certain amount of time.
342 This driver is like the WDT501 driver but for slightly different hardware.
344 To compile this driver as a module, choose M here: the
345 module will be called ib700wdt.
347 Most people will say N.
350 tristate "IBM Automatic Server Restart"
353 This is the driver for the IBM Automatic Server Restart watchdog
354 timer built-in into some eServer xSeries machines.
356 To compile this driver as a module, choose M here: the
357 module will be called ibmasr.
360 tristate "ICP Single Board Computer Watchdog Timer"
363 This is a driver for the hardware watchdog on the ICP Single
364 Board Computer. This driver is working on (at least) the following
365 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
367 To compile this driver as a module, choose M here: the
368 module will be called wafer5823wdt.
371 tristate "Intel 6300ESB Timer/Watchdog"
372 depends on X86 && PCI
374 Hardware driver for the watchdog timer built into the Intel
375 6300ESB controller hub.
377 To compile this driver as a module, choose M here: the
378 module will be called i6300esb.
381 tristate "Intel TCO Timer/Watchdog"
382 depends on (X86 || IA64) && PCI
384 Hardware driver for the intel TCO timer based watchdog devices.
385 These drivers are included in the Intel 82801 I/O Controller
386 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
389 The TCO (Total Cost of Ownership) timer is a watchdog timer
390 that will reboot the machine after its second expiration. The
391 expiration time can be configured with the "heartbeat" parameter.
393 On some motherboards the driver may fail to reset the chipset's
394 NO_REBOOT flag which prevents the watchdog from rebooting the
395 machine. If this is the case you will get a kernel message like
396 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
398 To compile this driver as a module, choose M here: the
399 module will be called iTCO_wdt.
401 config ITCO_VENDOR_SUPPORT
402 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
405 Add vendor specific support to the intel TCO timer based watchdog
406 devices. At this moment we only have additional support for some
407 SuperMicro Inc. motherboards.
410 tristate "IT8712F (Smart Guardian) Watchdog Timer"
413 This is the driver for the built-in watchdog timer on the IT8712F
414 Super I/0 chipset used on many motherboards.
416 To compile this driver as a module, choose M here: the
417 module will be called it8712f_wdt.
420 tristate "IT87 Watchdog Timer"
421 depends on X86 && EXPERIMENTAL
423 This is the driver for the hardware watchdog on the ITE IT8716,
424 IT8718, IT8726, IT8712(Version J,K) Super I/O chips. This watchdog
425 simply watches your kernel to make sure it doesn't freeze, and if
426 it does, it reboots your computer after a certain amount of time.
428 To compile this driver as a module, choose M here: the module will
432 tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
435 A software monitoring watchdog and NMI sourcing driver. This driver
436 will detect lockups and provide stack trace. Also, when an NMI
437 occurs this driver will make the necessary BIOS calls to log
438 the cause of the NMI. This is a driver that will only load on a
439 HP ProLiant system with a minimum of iLO2 support.
440 To compile this driver as a module, choose M here: the
441 module will be called hpwdt.
444 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
447 This is a driver for National Semiconductor PC87307/PC97307 hardware
448 watchdog cards as found on the SC1200. This watchdog is mainly used
449 for power management purposes and can be used to power down the device
450 during inactivity periods (includes interrupt activity monitoring).
452 To compile this driver as a module, choose M here: the
453 module will be called sc1200wdt.
455 Most people will say N.
458 tristate "National Semiconductor SCx200 Watchdog"
459 depends on SCx200 && PCI
461 Enable the built-in watchdog timer support on the National
462 Semiconductor SCx200 processors.
464 If compiled as a module, it will be called scx200_wdt.
467 tristate "NS PC87413 watchdog"
470 This is the driver for the hardware watchdog on the PC87413 chipset
471 This watchdog simply watches your kernel to make sure it doesn't
472 freeze, and if it does, it reboots your computer after a certain
475 To compile this driver as a module, choose M here: the
476 module will be called pc87413_wdt.
478 Most people will say N.
481 tristate "RDC R-321x SoC watchdog"
482 depends on X86_RDC321X
484 This is the driver for the built in hardware watchdog
485 in the RDC R-321x SoC.
487 To compile this driver as a module, choose M here: the
488 module will be called rdc321x_wdt.
491 tristate "SBC-60XX Watchdog Timer"
494 This driver can be used with the watchdog timer found on some
495 single board computers, namely the 6010 PII based computer.
496 It may well work with other cards. It reads port 0x443 to enable
497 and re-set the watchdog timer, and reads port 0x45 to disable
498 the watchdog. If you have a card that behave in similar ways,
499 you can probably make this driver work with your card as well.
501 You can compile this driver directly into the kernel, or use
502 it as a module. The module will be called sbc60xxwdt.
505 tristate "SBC8360 Watchdog Timer"
509 This is the driver for the hardware watchdog on the SBC8360 Single
510 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
512 To compile this driver as a module, choose M here: the
513 module will be called sbc8360.ko.
515 Most people will say N.
518 tristate "SBC Nano 7240 Watchdog Timer"
521 This is the driver for the hardware watchdog found on the IEI
522 single board computers EPIC Nano 7240 (and likely others). This
523 watchdog simply watches your kernel to make sure it doesn't freeze,
524 and if it does, it reboots your computer after a certain amount of
527 To compile this driver as a module, choose M here: the
528 module will be called sbc7240_wdt.
531 tristate "SMA CPU5 Watchdog"
535 To compile this driver as a module, choose M here: the
536 module will be called cpu5wdt.
538 config SMSC37B787_WDT
539 tristate "Winbond SMsC37B787 Watchdog Timer"
542 This is the driver for the hardware watchdog component on the
543 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
544 from Vision Systems and maybe others.
546 This watchdog simply watches your kernel to make sure it doesn't
547 freeze, and if it does, it reboots your computer after a certain
550 Usually a userspace daemon will notify the kernel WDT driver that
551 userspace is still alive, at regular intervals.
553 To compile this driver as a module, choose M here: the
554 module will be called smsc37b787_wdt.
556 Most people will say N.
559 tristate "W83627HF Watchdog Timer"
562 This is the driver for the hardware watchdog on the W83627HF chipset
563 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
564 (and likely others). This watchdog simply watches your kernel to
565 make sure it doesn't freeze, and if it does, it reboots your computer
566 after a certain amount of time.
568 To compile this driver as a module, choose M here: the
569 module will be called w83627hf_wdt.
571 Most people will say N.
574 tristate "W83697HF/W83697HG Watchdog Timer"
577 This is the driver for the hardware watchdog on the W83697HF/HG
578 chipset as used in Dedibox/VIA motherboards (and likely others).
579 This watchdog simply watches your kernel to make sure it doesn't
580 freeze, and if it does, it reboots your computer after a certain
583 To compile this driver as a module, choose M here: the
584 module will be called w83697hf_wdt.
586 Most people will say N.
589 tristate "W83877F (EMACS) Watchdog Timer"
592 This is the driver for the hardware watchdog on the W83877F chipset
593 as used in EMACS PC-104 motherboards (and likely others). This
594 watchdog 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
598 To compile this driver as a module, choose M here: the
599 module will be called w83877f_wdt.
601 Most people will say N.
604 tristate "W83977F (PCM-5335) Watchdog Timer"
607 This is the driver for the hardware watchdog on the W83977F I/O chip
608 as used in AAEON's PCM-5335 SBC (and likely others). This
609 watchdog simply watches your kernel to make sure it doesn't freeze,
610 and if it does, it reboots your computer after a certain amount of
613 To compile this driver as a module, choose M here: the
614 module will be called w83977f_wdt.
617 tristate "ZF MachZ Watchdog"
620 If you are using a ZF Micro MachZ processor, say Y here, otherwise
621 N. This is the driver for the watchdog timer built-in on that
622 processor using ZF-Logic interface. This watchdog simply watches
623 your kernel to make sure it doesn't freeze, and if it does, it
624 reboots your computer after a certain amount of time.
626 To compile this driver as a module, choose M here: the
627 module will be called machzwd.
629 config SBC_EPX_C3_WATCHDOG
630 tristate "Winsystems SBC EPX-C3 watchdog"
633 This is the driver for the built-in watchdog timer on the EPX-C3
634 Single-board computer made by Winsystems, Inc.
636 *Note*: This hardware watchdog is not probeable and thus there
637 is no way to know if writing to its IO address will corrupt
638 your system or have any real effect. The only way to be sure
639 that this driver does what you want is to make sure you
640 are running it on an EPX-C3 from Winsystems with the watchdog
641 timer at IO address 0x1ee and 0x1ef. It will write to both those
642 IO ports. Basically, the assumption is made that if you compile
643 this driver into your kernel and/or load it as a module, that you
644 know what you are doing and that you are in fact running on an
647 To compile this driver as a module, choose M here: the
648 module will be called sbc_epx_c3.
654 # M68KNOMMU Architecture
659 tristate "IDT RC32434 SoC Watchdog Timer"
660 depends on MIKROTIK_RB532
662 Hardware driver for the IDT RC32434 SoC built-in
665 To compile this driver as a module, choose M here: the
666 module will be called rc32434_wdt.
669 tristate "Indy/I2 Hardware Watchdog"
670 depends on SGI_HAS_INDYDOG
672 Hardware driver for the Indy's/I2's watchdog. This is a
673 watchdog timer that will reboot the machine after a 60 second
674 timer expired and no process has written to /dev/watchdog during
678 tristate "MTX-1 Hardware Watchdog"
681 Hardware driver for the MTX-1 boards. This is a watchdog timer that
682 will reboot the machine after a 100 seconds timer expired.
685 tristate "RM9000/GPI hardware watchdog"
686 depends on CPU_RM9000
688 Watchdog implementation using the GPI hardware found on
689 PMC-Sierra RM9xxx CPUs.
691 To compile this driver as a module, choose M here: the
692 module will be called rm9k_wdt.
695 tristate "Sibyte SoC hardware watchdog"
698 Watchdog driver for the built in watchdog hardware in Sibyte
699 SoC processors. There are apparently two watchdog timers
700 on such processors; this driver supports only the first one,
701 because currently Linux only supports exporting one watchdog
704 To compile this driver as a loadable module, choose M here.
705 The module will be called sb_wdog.
708 tristate "TI AR7 Watchdog Timer"
711 Hardware driver for the TI AR7 Watchdog Timer.
714 tristate "Toshiba TXx9 Watchdog Timer"
715 depends on CPU_TX39XX || CPU_TX49XX
717 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
719 # PARISC Architecture
721 # POWERPC Architecture
724 tristate "MPC5200 Watchdog Timer"
725 depends on PPC_MPC52xx
728 tristate "MPC8xxx Platform Watchdog Timer"
729 depends on PPC_8xx || PPC_83xx || PPC_86xx
731 This driver is for a SoC level watchdog that exists on some
732 Freescale PowerPC processors. So far this driver supports:
737 For BookE processors (MPC85xx) use the BOOKE_WDT driver instead.
740 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
744 bool "PowerPC Book-E Watchdog Timer"
745 depends on BOOKE || 4xx
747 Please see Documentation/watchdog/watchdog-api.txt for
753 tristate "RTAS watchdog"
756 This driver adds watchdog support for the RTAS watchdog.
758 To compile this driver as a module, choose M here. The module
759 will be called wdrtas.
764 tristate "z/VM Watchdog Timer"
767 IBM s/390 and zSeries machines running under z/VM 5.1 or later
768 provide a virtual watchdog timer to their guest that cause a
769 user define Control Program command to be executed after a
772 To compile this driver as a module, choose M here. The module
773 will be called vmwatchdog.
775 # SUPERH (sh + sh64) Architecture
778 tristate "SuperH Watchdog"
779 depends on SUPERH && (CPU_SH3 || CPU_SH4)
781 This driver adds watchdog support for the integrated watchdog in the
782 SuperH processors. If you have one of these processors and wish
783 to have watchdog support enabled, say Y, otherwise say N.
785 As a side note, saying Y here will automatically boost HZ to 1000
786 so that the timer has a chance to clear the overflow counter. On
787 slower systems (such as the SH-2 and SH-3) this will likely yield
788 some performance issues. As such, the WDT should be avoided here
789 unless it is absolutely necessary.
791 To compile this driver as a module, choose M here: the
792 module will be called shwdt.
795 bool "Allow mmap of SH WDT"
799 If you say Y here, user applications will be able to mmap the
804 # SPARC64 Architecture
806 config WATCHDOG_CP1XXX
807 tristate "CP1XXX Hardware Watchdog support"
808 depends on SPARC64 && PCI
810 This is the driver for the hardware watchdog timers present on
811 Sun Microsystems CompactPCI models CP1400 and CP1500.
813 To compile this driver as a module, choose M here: the
814 module will be called cpwatchdog.
816 If you do not have a CompactPCI model CP1400 or CP1500, or
817 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
818 you should say N to this option.
821 tristate "RIO Hardware Watchdog support"
822 depends on SPARC64 && PCI
824 Say Y here to support the hardware watchdog capability on Sun RIO
825 machines. The watchdog timeout period is normally one minute but
826 can be changed with a boot-time parameter.
828 # XTENSA Architecture
831 # ISA-based Watchdog Cards
834 comment "ISA-based Watchdog Cards"
838 tristate "Berkshire Products ISA-PC Watchdog"
841 This is the driver for the Berkshire Products ISA-PC Watchdog card.
842 This card simply watches your kernel to make sure it doesn't freeze,
843 and if it does, it reboots your computer after a certain amount of
844 time. This driver is like the WDT501 driver but for different
845 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
846 watchdog cards can be ordered from <http://www.berkprod.com/>.
848 To compile this driver as a module, choose M here: the
849 module will be called pcwd.
851 Most people will say N.
854 tristate "Mixcom Watchdog"
857 This is a driver for the Mixcom hardware watchdog cards. This
858 watchdog simply watches your kernel to make sure it doesn't freeze,
859 and if it does, it reboots your computer after a certain amount of
862 To compile this driver as a module, choose M here: the
863 module will be called mixcomwd.
865 Most people will say N.
868 tristate "WDT Watchdog timer"
871 If you have a WDT500P or WDT501P watchdog board, say Y here,
872 otherwise N. It is not possible to probe for this board, which means
873 that you have to inform the kernel about the IO port and IRQ that
874 is needed (you can do this via the io and irq parameters)
876 To compile this driver as a module, choose M here: the
877 module will be called wdt.
880 bool "WDT501 features"
883 Saying Y here and creating a character special file /dev/temperature
884 with major number 10 and minor number 131 ("man mknod") will give
885 you a thermometer inside your computer: reading from
886 /dev/temperature yields one byte, the temperature in degrees
887 Fahrenheit. This works only if you have a WDT501P watchdog board
890 If you want to enable the Fan Tachometer on the WDT501P, then you
891 can do this via the tachometer parameter. Only do this if you have a
892 fan tachometer actually set up.
895 # PCI-based Watchdog Cards
898 comment "PCI-based Watchdog Cards"
902 tristate "Berkshire Products PCI-PC Watchdog"
905 This is the driver for the Berkshire Products PCI-PC Watchdog card.
906 This card simply watches your kernel to make sure it doesn't freeze,
907 and if it does, it reboots your computer after a certain amount of
908 time. The card can also monitor the internal temperature of the PC.
909 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
911 To compile this driver as a module, choose M here: the
912 module will be called pcwd_pci.
914 Most people will say N.
917 tristate "PCI-WDT500/501 Watchdog timer"
920 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
922 To compile this driver as a module, choose M here: the
923 module will be called wdt_pci.
926 bool "PCI-WDT501 features"
929 Saying Y here and creating a character special file /dev/temperature
930 with major number 10 and minor number 131 ("man mknod") will give
931 you a thermometer inside your computer: reading from
932 /dev/temperature yields one byte, the temperature in degrees
933 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
936 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
937 can do this via the tachometer parameter. Only do this if you have a
938 fan tachometer actually set up.
941 # USB-based Watchdog Cards
944 comment "USB-based Watchdog Cards"
948 tristate "Berkshire Products USB-PC Watchdog"
951 This is the driver for the Berkshire Products USB-PC Watchdog card.
952 This card simply watches your kernel to make sure it doesn't freeze,
953 and if it does, it reboots your computer after a certain amount of
954 time. The card can also monitor the internal temperature of the PC.
955 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
957 To compile this driver as a module, choose M here: the
958 module will be called pcwd_usb.
960 Most people will say N.