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
40 source "drivers/watchdog/core/Kconfig"
43 # General Watchdog drivers
46 comment "Watchdog Device Drivers"
48 # Architecture Independent
51 tristate "Software watchdog"
53 A software monitoring watchdog. This will fail to reboot your system
54 from some situations that the hardware watchdog will recover
55 from. Equally it's a lot cheaper to install.
57 To compile this driver as a module, choose M here: the
58 module will be called softdog.
64 config AT91RM9200_WATCHDOG
65 tristate "AT91RM9200 watchdog"
66 depends on ARCH_AT91RM9200
68 Watchdog timer embedded into AT91RM9200 chips. This will reboot your
69 system when the timeout is reached.
72 tristate "DC21285 watchdog"
75 The Intel Footbridge chip contains a built-in watchdog circuit. Say Y
76 here if you wish to use this. Alternatively say M to compile the
77 driver as a module, which will be called wdt285.
79 This driver does not work on all machines. In particular, early CATS
80 boards have hardware problems that will cause the machine to simply
81 lock up if the watchdog fires.
83 "If in doubt, leave it out" - say N.
86 tristate "NetWinder WB83C977 watchdog"
87 depends on FOOTBRIDGE && ARCH_NETWINDER
89 Say Y here to include support for the WB977 watchdog included in
90 NetWinder machines. Alternatively say M to compile the driver as
91 a module, which will be called wdt977.
93 Not sure? It's safe to say N.
95 config IXP2000_WATCHDOG
96 tristate "IXP2000 Watchdog"
97 depends on ARCH_IXP2000
99 Say Y here if to include support for the watchdog timer
100 in the Intel IXP2000(2400, 2800, 2850) network processors.
101 This driver can be built as a module by choosing M. The module
102 will be called ixp2000_wdt.
104 Say N if you are unsure.
106 config IXP4XX_WATCHDOG
107 tristate "IXP4xx Watchdog"
108 depends on ARCH_IXP4XX
110 Say Y here if to include support for the watchdog timer
111 in the Intel IXP4xx network processors. This driver can
112 be built as a module by choosing M. The module will
113 be called ixp4xx_wdt.
115 Note: The internal IXP4xx watchdog does a soft CPU reset
116 which doesn't reset any peripherals. There are circumstances
117 where the watchdog will fail to reset the board correctly
118 (e.g., if the boot ROM is in an unreadable state).
120 Say N if you are unsure.
122 config KS8695_WATCHDOG
123 tristate "KS8695 watchdog"
124 depends on ARCH_KS8695
126 Watchdog timer embedded into KS8695 processor. This will reboot your
127 system when the timeout is reached.
129 config S3C2410_WATCHDOG
130 tristate "S3C2410 Watchdog"
131 depends on ARCH_S3C2410
133 Watchdog timer block in the Samsung S3C2410 chips. This will
134 reboot the system when the timer expires with the watchdog
137 The driver is limited by the speed of the system's PCLK
138 signal, so with reasonably fast systems (PCLK around 50-66MHz)
139 then watchdog intervals of over approximately 20seconds are
142 The driver can be built as a module by choosing M, and will
143 be called s3c2410_wdt
145 config SA1100_WATCHDOG
146 tristate "SA1100/PXA2xx watchdog"
147 depends on ARCH_SA1100 || ARCH_PXA
149 Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
150 reboot your system when timeout is reached.
152 NOTE: once enabled, this timer cannot be disabled.
154 To compile this driver as a module, choose M here: the
155 module will be called sa1100_wdt.
157 config MPCORE_WATCHDOG
158 tristate "MPcore watchdog"
159 depends on ARM_MPCORE_PLATFORM && LOCAL_TIMERS
161 Watchdog timer embedded into the MPcore system.
163 To compile this driver as a module, choose M here: the
164 module will be called mpcore_wdt.
166 config EP93XX_WATCHDOG
167 tristate "EP93xx Watchdog"
168 depends on ARCH_EP93XX
170 Say Y here if to include support for the watchdog timer
171 embedded in the Cirrus Logic EP93xx family of devices.
173 To compile this driver as a module, choose M here: the
174 module will be called ep93xx_wdt.
177 tristate "OMAP Watchdog"
178 depends on ARCH_OMAP16XX || ARCH_OMAP24XX
180 Support for TI OMAP1610/OMAP1710/OMAP2420 watchdog. Say 'Y' here to
181 enable the OMAP1610/OMAP1710 watchdog timer.
183 config PNX4008_WATCHDOG
184 tristate "PNX4008 Watchdog"
185 depends on ARCH_PNX4008
187 Say Y here if to include support for the watchdog timer
188 in the PNX4008 processor.
189 This driver can be built as a module by choosing M. The module
190 will be called pnx4008_wdt.
192 Say N if you are unsure.
195 tristate "IOP Watchdog"
197 select WATCHDOG_NOWAYOUT if (ARCH_IOP32X || ARCH_IOP33X)
199 Say Y here if to include support for the watchdog timer
200 in the Intel IOP3XX & IOP13XX I/O Processors. This driver can
201 be built as a module by choosing M. The module will
204 Note: The IOP13XX watchdog does an Internal Bus Reset which will
205 affect both cores and the peripherals of the IOP. The ATU-X
206 and/or ATUe configuration registers will remain intact, but if
207 operating as an Root Complex and/or Central Resource, the PCI-X
208 and/or PCIe busses will also be reset. THIS IS A VERY BIG HAMMER.
210 config DAVINCI_WATCHDOG
211 tristate "DaVinci watchdog"
212 depends on ARCH_DAVINCI
214 Say Y here if to include support for the watchdog timer
215 in the DaVinci DM644x/DM646x processors.
216 To compile this driver as a module, choose M here: the
217 module will be called davinci_wdt.
219 NOTE: once enabled, this timer cannot be disabled.
220 Say N if you are unsure.
226 config AT32AP700X_WDT
227 tristate "AT32AP700x watchdog"
228 depends on CPU_AT32AP7000
230 Watchdog timer embedded into AT32AP700x devices. This will reboot
231 your system when the timeout is reached.
233 # BLACKFIN Architecture
236 tristate "Blackfin On-Chip Watchdog Timer"
239 If you say yes here you will get support for the Blackfin On-Chip
240 Watchdog Timer. If you have one of these processors and wish to
241 have watchdog support enabled, say Y, otherwise say N.
243 To compile this driver as a module, choose M here: the
244 module will be called bfin_wdt.
252 # X86 (i386 + ia64 + x86_64) Architecture
255 tristate "Acquire SBC Watchdog Timer"
258 This is the driver for the hardware watchdog on Single Board
259 Computers produced by Acquire Inc (and others). This watchdog
260 simply watches your kernel to make sure it doesn't freeze, and if
261 it does, it reboots your computer after a certain amount of time.
263 To compile this driver as a module, choose M here: the
264 module will be called acquirewdt.
266 Most people will say N.
269 tristate "Advantech SBC Watchdog Timer"
272 If you are configuring a Linux kernel for the Advantech single-board
273 computer, say `Y' here to support its built-in watchdog timer
274 feature. More information can be found at
275 <http://www.advantech.com.tw/products/>
278 tristate "ALi M1535 PMU Watchdog Timer"
279 depends on X86 && PCI
281 This is the driver for the hardware watchdog on the ALi M1535 PMU.
283 To compile this driver as a module, choose M here: the
284 module will be called alim1535_wdt.
286 Most people will say N.
289 tristate "ALi M7101 PMU Computer Watchdog"
290 depends on X86 && PCI
292 This is the driver for the hardware watchdog on the ALi M7101 PMU
293 as used in the x86 Cobalt servers.
295 To compile this driver as a module, choose M here: the
296 module will be called alim7101_wdt.
298 Most people will say N.
301 tristate "AMD Elan SC520 processor Watchdog"
304 This is the driver for the hardware watchdog built in to the
305 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
306 This watchdog simply watches your kernel to make sure it doesn't
307 freeze, and if it does, it reboots your computer after a certain
310 You can compile this driver directly into the kernel, or use
311 it as a module. The module will be called sc520_wdt.
314 tristate "Eurotech CPU-1220/1410 Watchdog Timer"
317 Enable support for the watchdog timer on the Eurotech CPU-1220 and
318 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
319 information are at <http://www.eurotech.it/>.
322 tristate "IB700 SBC Watchdog Timer"
325 This is the driver for the hardware watchdog on the IB700 Single
326 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
327 simply watches your kernel to make sure it doesn't freeze, and if
328 it does, it reboots your computer after a certain amount of time.
330 This driver is like the WDT501 driver but for slightly different hardware.
332 To compile this driver as a module, choose M here: the
333 module will be called ib700wdt.
335 Most people will say N.
338 tristate "IBM Automatic Server Restart"
341 This is the driver for the IBM Automatic Server Restart watchdog
342 timer built-in into some eServer xSeries machines.
344 To compile this driver as a module, choose M here: the
345 module will be called ibmasr.
348 tristate "ICP Single Board Computer Watchdog Timer"
351 This is a driver for the hardware watchdog on the ICP Single
352 Board Computer. This driver is working on (at least) the following
353 IPC SBC's: Wafer 5823, Rocky 4783, Rocky 3703 and Rocky 3782.
355 To compile this driver as a module, choose M here: the
356 module will be called wafer5823wdt.
359 tristate "Intel 6300ESB Timer/Watchdog"
360 depends on X86 && PCI
362 Hardware driver for the watchdog timer built into the Intel
363 6300ESB controller hub.
365 To compile this driver as a module, choose M here: the
366 module will be called i6300esb.
369 tristate "Intel TCO Timer/Watchdog"
370 depends on (X86 || IA64) && PCI
373 Hardware driver for the intel TCO timer based watchdog devices.
374 These drivers are included in the Intel 82801 I/O Controller
375 Hub family (from ICH0 up to ICH9) and in the Intel 63xxESB
378 The TCO (Total Cost of Ownership) timer is a watchdog timer
379 that will reboot the machine after its second expiration. The
380 expiration time can be configured with the "heartbeat" parameter.
382 On some motherboards the driver may fail to reset the chipset's
383 NO_REBOOT flag which prevents the watchdog from rebooting the
384 machine. If this is the case you will get a kernel message like
385 "failed to reset NO_REBOOT flag, reboot disabled by hardware".
387 To compile this driver as a module, choose M here: the
388 module will be called iTCO_wdt.
390 config ITCO_VENDOR_SUPPORT
391 bool "Intel TCO Timer/Watchdog Specific Vendor Support"
394 Add vendor specific support to the intel TCO timer based watchdog
395 devices. At this moment we only have additional support for some
396 SuperMicro Inc. motherboards.
399 tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
402 This is a driver for National Semiconductor PC87307/PC97307 hardware
403 watchdog cards as found on the SC1200. This watchdog is mainly used
404 for power management purposes and can be used to power down the device
405 during inactivity periods (includes interrupt activity monitoring).
407 To compile this driver as a module, choose M here: the
408 module will be called sc1200wdt.
410 Most people will say N.
413 tristate "National Semiconductor SCx200 Watchdog"
414 depends on SCx200 && PCI
416 Enable the built-in watchdog timer support on the National
417 Semiconductor SCx200 processors.
419 If compiled as a module, it will be called scx200_wdt.
422 tristate "NS PC87413 watchdog"
425 This is the driver for the hardware watchdog on the PC87413 chipset
426 This watchdog simply watches your kernel to make sure it doesn't
427 freeze, and if it does, it reboots your computer after a certain
430 To compile this driver as a module, choose M here: the
431 module will be called pc87413_wdt.
433 Most people will say N.
436 tristate "SBC-60XX Watchdog Timer"
439 This driver can be used with the watchdog timer found on some
440 single board computers, namely the 6010 PII based computer.
441 It may well work with other cards. It reads port 0x443 to enable
442 and re-set the watchdog timer, and reads port 0x45 to disable
443 the watchdog. If you have a card that behave in similar ways,
444 you can probably make this driver work with your card as well.
446 You can compile this driver directly into the kernel, or use
447 it as a module. The module will be called sbc60xxwdt.
450 tristate "SBC8360 Watchdog Timer"
454 This is the driver for the hardware watchdog on the SBC8360 Single
455 Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
457 To compile this driver as a module, choose M here: the
458 module will be called sbc8360.ko.
460 Most people will say N.
463 tristate "SBC Nano 7240 Watchdog Timer"
466 This is the driver for the hardware watchdog found on the IEI
467 single board computers EPIC Nano 7240 (and likely others). This
468 watchdog simply watches your kernel to make sure it doesn't freeze,
469 and if it does, it reboots your computer after a certain amount of
472 To compile this driver as a module, choose M here: the
473 module will be called sbc7240_wdt.
476 tristate "SMA CPU5 Watchdog"
480 To compile this driver as a module, choose M here: the
481 module will be called cpu5wdt.
483 config SMSC37B787_WDT
484 tristate "Winbond SMsC37B787 Watchdog Timer"
487 This is the driver for the hardware watchdog component on the
488 Winbond SMsC37B787 chipset as used on the NetRunner Mainboard
489 from Vision Systems and maybe others.
491 This watchdog simply watches your kernel to make sure it doesn't
492 freeze, and if it does, it reboots your computer after a certain
495 Usually a userspace daemon will notify the kernel WDT driver that
496 userspace is still alive, at regular intervals.
498 To compile this driver as a module, choose M here: the
499 module will be called smsc37b787_wdt.
501 Most people will say N.
504 tristate "W83627HF Watchdog Timer"
507 This is the driver for the hardware watchdog on the W83627HF chipset
508 as used in Advantech PC-9578 and Tyan S2721-533 motherboards
509 (and likely others). This watchdog simply watches your kernel to
510 make sure it doesn't freeze, and if it does, it reboots your computer
511 after a certain amount of time.
513 To compile this driver as a module, choose M here: the
514 module will be called w83627hf_wdt.
516 Most people will say N.
519 tristate "W83697HF/W83697HG Watchdog Timer"
522 This is the driver for the hardware watchdog on the W83697HF/HG
523 chipset as used in Dedibox/VIA motherboards (and likely others).
524 This watchdog simply watches your kernel to make sure it doesn't
525 freeze, and if it does, it reboots your computer after a certain
528 To compile this driver as a module, choose M here: the
529 module will be called w83697hf_wdt.
531 Most people will say N.
534 tristate "W83877F (EMACS) Watchdog Timer"
537 This is the driver for the hardware watchdog on the W83877F chipset
538 as used in EMACS PC-104 motherboards (and likely others). This
539 watchdog simply watches your kernel to make sure it doesn't freeze,
540 and if it does, it reboots your computer after a certain amount of
543 To compile this driver as a module, choose M here: the
544 module will be called w83877f_wdt.
546 Most people will say N.
549 tristate "W83977F (PCM-5335) Watchdog Timer"
552 This is the driver for the hardware watchdog on the W83977F I/O chip
553 as used in AAEON's PCM-5335 SBC (and likely others). This
554 watchdog simply watches your kernel to make sure it doesn't freeze,
555 and if it does, it reboots your computer after a certain amount of
558 To compile this driver as a module, choose M here: the
559 module will be called w83977f_wdt.
562 tristate "ZF MachZ Watchdog"
565 If you are using a ZF Micro MachZ processor, say Y here, otherwise
566 N. This is the driver for the watchdog timer built-in on that
567 processor using ZF-Logic interface. This watchdog simply watches
568 your kernel to make sure it doesn't freeze, and if it does, it
569 reboots your computer after a certain amount of time.
571 To compile this driver as a module, choose M here: the
572 module will be called machzwd.
574 config SBC_EPX_C3_WATCHDOG
575 tristate "Winsystems SBC EPX-C3 watchdog"
578 This is the driver for the built-in watchdog timer on the EPX-C3
579 Single-board computer made by Winsystems, Inc.
581 *Note*: This hardware watchdog is not probeable and thus there
582 is no way to know if writing to its IO address will corrupt
583 your system or have any real effect. The only way to be sure
584 that this driver does what you want is to make sure you
585 are running it on an EPX-C3 from Winsystems with the watchdog
586 timer at IO address 0x1ee and 0x1ef. It will write to both those
587 IO ports. Basically, the assumption is made that if you compile
588 this driver into your kernel and/or load it as a module, that you
589 know what you are doing and that you are in fact running on an
592 To compile this driver as a module, choose M here: the
593 module will be called sbc_epx_c3.
599 # M68KNOMMU Architecture
604 tristate "Indy/I2 Hardware Watchdog"
607 Hardware driver for the Indy's/I2's watchdog. This is a
608 watchdog timer that will reboot the machine after a 60 second
609 timer expired and no process has written to /dev/watchdog during
613 tristate "MTX-1 Hardware Watchdog"
616 Hardware driver for the MTX-1 boards. This is a watchdog timer that
617 will reboot the machine after a 100 seconds timer expired.
620 tristate "RM9000/GPI hardware watchdog"
621 depends on CPU_RM9000
623 Watchdog implementation using the GPI hardware found on
624 PMC-Sierra RM9xxx CPUs.
626 To compile this driver as a module, choose M here: the
627 module will be called rm9k_wdt.
630 tristate "TI AR7 Watchdog Timer"
633 Hardware driver for the TI AR7 Watchdog Timer.
635 # PARISC Architecture
637 # POWERPC Architecture
640 tristate "MPC5200 Watchdog Timer"
641 depends on PPC_MPC52xx
644 tristate "MPC8xx Watchdog Timer"
648 tristate "MPC83xx Watchdog Timer"
652 tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
656 bool "PowerPC Book-E Watchdog Timer"
657 depends on BOOKE || 4xx
659 Please see Documentation/watchdog/watchdog-api.txt for
665 tristate "RTAS watchdog"
668 This driver adds watchdog support for the RTAS watchdog.
670 To compile this driver as a module, choose M here. The module
671 will be called wdrtas.
676 tristate "z/VM Watchdog Timer"
679 IBM s/390 and zSeries machines running under z/VM 5.1 or later
680 provide a virtual watchdog timer to their guest that cause a
681 user define Control Program command to be executed after a
684 To compile this driver as a module, choose M here. The module
685 will be called vmwatchdog.
687 # SUPERH (sh + sh64) Architecture
690 tristate "SuperH Watchdog"
691 depends on SUPERH && (CPU_SH3 || CPU_SH4)
693 This driver adds watchdog support for the integrated watchdog in the
694 SuperH processors. If you have one of these processors and wish
695 to have watchdog support enabled, say Y, otherwise say N.
697 As a side note, saying Y here will automatically boost HZ to 1000
698 so that the timer has a chance to clear the overflow counter. On
699 slower systems (such as the SH-2 and SH-3) this will likely yield
700 some performance issues. As such, the WDT should be avoided here
701 unless it is absolutely necessary.
703 To compile this driver as a module, choose M here: the
704 module will be called shwdt.
707 bool "Allow mmap of SH WDT"
711 If you say Y here, user applications will be able to mmap the
716 # SPARC64 Architecture
718 config WATCHDOG_CP1XXX
719 tristate "CP1XXX Hardware Watchdog support"
720 depends on SPARC64 && PCI
722 This is the driver for the hardware watchdog timers present on
723 Sun Microsystems CompactPCI models CP1400 and CP1500.
725 To compile this driver as a module, choose M here: the
726 module will be called cpwatchdog.
728 If you do not have a CompactPCI model CP1400 or CP1500, or
729 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
730 you should say N to this option.
733 tristate "RIO Hardware Watchdog support"
734 depends on SPARC64 && PCI
736 Say Y here to support the hardware watchdog capability on Sun RIO
737 machines. The watchdog timeout period is normally one minute but
738 can be changed with a boot-time parameter.
742 # XTENSA Architecture
745 # ISA-based Watchdog Cards
748 comment "ISA-based Watchdog Cards"
752 tristate "Berkshire Products ISA-PC Watchdog"
755 This is the driver for the Berkshire Products ISA-PC Watchdog card.
756 This card simply watches your kernel to make sure it doesn't freeze,
757 and if it does, it reboots your computer after a certain amount of
758 time. This driver is like the WDT501 driver but for different
759 hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
760 watchdog cards can be ordered from <http://www.berkprod.com/>.
762 To compile this driver as a module, choose M here: the
763 module will be called pcwd.
765 Most people will say N.
768 tristate "Mixcom Watchdog"
771 This is a driver for the Mixcom hardware watchdog cards. This
772 watchdog simply watches your kernel to make sure it doesn't freeze,
773 and if it does, it reboots your computer after a certain amount of
776 To compile this driver as a module, choose M here: the
777 module will be called mixcomwd.
779 Most people will say N.
782 tristate "WDT Watchdog timer"
785 If you have a WDT500P or WDT501P watchdog board, say Y here,
786 otherwise N. It is not possible to probe for this board, which means
787 that you have to inform the kernel about the IO port and IRQ that
788 is needed (you can do this via the io and irq parameters)
790 To compile this driver as a module, choose M here: the
791 module will be called wdt.
794 bool "WDT501 features"
797 Saying Y here and creating a character special file /dev/temperature
798 with major number 10 and minor number 131 ("man mknod") will give
799 you a thermometer inside your computer: reading from
800 /dev/temperature yields one byte, the temperature in degrees
801 Fahrenheit. This works only if you have a WDT501P watchdog board
804 If you want to enable the Fan Tachometer on the WDT501P, then you
805 can do this via the tachometer parameter. Only do this if you have a
806 fan tachometer actually set up.
809 # PCI-based Watchdog Cards
812 comment "PCI-based Watchdog Cards"
816 tristate "Berkshire Products PCI-PC Watchdog"
819 This is the driver for the Berkshire Products PCI-PC Watchdog card.
820 This card simply watches your kernel to make sure it doesn't freeze,
821 and if it does, it reboots your computer after a certain amount of
822 time. The card can also monitor the internal temperature of the PC.
823 More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
825 To compile this driver as a module, choose M here: the
826 module will be called pcwd_pci.
828 Most people will say N.
831 tristate "PCI-WDT500/501 Watchdog timer"
834 If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
836 To compile this driver as a module, choose M here: the
837 module will be called wdt_pci.
840 bool "PCI-WDT501 features"
843 Saying Y here and creating a character special file /dev/temperature
844 with major number 10 and minor number 131 ("man mknod") will give
845 you a thermometer inside your computer: reading from
846 /dev/temperature yields one byte, the temperature in degrees
847 Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
850 If you want to enable the Fan Tachometer on the PCI-WDT501, then you
851 can do this via the tachometer parameter. Only do this if you have a
852 fan tachometer actually set up.
855 # USB-based Watchdog Cards
858 comment "USB-based Watchdog Cards"
862 tristate "Berkshire Products USB-PC Watchdog"
865 This is the driver for the Berkshire Products USB-PC Watchdog card.
866 This card simply watches your kernel to make sure it doesn't freeze,
867 and if it does, it reboots your computer after a certain amount of
868 time. The card can also monitor the internal temperature of the PC.
869 More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
871 To compile this driver as a module, choose M here: the
872 module will be called pcwd_usb.
874 Most people will say N.