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"
288 depends on X86 && PCI
290 This is the driver for the hardware watchdog on the ALi M7101 PMU
291 as used in the x86 Cobalt servers.
293 To compile this driver as a module, choose M here: the
294 module will be called alim7101_wdt.
296 Most people will say N.
299 tristate "AMD Elan SC520 processor Watchdog"
302 This is the driver for the hardware watchdog built in to the
303 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
304 This watchdog simply watches your kernel to make sure it doesn't
305 freeze, and if it does, it reboots your computer after a certain
308 You can compile this driver directly into the kernel, or use
309 it as a module. The module will be called sc520_wdt.
312 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
315 Enable support for the watchdog timer on the Eurotech CPU-1220 and
316 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
317 information are at <http://www.eurotech.it/>.
320 tristate "IB700 SBC Watchdog Timer"
323 This is the driver for the hardware watchdog on the IB700 Single
324 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
325 simply watches your kernel to make sure it doesn't freeze, and if
326 it does, it reboots your computer after a certain amount of time.
328 This driver is like the WDT501 driver but for slightly different hardware.
330 To compile this driver as a module, choose M here: the
331 module will be called ib700wdt.
333 Most people will say N.
336 tristate "IBM Automatic Server Restart"
339 This is the driver for the IBM Automatic Server Restart watchdog
340 timer built-in into some eServer xSeries machines.
342 To compile this driver as a module, choose M here: the
343 module will be called ibmasr.
346 tristate "ICP Single Board Computer Watchdog Timer"
349 This is a driver for the hardware watchdog on the ICP Single
350 Board Computer. This driver is working on (at least) the following
351 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
353 To compile this driver as a module, choose M here: the
354 module will be called wafer5823wdt.
357 tristate "Intel 6300ESB Timer/Watchdog"
358 depends on X86 && PCI
360 Hardware driver for the watchdog timer built into the Intel
361 6300ESB controller hub.
363 To compile this driver as a module, choose M here: the
364 module will be called i6300esb.
367 tristate "Intel TCO Timer/Watchdog"
368 depends on (X86 || IA64) && PCI
370 Hardware driver for the intel TCO timer based watchdog devices.
371 These drivers are included in the Intel 82801 I/O Controller
372 Hub family (from ICH0 up to ICH8) and in the Intel 6300ESB
375 The TCO (Total Cost of Ownership) timer is a watchdog timer
376 that will reboot the machine after its second expiration. The
377 expiration time can be configured with the "heartbeat" parameter.
379 On some motherboards the driver may fail to reset the chipset's
380 NO_REBOOT flag which prevents the watchdog from rebooting the
381 machine. If this is the case you will get a kernel message like
382 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
384 To compile this driver as a module, choose M here: the
385 module will be called iTCO_wdt.
387 config ITCO_VENDOR_SUPPORT
388 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
391 Add vendor specific support to the intel TCO timer based watchdog
392 devices. At this moment we only have additional support for some
393 SuperMicro Inc. motherboards.
396 tristate "IT8712F (Smart Guardian) Watchdog Timer"
399 This is the driver for the built-in watchdog timer on the IT8712F
400 Super I/0 chipset used on many motherboards.
402 To compile this driver as a module, choose M here: the
403 module will be called it8712f_wdt.
406 tristate "HP Proliant iLO 2 Hardware Watchdog Timer"
409 A software monitoring watchdog and NMI sourcing driver. This driver
410 will detect lockups and provide stack trace. Also, when an NMI
411 occurs this driver will make the necessary BIOS calls to log
412 the cause of the NMI. This is a driver that will only load on a
413 HP ProLiant system with a minimum of iLO2 support.
414 To compile this driver as a module, choose M here: the
415 module will be called hpwdt.
418 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
421 This is a driver for National Semiconductor PC87307/PC97307 hardware
422 watchdog cards as found on the SC1200. This watchdog is mainly used
423 for power management purposes and can be used to power down the device
424 during inactivity periods (includes interrupt activity monitoring).
426 To compile this driver as a module, choose M here: the
427 module will be called sc1200wdt.
429 Most people will say N.
432 tristate "National Semiconductor SCx200 Watchdog"
433 depends on SCx200 && PCI
435 Enable the built-in watchdog timer support on the National
436 Semiconductor SCx200 processors.
438 If compiled as a module, it will be called scx200_wdt.
441 tristate "NS PC87413 watchdog"
444 This is the driver for the hardware watchdog on the PC87413 chipset
445 This watchdog simply watches your kernel to make sure it doesn't
446 freeze, and if it does, it reboots your computer after a certain
449 To compile this driver as a module, choose M here: the
450 module will be called pc87413_wdt.
452 Most people will say N.
455 tristate "SBC-60XX Watchdog Timer"
458 This driver can be used with the watchdog timer found on some
459 single board computers, namely the 6010 PII based computer.
460 It may well work with other cards. It reads port 0x443 to enable
461 and re-set the watchdog timer, and reads port 0x45 to disable
462 the watchdog. If you have a card that behave in similar ways,
463 you can probably make this driver work with your card as well.
465 You can compile this driver directly into the kernel, or use
466 it as a module. The module will be called sbc60xxwdt.
469 tristate "SBC8360 Watchdog Timer"
473 This is the driver for the hardware watchdog on the SBC8360 Single
474 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
476 To compile this driver as a module, choose M here: the
477 module will be called sbc8360.ko.
479 Most people will say N.
482 tristate "SBC Nano 7240 Watchdog Timer"
485 This is the driver for the hardware watchdog found on the IEI
486 single board computers EPIC Nano 7240 (and likely others). This
487 watchdog simply watches your kernel to make sure it doesn't freeze,
488 and if it does, it reboots your computer after a certain amount of
491 To compile this driver as a module, choose M here: the
492 module will be called sbc7240_wdt.
495 tristate "SMA CPU5 Watchdog"
499 To compile this driver as a module, choose M here: the
500 module will be called cpu5wdt.
502 config SMSC37B787_WDT
503 tristate "Winbond SMsC37B787 Watchdog Timer"
506 This is the driver for the hardware watchdog component on the
507 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
508 from Vision Systems and maybe others.
510 This watchdog simply watches your kernel to make sure it doesn't
511 freeze, and if it does, it reboots your computer after a certain
514 Usually a userspace daemon will notify the kernel WDT driver that
515 userspace is still alive, at regular intervals.
517 To compile this driver as a module, choose M here: the
518 module will be called smsc37b787_wdt.
520 Most people will say N.
523 tristate "W83627HF Watchdog Timer"
526 This is the driver for the hardware watchdog on the W83627HF chipset
527 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
528 (and likely others). This watchdog simply watches your kernel to
529 make sure it doesn't freeze, and if it does, it reboots your computer
530 after a certain amount of time.
532 To compile this driver as a module, choose M here: the
533 module will be called w83627hf_wdt.
535 Most people will say N.
538 tristate "W83697HF/W83697HG Watchdog Timer"
541 This is the driver for the hardware watchdog on the W83697HF/HG
542 chipset as used in Dedibox/VIA motherboards (and likely others).
543 This watchdog simply watches your kernel to make sure it doesn't
544 freeze, and if it does, it reboots your computer after a certain
547 To compile this driver as a module, choose M here: the
548 module will be called w83697hf_wdt.
550 Most people will say N.
553 tristate "W83877F (EMACS) Watchdog Timer"
556 This is the driver for the hardware watchdog on the W83877F chipset
557 as used in EMACS PC-104 motherboards (and likely others). This
558 watchdog simply watches your kernel to make sure it doesn't freeze,
559 and if it does, it reboots your computer after a certain amount of
562 To compile this driver as a module, choose M here: the
563 module will be called w83877f_wdt.
565 Most people will say N.
568 tristate "W83977F (PCM-5335) Watchdog Timer"
571 This is the driver for the hardware watchdog on the W83977F I/O chip
572 as used in AAEON's PCM-5335 SBC (and likely others). This
573 watchdog simply watches your kernel to make sure it doesn't freeze,
574 and if it does, it reboots your computer after a certain amount of
577 To compile this driver as a module, choose M here: the
578 module will be called w83977f_wdt.
581 tristate "ZF MachZ Watchdog"
584 If you are using a ZF Micro MachZ processor, say Y here, otherwise
585 N. This is the driver for the watchdog timer built-in on that
586 processor using ZF-Logic interface. This watchdog simply watches
587 your kernel to make sure it doesn't freeze, and if it does, it
588 reboots your computer after a certain amount of time.
590 To compile this driver as a module, choose M here: the
591 module will be called machzwd.
593 config SBC_EPX_C3_WATCHDOG
594 tristate "Winsystems SBC EPX-C3 watchdog"
597 This is the driver for the built-in watchdog timer on the EPX-C3
598 Single-board computer made by Winsystems, Inc.
600 *Note*: This hardware watchdog is not probeable and thus there
601 is no way to know if writing to its IO address will corrupt
602 your system or have any real effect. The only way to be sure
603 that this driver does what you want is to make sure you
604 are running it on an EPX-C3 from Winsystems with the watchdog
605 timer at IO address 0x1ee and 0x1ef. It will write to both those
606 IO ports. Basically, the assumption is made that if you compile
607 this driver into your kernel and/or load it as a module, that you
608 know what you are doing and that you are in fact running on an
611 To compile this driver as a module, choose M here: the
612 module will be called sbc_epx_c3.
618 # M68KNOMMU Architecture
623 tristate "Indy/I2 Hardware Watchdog"
624 depends on SGI_HAS_INDYDOG
626 Hardware driver for the Indy's/I2's watchdog. This is a
627 watchdog timer that will reboot the machine after a 60 second
628 timer expired and no process has written to /dev/watchdog during
632 tristate "MTX-1 Hardware Watchdog"
635 Hardware driver for the MTX-1 boards. This is a watchdog timer that
636 will reboot the machine after a 100 seconds timer expired.
639 tristate "RM9000/GPI hardware watchdog"
640 depends on CPU_RM9000
642 Watchdog implementation using the GPI hardware found on
643 PMC-Sierra RM9xxx CPUs.
645 To compile this driver as a module, choose M here: the
646 module will be called rm9k_wdt.
649 tristate "Sibyte SoC hardware watchdog"
652 Watchdog driver for the built in watchdog hardware in Sibyte
653 SoC processors. There are apparently two watchdog timers
654 on such processors; this driver supports only the first one,
655 because currently Linux only supports exporting one watchdog
658 To compile this driver as a loadable module, choose M here.
659 The module will be called sb_wdog.
662 tristate "TI AR7 Watchdog Timer"
665 Hardware driver for the TI AR7 Watchdog Timer.
668 tristate "Toshiba TXx9 Watchdog Timer"
669 depends on CPU_TX39XX || CPU_TX49XX
671 Hardware driver for the built-in watchdog timer on TXx9 MIPS SoCs.
673 # PARISC Architecture
675 # POWERPC Architecture
678 tristate "MPC5200 Watchdog Timer"
679 depends on PPC_MPC52xx
682 tristate "MPC8xx Watchdog Timer"
686 tristate "MPC83xx Watchdog Timer"
690 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
694 bool "PowerPC Book-E Watchdog Timer"
695 depends on BOOKE || 4xx
697 Please see Documentation/watchdog/watchdog-api.txt for
703 tristate "RTAS watchdog"
706 This driver adds watchdog support for the RTAS watchdog.
708 To compile this driver as a module, choose M here. The module
709 will be called wdrtas.
714 tristate "z/VM Watchdog Timer"
717 IBM s/390 and zSeries machines running under z/VM 5.1 or later
718 provide a virtual watchdog timer to their guest that cause a
719 user define Control Program command to be executed after a
722 To compile this driver as a module, choose M here. The module
723 will be called vmwatchdog.
725 # SUPERH (sh + sh64) Architecture
728 tristate "SuperH Watchdog"
729 depends on SUPERH && (CPU_SH3 || CPU_SH4)
731 This driver adds watchdog support for the integrated watchdog in the
732 SuperH processors. If you have one of these processors and wish
733 to have watchdog support enabled, say Y, otherwise say N.
735 As a side note, saying Y here will automatically boost HZ to 1000
736 so that the timer has a chance to clear the overflow counter. On
737 slower systems (such as the SH-2 and SH-3) this will likely yield
738 some performance issues. As such, the WDT should be avoided here
739 unless it is absolutely necessary.
741 To compile this driver as a module, choose M here: the
742 module will be called shwdt.
745 bool "Allow mmap of SH WDT"
749 If you say Y here, user applications will be able to mmap the
754 # SPARC64 Architecture
756 config WATCHDOG_CP1XXX
757 tristate "CP1XXX Hardware Watchdog support"
758 depends on SPARC64 && PCI
760 This is the driver for the hardware watchdog timers present on
761 Sun Microsystems CompactPCI models CP1400 and CP1500.
763 To compile this driver as a module, choose M here: the
764 module will be called cpwatchdog.
766 If you do not have a CompactPCI model CP1400 or CP1500, or
767 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
768 you should say N to this option.
771 tristate "RIO Hardware Watchdog support"
772 depends on SPARC64 && PCI
774 Say Y here to support the hardware watchdog capability on Sun RIO
775 machines. The watchdog timeout period is normally one minute but
776 can be changed with a boot-time parameter.
780 # XTENSA Architecture
783 # ISA-based Watchdog Cards
786 comment "ISA-based Watchdog Cards"
790 tristate "Berkshire Products ISA-PC Watchdog"
793 This is the driver for the Berkshire Products ISA-PC Watchdog card.
794 This card simply watches your kernel to make sure it doesn't freeze,
795 and if it does, it reboots your computer after a certain amount of
796 time. This driver is like the WDT501 driver but for different
797 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
798 watchdog cards can be ordered from <http://www.berkprod.com/>.
800 To compile this driver as a module, choose M here: the
801 module will be called pcwd.
803 Most people will say N.
806 tristate "Mixcom Watchdog"
809 This is a driver for the Mixcom hardware watchdog cards. This
810 watchdog simply watches your kernel to make sure it doesn't freeze,
811 and if it does, it reboots your computer after a certain amount of
814 To compile this driver as a module, choose M here: the
815 module will be called mixcomwd.
817 Most people will say N.
820 tristate "WDT Watchdog timer"
823 If you have a WDT500P or WDT501P watchdog board, say Y here,
824 otherwise N. It is not possible to probe for this board, which means
825 that you have to inform the kernel about the IO port and IRQ that
826 is needed (you can do this via the io and irq parameters)
828 To compile this driver as a module, choose M here: the
829 module will be called wdt.
832 bool "WDT501 features"
835 Saying Y here and creating a character special file /dev/temperature
836 with major number 10 and minor number 131 ("man mknod") will give
837 you a thermometer inside your computer: reading from
838 /dev/temperature yields one byte, the temperature in degrees
839 Fahrenheit. This works only if you have a WDT501P watchdog board
842 If you want to enable the Fan Tachometer on the WDT501P, then you
843 can do this via the tachometer parameter. Only do this if you have a
844 fan tachometer actually set up.
847 # PCI-based Watchdog Cards
850 comment "PCI-based Watchdog Cards"
854 tristate "Berkshire Products PCI-PC Watchdog"
857 This is the driver for the Berkshire Products PCI-PC Watchdog card.
858 This card 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
860 time. The card can also monitor the internal temperature of the PC.
861 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
863 To compile this driver as a module, choose M here: the
864 module will be called pcwd_pci.
866 Most people will say N.
869 tristate "PCI-WDT500/501 Watchdog timer"
872 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
874 To compile this driver as a module, choose M here: the
875 module will be called wdt_pci.
878 bool "PCI-WDT501 features"
881 Saying Y here and creating a character special file /dev/temperature
882 with major number 10 and minor number 131 ("man mknod") will give
883 you a thermometer inside your computer: reading from
884 /dev/temperature yields one byte, the temperature in degrees
885 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
888 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
889 can do this via the tachometer parameter. Only do this if you have a
890 fan tachometer actually set up.
893 # USB-based Watchdog Cards
896 comment "USB-based Watchdog Cards"
900 tristate "Berkshire Products USB-PC Watchdog"
903 This is the driver for the Berkshire Products USB-PC Watchdog card.
904 This card simply watches your kernel to make sure it doesn't freeze,
905 and if it does, it reboots your computer after a certain amount of
906 time. The card can also monitor the internal temperature of the PC.
907 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
909 To compile this driver as a module, choose M here: the
910 module will be called pcwd_usb.
912 Most people will say N.