Kconfig 21 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652
  1. #
  2. # Watchdog device configuration
  3. #
  4. menu "Watchdog Cards"
  5. config 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. online 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. The watchdog is usually used together with the watchdog daemon
  21. which is available from
  22. <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
  23. also monitor NFS connections and can reboot the machine when the process
  24. table is full.
  25. If unsure, say N.
  26. config WATCHDOG_NOWAYOUT
  27. bool "Disable watchdog shutdown on close"
  28. depends on WATCHDOG
  29. help
  30. The default watchdog behaviour (which you get if you say N here) is
  31. to stop the timer if the process managing it closes the file
  32. /dev/watchdog. It's always remotely possible that this process might
  33. get killed. If you say Y here, the watchdog cannot be stopped once
  34. it has been started.
  35. #
  36. # General Watchdog drivers
  37. #
  38. comment "Watchdog Device Drivers"
  39. depends on WATCHDOG
  40. # Architecture Independant
  41. config SOFT_WATCHDOG
  42. tristate "Software watchdog"
  43. depends on WATCHDOG
  44. help
  45. A software monitoring watchdog. This will fail to reboot your system
  46. from some situations that the hardware watchdog will recover
  47. from. Equally it's a lot cheaper to install.
  48. To compile this driver as a module, choose M here: the
  49. module will be called softdog.
  50. # ARM Architecture
  51. config 21285_WATCHDOG
  52. tristate "DC21285 watchdog"
  53. depends on WATCHDOG && FOOTBRIDGE
  54. help
  55. The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
  56. here if you wish to use this. Alternatively say M to compile the
  57. driver as a module, which will be called wdt285.
  58. This driver does not work on all machines. In particular, early CATS
  59. boards have hardware problems that will cause the machine to simply
  60. lock up if the watchdog fires.
  61. "If in doubt, leave it out" - say N.
  62. config 977_WATCHDOG
  63. tristate "NetWinder WB83C977 watchdog"
  64. depends on WATCHDOG && FOOTBRIDGE && ARCH_NETWINDER
  65. help
  66. Say Y here to include support for the WB977 watchdog included in
  67. NetWinder machines. Alternatively say M to compile the driver as
  68. a module, which will be called wdt977.
  69. Not sure? It's safe to say N.
  70. config IXP2000_WATCHDOG
  71. tristate "IXP2000 Watchdog"
  72. depends on WATCHDOG && ARCH_IXP2000
  73. help
  74. Say Y here if to include support for the watchdog timer
  75. in the Intel IXP2000(2400, 2800, 2850) network processors.
  76. This driver can be built as a module by choosing M. The module
  77. will be called ixp2000_wdt.
  78. Say N if you are unsure.
  79. config IXP4XX_WATCHDOG
  80. tristate "IXP4xx Watchdog"
  81. depends on WATCHDOG && ARCH_IXP4XX
  82. help
  83. Say Y here if to include support for the watchdog timer
  84. in the Intel IXP4xx network processors. This driver can
  85. be built as a module by choosing M. The module will
  86. be called ixp4xx_wdt.
  87. Note: The internal IXP4xx watchdog does a soft CPU reset
  88. which doesn't reset any peripherals. There are circumstances
  89. where the watchdog will fail to reset the board correctly
  90. (e.g., if the boot ROM is in an unreadable state).
  91. Say N if you are unsure.
  92. config S3C2410_WATCHDOG
  93. tristate "S3C2410 Watchdog"
  94. depends on WATCHDOG && ARCH_S3C2410
  95. help
  96. Watchdog timer block in the Samsung S3C2410 chips. This will
  97. reboot the system when the timer expires with the watchdog
  98. enabled.
  99. The driver is limited by the speed of the system's PCLK
  100. signal, so with reasonbaly fast systems (PCLK around 50-66MHz)
  101. then watchdog intervals of over approximately 20seconds are
  102. unavailable.
  103. The driver can be built as a module by choosing M, and will
  104. be called s3c2410_wdt
  105. config SA1100_WATCHDOG
  106. tristate "SA1100/PXA2xx watchdog"
  107. depends on WATCHDOG && ( ARCH_SA1100 || ARCH_PXA )
  108. help
  109. Watchdog timer embedded into SA11x0 and PXA2xx chips. This will
  110. reboot your system when timeout is reached.
  111. NOTE: once enabled, this timer cannot be disabled.
  112. To compile this driver as a module, choose M here: the
  113. module will be called sa1100_wdt.
  114. config MPCORE_WATCHDOG
  115. tristate "MPcore watchdog"
  116. depends on WATCHDOG && ARM_MPCORE_PLATFORM && LOCAL_TIMERS
  117. help
  118. Watchdog timer embedded into the MPcore system.
  119. To compile this driver as a module, choose M here: the
  120. module will be called mpcore_wdt.
  121. # X86 (i386 + ia64 + x86_64) Architecture
  122. config ACQUIRE_WDT
  123. tristate "Acquire SBC Watchdog Timer"
  124. depends on WATCHDOG && X86
  125. ---help---
  126. This is the driver for the hardware watchdog on Single Board
  127. Computers produced by Acquire Inc (and others). This watchdog
  128. simply watches your kernel to make sure it doesn't freeze, and if
  129. it does, it reboots your computer after a certain amount of time.
  130. To compile this driver as a module, choose M here: the
  131. module will be called acquirewdt.
  132. Most people will say N.
  133. config ADVANTECH_WDT
  134. tristate "Advantech SBC Watchdog Timer"
  135. depends on WATCHDOG && X86
  136. help
  137. If you are configuring a Linux kernel for the Advantech single-board
  138. computer, say `Y' here to support its built-in watchdog timer
  139. feature. More information can be found at
  140. <http://www.advantech.com.tw/products/>
  141. config ALIM1535_WDT
  142. tristate "ALi M1535 PMU Watchdog Timer"
  143. depends on WATCHDOG && X86 && PCI
  144. ---help---
  145. This is the driver for the hardware watchdog on the ALi M1535 PMU.
  146. To compile this driver as a module, choose M here: the
  147. module will be called alim1535_wdt.
  148. Most people will say N.
  149. config ALIM7101_WDT
  150. tristate "ALi M7101 PMU Computer Watchdog"
  151. depends on WATCHDOG && X86 && PCI
  152. help
  153. This is the driver for the hardware watchdog on the ALi M7101 PMU
  154. as used in the x86 Cobalt servers.
  155. To compile this driver as a module, choose M here: the
  156. module will be called alim7101_wdt.
  157. Most people will say N.
  158. config SC520_WDT
  159. tristate "AMD Elan SC520 processor Watchdog"
  160. depends on WATCHDOG && X86
  161. help
  162. This is the driver for the hardware watchdog built in to the
  163. AMD "Elan" SC520 microcomputer commonly used in embedded systems.
  164. This watchdog simply watches your kernel to make sure it doesn't
  165. freeze, and if it does, it reboots your computer after a certain
  166. amount of time.
  167. You can compile this driver directly into the kernel, or use
  168. it as a module. The module will be called sc520_wdt.
  169. config EUROTECH_WDT
  170. tristate "Eurotech CPU-1220/1410 Watchdog Timer"
  171. depends on WATCHDOG && X86
  172. help
  173. Enable support for the watchdog timer on the Eurotech CPU-1220 and
  174. CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
  175. information are at <http://www.eurotech.it/>.
  176. config IB700_WDT
  177. tristate "IB700 SBC Watchdog Timer"
  178. depends on WATCHDOG && X86
  179. ---help---
  180. This is the driver for the hardware watchdog on the IB700 Single
  181. Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
  182. simply watches your kernel to make sure it doesn't freeze, and if
  183. it does, it reboots your computer after a certain amount of time.
  184. This driver is like the WDT501 driver but for slightly different hardware.
  185. To compile this driver as a module, choose M here: the
  186. module will be called ib700wdt.
  187. Most people will say N.
  188. config IBMASR
  189. tristate "IBM Automatic Server Restart"
  190. depends on WATCHDOG && X86
  191. help
  192. This is the driver for the IBM Automatic Server Restart watchdog
  193. timer builtin into some eServer xSeries machines.
  194. To compile this driver as a module, choose M here: the
  195. module will be called ibmasr.
  196. config WAFER_WDT
  197. tristate "ICP Wafer 5823 Single Board Computer Watchdog"
  198. depends on WATCHDOG && X86
  199. help
  200. This is a driver for the hardware watchdog on the ICP Wafer 5823
  201. Single Board Computer (and probably other similar models).
  202. To compile this driver as a module, choose M here: the
  203. module will be called wafer5823wdt.
  204. config I6300ESB_WDT
  205. tristate "Intel 6300ESB Timer/Watchdog"
  206. depends on WATCHDOG && X86 && PCI
  207. ---help---
  208. Hardware driver for the watchdog timer built into the Intel
  209. 6300ESB controller hub.
  210. To compile this driver as a module, choose M here: the
  211. module will be called i6300esb.
  212. config I8XX_TCO
  213. tristate "Intel i8xx TCO Timer/Watchdog"
  214. depends on WATCHDOG && (X86 || IA64) && PCI
  215. ---help---
  216. Hardware driver for the TCO timer built into the Intel 82801
  217. I/O Controller Hub family. The TCO (Total Cost of Ownership)
  218. timer is a watchdog timer that will reboot the machine after
  219. its second expiration. The expiration time can be configured
  220. with the "heartbeat" parameter.
  221. On some motherboards the driver may fail to reset the chipset's
  222. NO_REBOOT flag which prevents the watchdog from rebooting the
  223. machine. If this is the case you will get a kernel message like
  224. "failed to reset NO_REBOOT flag, reboot disabled by hardware".
  225. To compile this driver as a module, choose M here: the
  226. module will be called i8xx_tco.
  227. config SC1200_WDT
  228. tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
  229. depends on WATCHDOG && X86
  230. help
  231. This is a driver for National Semiconductor PC87307/PC97307 hardware
  232. watchdog cards as found on the SC1200. This watchdog is mainly used
  233. for power management purposes and can be used to power down the device
  234. during inactivity periods (includes interrupt activity monitoring).
  235. To compile this driver as a module, choose M here: the
  236. module will be called sc1200wdt.
  237. Most people will say N.
  238. config SCx200_WDT
  239. tristate "National Semiconductor SCx200 Watchdog"
  240. depends on WATCHDOG && SCx200 && PCI
  241. help
  242. Enable the built-in watchdog timer support on the National
  243. Semiconductor SCx200 processors.
  244. If compiled as a module, it will be called scx200_wdt.
  245. config 60XX_WDT
  246. tristate "SBC-60XX Watchdog Timer"
  247. depends on WATCHDOG && X86
  248. help
  249. This driver can be used with the watchdog timer found on some
  250. single board computers, namely the 6010 PII based computer.
  251. It may well work with other cards. It reads port 0x443 to enable
  252. and re-set the watchdog timer, and reads port 0x45 to disable
  253. the watchdog. If you have a card that behave in similar ways,
  254. you can probably make this driver work with your card as well.
  255. You can compile this driver directly into the kernel, or use
  256. it as a module. The module will be called sbc60xxwdt.
  257. config SBC8360_WDT
  258. tristate "SBC8360 Watchdog Timer"
  259. depends on WATCHDOG && X86
  260. ---help---
  261. This is the driver for the hardware watchdog on the SBC8360 Single
  262. Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
  263. To compile this driver as a module, choose M here: the
  264. module will be called sbc8360.ko.
  265. Most people will say N.
  266. config CPU5_WDT
  267. tristate "SMA CPU5 Watchdog"
  268. depends on WATCHDOG && X86
  269. ---help---
  270. TBD.
  271. To compile this driver as a module, choose M here: the
  272. module will be called cpu5wdt.
  273. config W83627HF_WDT
  274. tristate "W83627HF Watchdog Timer"
  275. depends on WATCHDOG && X86
  276. ---help---
  277. This is the driver for the hardware watchdog on the W83627HF chipset
  278. as used in Advantech PC-9578 and Tyan S2721-533 motherboards
  279. (and likely others). This watchdog simply watches your kernel to
  280. make sure it doesn't freeze, and if it does, it reboots your computer
  281. after a certain amount of time.
  282. To compile this driver as a module, choose M here: the
  283. module will be called w83627hf_wdt.
  284. Most people will say N.
  285. config W83877F_WDT
  286. tristate "W83877F (EMACS) Watchdog Timer"
  287. depends on WATCHDOG && X86
  288. ---help---
  289. This is the driver for the hardware watchdog on the W83877F chipset
  290. as used in EMACS PC-104 motherboards (and likely others). This
  291. watchdog simply watches your kernel to make sure it doesn't freeze,
  292. and if it does, it reboots your computer after a certain amount of
  293. time.
  294. To compile this driver as a module, choose M here: the
  295. module will be called w83877f_wdt.
  296. Most people will say N.
  297. config W83977F_WDT
  298. tristate "W83977F (PCM-5335) Watchdog Timer"
  299. depends on WATCHDOG && X86
  300. ---help---
  301. This is the driver for the hardware watchdog on the W83977F I/O chip
  302. as used in AAEON's PCM-5335 SBC (and likely others). This
  303. watchdog simply watches your kernel to make sure it doesn't freeze,
  304. and if it does, it reboots your computer after a certain amount of
  305. time.
  306. To compile this driver as a module, choose M here: the
  307. module will be called w83977f_wdt.
  308. config MACHZ_WDT
  309. tristate "ZF MachZ Watchdog"
  310. depends on WATCHDOG && X86
  311. ---help---
  312. If you are using a ZF Micro MachZ processor, say Y here, otherwise
  313. N. This is the driver for the watchdog timer builtin on that
  314. processor using ZF-Logic interface. This watchdog simply watches
  315. your kernel to make sure it doesn't freeze, and if it does, it
  316. reboots your computer after a certain amount of time.
  317. To compile this driver as a module, choose M here: the
  318. module will be called machzwd.
  319. config SBC_EPX_C3_WATCHDOG
  320. tristate "Winsystems SBC EPX-C3 watchdog"
  321. depends on WATCHDOG && X86
  322. ---help---
  323. This is the driver for the built-in watchdog timer on the EPX-C3
  324. Single-board computer made by Winsystems, Inc.
  325. *Note*: This hardware watchdog is not probeable and thus there
  326. is no way to know if writing to its IO address will corrupt
  327. your system or have any real effect. The only way to be sure
  328. that this driver does what you want is to make sure you
  329. are runnning it on an EPX-C3 from Winsystems with the watchdog
  330. timer at IO address 0x1ee and 0x1ef. It will write to both those
  331. IO ports. Basically, the assumption is made that if you compile
  332. this driver into your kernel and/or load it as a module, that you
  333. know what you are doing and that you are in fact running on an
  334. EPX-C3 board!
  335. To compile this driver as a module, choose M here: the
  336. module will be called sbc_epx_c3.
  337. # PowerPC Architecture
  338. config 8xx_WDT
  339. tristate "MPC8xx Watchdog Timer"
  340. depends on WATCHDOG && 8xx
  341. config 83xx_WDT
  342. tristate "MPC83xx Watchdog Timer"
  343. depends on WATCHDOG && PPC_83xx
  344. config MV64X60_WDT
  345. tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
  346. depends on WATCHDOG && MV64X60
  347. config BOOKE_WDT
  348. tristate "PowerPC Book-E Watchdog Timer"
  349. depends on WATCHDOG && (BOOKE || 4xx)
  350. ---help---
  351. Please see Documentation/watchdog/watchdog-api.txt for
  352. more information.
  353. # PPC64 Architecture
  354. config WATCHDOG_RTAS
  355. tristate "RTAS watchdog"
  356. depends on WATCHDOG && PPC_RTAS
  357. help
  358. This driver adds watchdog support for the RTAS watchdog.
  359. To compile this driver as a module, choose M here. The module
  360. will be called wdrtas.
  361. # MIPS Architecture
  362. config INDYDOG
  363. tristate "Indy/I2 Hardware Watchdog"
  364. depends on WATCHDOG && SGI_IP22
  365. help
  366. Hardwaredriver for the Indy's/I2's watchdog. This is a
  367. watchdog timer that will reboot the machine after a 60 second
  368. timer expired and no process has written to /dev/watchdog during
  369. that time.
  370. # S390 Architecture
  371. config ZVM_WATCHDOG
  372. tristate "z/VM Watchdog Timer"
  373. depends on WATCHDOG && S390
  374. help
  375. IBM s/390 and zSeries machines running under z/VM 5.1 or later
  376. provide a virtual watchdog timer to their guest that cause a
  377. user define Control Program command to be executed after a
  378. timeout.
  379. To compile this driver as a module, choose M here. The module
  380. will be called vmwatchdog.
  381. # SUPERH Architecture
  382. config SH_WDT
  383. tristate "SuperH Watchdog"
  384. depends on WATCHDOG && SUPERH
  385. help
  386. This driver adds watchdog support for the integrated watchdog in the
  387. SuperH processors. If you have one of these processors and wish
  388. to have watchdog support enabled, say Y, otherwise say N.
  389. As a side note, saying Y here will automatically boost HZ to 1000
  390. so that the timer has a chance to clear the overflow counter. On
  391. slower systems (such as the SH-2 and SH-3) this will likely yield
  392. some performance issues. As such, the WDT should be avoided here
  393. unless it is absolutely necessary.
  394. To compile this driver as a module, choose M here: the
  395. module will be called shwdt.
  396. # SPARC64 Architecture
  397. config WATCHDOG_CP1XXX
  398. tristate "CP1XXX Hardware Watchdog support"
  399. depends on WATCHDOG && SPARC64 && PCI
  400. ---help---
  401. This is the driver for the hardware watchdog timers present on
  402. Sun Microsystems CompactPCI models CP1400 and CP1500.
  403. To compile this driver as a module, choose M here: the
  404. module will be called cpwatchdog.
  405. If you do not have a CompactPCI model CP1400 or CP1500, or
  406. another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
  407. you should say N to this option.
  408. config WATCHDOG_RIO
  409. tristate "RIO Hardware Watchdog support"
  410. depends on WATCHDOG && SPARC64 && PCI
  411. help
  412. Say Y here to support the hardware watchdog capability on Sun RIO
  413. machines. The watchdog timeout period is normally one minute but
  414. can be changed with a boot-time parameter.
  415. #
  416. # ISA-based Watchdog Cards
  417. #
  418. comment "ISA-based Watchdog Cards"
  419. depends on WATCHDOG && ISA
  420. config PCWATCHDOG
  421. tristate "Berkshire Products ISA-PC Watchdog"
  422. depends on WATCHDOG && ISA
  423. ---help---
  424. This is the driver for the Berkshire Products ISA-PC Watchdog card.
  425. This card simply watches your kernel to make sure it doesn't freeze,
  426. and if it does, it reboots your computer after a certain amount of
  427. time. This driver is like the WDT501 driver but for different
  428. hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
  429. watchdog cards can be ordered from <http://www.berkprod.com/>.
  430. To compile this driver as a module, choose M here: the
  431. module will be called pcwd.
  432. Most people will say N.
  433. config MIXCOMWD
  434. tristate "Mixcom Watchdog"
  435. depends on WATCHDOG && ISA
  436. ---help---
  437. This is a driver for the Mixcom hardware watchdog cards. This
  438. watchdog simply watches your kernel to make sure it doesn't freeze,
  439. and if it does, it reboots your computer after a certain amount of
  440. time.
  441. To compile this driver as a module, choose M here: the
  442. module will be called mixcomwd.
  443. Most people will say N.
  444. config WDT
  445. tristate "WDT Watchdog timer"
  446. depends on WATCHDOG && ISA
  447. ---help---
  448. If you have a WDT500P or WDT501P watchdog board, say Y here,
  449. otherwise N. It is not possible to probe for this board, which means
  450. that you have to inform the kernel about the IO port and IRQ that
  451. is needed (you can do this via the io and irq parameters)
  452. To compile this driver as a module, choose M here: the
  453. module will be called wdt.
  454. config WDT_501
  455. bool "WDT501 features"
  456. depends on WDT
  457. help
  458. Saying Y here and creating a character special file /dev/temperature
  459. with major number 10 and minor number 131 ("man mknod") will give
  460. you a thermometer inside your computer: reading from
  461. /dev/temperature yields one byte, the temperature in degrees
  462. Fahrenheit. This works only if you have a WDT501P watchdog board
  463. installed.
  464. If you want to enable the Fan Tachometer on the WDT501P, then you
  465. can do this via the tachometer parameter. Only do this if you have a
  466. fan tachometer actually set up.
  467. #
  468. # PCI-based Watchdog Cards
  469. #
  470. comment "PCI-based Watchdog Cards"
  471. depends on WATCHDOG && PCI
  472. config PCIPCWATCHDOG
  473. tristate "Berkshire Products PCI-PC Watchdog"
  474. depends on WATCHDOG && PCI
  475. ---help---
  476. This is the driver for the Berkshire Products PCI-PC Watchdog card.
  477. This card 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. The card can also monitor the internal temperature of the PC.
  480. More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
  481. To compile this driver as a module, choose M here: the
  482. module will be called pcwd_pci.
  483. Most people will say N.
  484. config WDTPCI
  485. tristate "PCI-WDT500/501 Watchdog timer"
  486. depends on WATCHDOG && PCI
  487. ---help---
  488. If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
  489. To compile this driver as a module, choose M here: the
  490. module will be called wdt_pci.
  491. config WDT_501_PCI
  492. bool "PCI-WDT501 features"
  493. depends on WDTPCI
  494. help
  495. Saying Y here and creating a character special file /dev/temperature
  496. with major number 10 and minor number 131 ("man mknod") will give
  497. you a thermometer inside your computer: reading from
  498. /dev/temperature yields one byte, the temperature in degrees
  499. Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
  500. installed.
  501. If you want to enable the Fan Tachometer on the PCI-WDT501, then you
  502. can do this via the tachometer parameter. Only do this if you have a
  503. fan tachometer actually set up.
  504. #
  505. # USB-based Watchdog Cards
  506. #
  507. comment "USB-based Watchdog Cards"
  508. depends on WATCHDOG && USB
  509. config USBPCWATCHDOG
  510. tristate "Berkshire Products USB-PC Watchdog"
  511. depends on WATCHDOG && USB
  512. ---help---
  513. This is the driver for the Berkshire Products USB-PC Watchdog card.
  514. This card simply watches your kernel to make sure it doesn't freeze,
  515. and if it does, it reboots your computer after a certain amount of
  516. time. The card can also monitor the internal temperature of the PC.
  517. More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
  518. To compile this driver as a module, choose M here: the
  519. module will be called pcwd_usb.
  520. Most people will say N.
  521. endmenu