Kconfig 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662
  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. config EP93XX_WATCHDOG
  122. tristate "EP93xx Watchdog"
  123. depends on WATCHDOG && ARCH_EP93XX
  124. help
  125. Say Y here if to include support for the watchdog timer
  126. embedded in the Cirrus Logic EP93xx family of devices.
  127. To compile this driver as a module, choose M here: the
  128. module will be called ep93xx_wdt.
  129. # X86 (i386 + ia64 + x86_64) Architecture
  130. config ACQUIRE_WDT
  131. tristate "Acquire SBC Watchdog Timer"
  132. depends on WATCHDOG && X86
  133. ---help---
  134. This is the driver for the hardware watchdog on Single Board
  135. Computers produced by Acquire Inc (and others). This watchdog
  136. simply watches your kernel to make sure it doesn't freeze, and if
  137. it does, it reboots your computer after a certain amount of time.
  138. To compile this driver as a module, choose M here: the
  139. module will be called acquirewdt.
  140. Most people will say N.
  141. config ADVANTECH_WDT
  142. tristate "Advantech SBC Watchdog Timer"
  143. depends on WATCHDOG && X86
  144. help
  145. If you are configuring a Linux kernel for the Advantech single-board
  146. computer, say `Y' here to support its built-in watchdog timer
  147. feature. More information can be found at
  148. <http://www.advantech.com.tw/products/>
  149. config ALIM1535_WDT
  150. tristate "ALi M1535 PMU Watchdog Timer"
  151. depends on WATCHDOG && X86 && PCI
  152. ---help---
  153. This is the driver for the hardware watchdog on the ALi M1535 PMU.
  154. To compile this driver as a module, choose M here: the
  155. module will be called alim1535_wdt.
  156. Most people will say N.
  157. config ALIM7101_WDT
  158. tristate "ALi M7101 PMU Computer Watchdog"
  159. depends on WATCHDOG && X86 && PCI
  160. help
  161. This is the driver for the hardware watchdog on the ALi M7101 PMU
  162. as used in the x86 Cobalt servers.
  163. To compile this driver as a module, choose M here: the
  164. module will be called alim7101_wdt.
  165. Most people will say N.
  166. config SC520_WDT
  167. tristate "AMD Elan SC520 processor Watchdog"
  168. depends on WATCHDOG && X86
  169. help
  170. This is the driver for the hardware watchdog built in to the
  171. AMD "Elan" SC520 microcomputer commonly used in embedded systems.
  172. This watchdog simply watches your kernel to make sure it doesn't
  173. freeze, and if it does, it reboots your computer after a certain
  174. amount of time.
  175. You can compile this driver directly into the kernel, or use
  176. it as a module. The module will be called sc520_wdt.
  177. config EUROTECH_WDT
  178. tristate "Eurotech CPU-1220/1410 Watchdog Timer"
  179. depends on WATCHDOG && X86
  180. help
  181. Enable support for the watchdog timer on the Eurotech CPU-1220 and
  182. CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
  183. information are at <http://www.eurotech.it/>.
  184. config IB700_WDT
  185. tristate "IB700 SBC Watchdog Timer"
  186. depends on WATCHDOG && X86
  187. ---help---
  188. This is the driver for the hardware watchdog on the IB700 Single
  189. Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
  190. simply watches your kernel to make sure it doesn't freeze, and if
  191. it does, it reboots your computer after a certain amount of time.
  192. This driver is like the WDT501 driver but for slightly different hardware.
  193. To compile this driver as a module, choose M here: the
  194. module will be called ib700wdt.
  195. Most people will say N.
  196. config IBMASR
  197. tristate "IBM Automatic Server Restart"
  198. depends on WATCHDOG && X86
  199. help
  200. This is the driver for the IBM Automatic Server Restart watchdog
  201. timer builtin into some eServer xSeries machines.
  202. To compile this driver as a module, choose M here: the
  203. module will be called ibmasr.
  204. config WAFER_WDT
  205. tristate "ICP Wafer 5823 Single Board Computer Watchdog"
  206. depends on WATCHDOG && X86
  207. help
  208. This is a driver for the hardware watchdog on the ICP Wafer 5823
  209. Single Board Computer (and probably other similar models).
  210. To compile this driver as a module, choose M here: the
  211. module will be called wafer5823wdt.
  212. config I6300ESB_WDT
  213. tristate "Intel 6300ESB Timer/Watchdog"
  214. depends on WATCHDOG && X86 && PCI
  215. ---help---
  216. Hardware driver for the watchdog timer built into the Intel
  217. 6300ESB controller hub.
  218. To compile this driver as a module, choose M here: the
  219. module will be called i6300esb.
  220. config I8XX_TCO
  221. tristate "Intel i8xx TCO Timer/Watchdog"
  222. depends on WATCHDOG && (X86 || IA64) && PCI
  223. ---help---
  224. Hardware driver for the TCO timer built into the Intel 82801
  225. I/O Controller Hub family. The TCO (Total Cost of Ownership)
  226. timer is a watchdog timer that will reboot the machine after
  227. its second expiration. The expiration time can be configured
  228. with the "heartbeat" parameter.
  229. On some motherboards the driver may fail to reset the chipset's
  230. NO_REBOOT flag which prevents the watchdog from rebooting the
  231. machine. If this is the case you will get a kernel message like
  232. "failed to reset NO_REBOOT flag, reboot disabled by hardware".
  233. To compile this driver as a module, choose M here: the
  234. module will be called i8xx_tco.
  235. config SC1200_WDT
  236. tristate "National Semiconductor PC87307/PC97307 (ala SC1200) Watchdog"
  237. depends on WATCHDOG && X86
  238. help
  239. This is a driver for National Semiconductor PC87307/PC97307 hardware
  240. watchdog cards as found on the SC1200. This watchdog is mainly used
  241. for power management purposes and can be used to power down the device
  242. during inactivity periods (includes interrupt activity monitoring).
  243. To compile this driver as a module, choose M here: the
  244. module will be called sc1200wdt.
  245. Most people will say N.
  246. config SCx200_WDT
  247. tristate "National Semiconductor SCx200 Watchdog"
  248. depends on WATCHDOG && SCx200 && PCI
  249. help
  250. Enable the built-in watchdog timer support on the National
  251. Semiconductor SCx200 processors.
  252. If compiled as a module, it will be called scx200_wdt.
  253. config 60XX_WDT
  254. tristate "SBC-60XX Watchdog Timer"
  255. depends on WATCHDOG && X86
  256. help
  257. This driver can be used with the watchdog timer found on some
  258. single board computers, namely the 6010 PII based computer.
  259. It may well work with other cards. It reads port 0x443 to enable
  260. and re-set the watchdog timer, and reads port 0x45 to disable
  261. the watchdog. If you have a card that behave in similar ways,
  262. you can probably make this driver work with your card as well.
  263. You can compile this driver directly into the kernel, or use
  264. it as a module. The module will be called sbc60xxwdt.
  265. config SBC8360_WDT
  266. tristate "SBC8360 Watchdog Timer"
  267. depends on WATCHDOG && X86
  268. ---help---
  269. This is the driver for the hardware watchdog on the SBC8360 Single
  270. Board Computer produced by Axiomtek Co., Ltd. (www.axiomtek.com).
  271. To compile this driver as a module, choose M here: the
  272. module will be called sbc8360.ko.
  273. Most people will say N.
  274. config CPU5_WDT
  275. tristate "SMA CPU5 Watchdog"
  276. depends on WATCHDOG && X86
  277. ---help---
  278. TBD.
  279. To compile this driver as a module, choose M here: the
  280. module will be called cpu5wdt.
  281. config W83627HF_WDT
  282. tristate "W83627HF Watchdog Timer"
  283. depends on WATCHDOG && X86
  284. ---help---
  285. This is the driver for the hardware watchdog on the W83627HF chipset
  286. as used in Advantech PC-9578 and Tyan S2721-533 motherboards
  287. (and likely others). This watchdog simply watches your kernel to
  288. make sure it doesn't freeze, and if it does, it reboots your computer
  289. after a certain amount of time.
  290. To compile this driver as a module, choose M here: the
  291. module will be called w83627hf_wdt.
  292. Most people will say N.
  293. config W83877F_WDT
  294. tristate "W83877F (EMACS) Watchdog Timer"
  295. depends on WATCHDOG && X86
  296. ---help---
  297. This is the driver for the hardware watchdog on the W83877F chipset
  298. as used in EMACS PC-104 motherboards (and likely others). This
  299. watchdog simply watches your kernel to make sure it doesn't freeze,
  300. and if it does, it reboots your computer after a certain amount of
  301. time.
  302. To compile this driver as a module, choose M here: the
  303. module will be called w83877f_wdt.
  304. Most people will say N.
  305. config W83977F_WDT
  306. tristate "W83977F (PCM-5335) Watchdog Timer"
  307. depends on WATCHDOG && X86
  308. ---help---
  309. This is the driver for the hardware watchdog on the W83977F I/O chip
  310. as used in AAEON's PCM-5335 SBC (and likely others). This
  311. watchdog simply watches your kernel to make sure it doesn't freeze,
  312. and if it does, it reboots your computer after a certain amount of
  313. time.
  314. To compile this driver as a module, choose M here: the
  315. module will be called w83977f_wdt.
  316. config MACHZ_WDT
  317. tristate "ZF MachZ Watchdog"
  318. depends on WATCHDOG && X86
  319. ---help---
  320. If you are using a ZF Micro MachZ processor, say Y here, otherwise
  321. N. This is the driver for the watchdog timer builtin on that
  322. processor using ZF-Logic interface. This watchdog simply watches
  323. your kernel to make sure it doesn't freeze, and if it does, it
  324. reboots your computer after a certain amount of time.
  325. To compile this driver as a module, choose M here: the
  326. module will be called machzwd.
  327. config SBC_EPX_C3_WATCHDOG
  328. tristate "Winsystems SBC EPX-C3 watchdog"
  329. depends on WATCHDOG && X86
  330. ---help---
  331. This is the driver for the built-in watchdog timer on the EPX-C3
  332. Single-board computer made by Winsystems, Inc.
  333. *Note*: This hardware watchdog is not probeable and thus there
  334. is no way to know if writing to its IO address will corrupt
  335. your system or have any real effect. The only way to be sure
  336. that this driver does what you want is to make sure you
  337. are runnning it on an EPX-C3 from Winsystems with the watchdog
  338. timer at IO address 0x1ee and 0x1ef. It will write to both those
  339. IO ports. Basically, the assumption is made that if you compile
  340. this driver into your kernel and/or load it as a module, that you
  341. know what you are doing and that you are in fact running on an
  342. EPX-C3 board!
  343. To compile this driver as a module, choose M here: the
  344. module will be called sbc_epx_c3.
  345. # PowerPC Architecture
  346. config 8xx_WDT
  347. tristate "MPC8xx Watchdog Timer"
  348. depends on WATCHDOG && 8xx
  349. config 83xx_WDT
  350. tristate "MPC83xx Watchdog Timer"
  351. depends on WATCHDOG && PPC_83xx
  352. config MV64X60_WDT
  353. tristate "MV64X60 (Marvell Discovery) Watchdog Timer"
  354. depends on WATCHDOG && MV64X60
  355. config BOOKE_WDT
  356. tristate "PowerPC Book-E Watchdog Timer"
  357. depends on WATCHDOG && (BOOKE || 4xx)
  358. ---help---
  359. Please see Documentation/watchdog/watchdog-api.txt for
  360. more information.
  361. # PPC64 Architecture
  362. config WATCHDOG_RTAS
  363. tristate "RTAS watchdog"
  364. depends on WATCHDOG && PPC_RTAS
  365. help
  366. This driver adds watchdog support for the RTAS watchdog.
  367. To compile this driver as a module, choose M here. The module
  368. will be called wdrtas.
  369. # MIPS Architecture
  370. config INDYDOG
  371. tristate "Indy/I2 Hardware Watchdog"
  372. depends on WATCHDOG && SGI_IP22
  373. help
  374. Hardwaredriver for the Indy's/I2's watchdog. This is a
  375. watchdog timer that will reboot the machine after a 60 second
  376. timer expired and no process has written to /dev/watchdog during
  377. that time.
  378. # S390 Architecture
  379. config ZVM_WATCHDOG
  380. tristate "z/VM Watchdog Timer"
  381. depends on WATCHDOG && S390
  382. help
  383. IBM s/390 and zSeries machines running under z/VM 5.1 or later
  384. provide a virtual watchdog timer to their guest that cause a
  385. user define Control Program command to be executed after a
  386. timeout.
  387. To compile this driver as a module, choose M here. The module
  388. will be called vmwatchdog.
  389. # SUPERH Architecture
  390. config SH_WDT
  391. tristate "SuperH Watchdog"
  392. depends on WATCHDOG && SUPERH
  393. help
  394. This driver adds watchdog support for the integrated watchdog in the
  395. SuperH processors. If you have one of these processors and wish
  396. to have watchdog support enabled, say Y, otherwise say N.
  397. As a side note, saying Y here will automatically boost HZ to 1000
  398. so that the timer has a chance to clear the overflow counter. On
  399. slower systems (such as the SH-2 and SH-3) this will likely yield
  400. some performance issues. As such, the WDT should be avoided here
  401. unless it is absolutely necessary.
  402. To compile this driver as a module, choose M here: the
  403. module will be called shwdt.
  404. # SPARC64 Architecture
  405. config WATCHDOG_CP1XXX
  406. tristate "CP1XXX Hardware Watchdog support"
  407. depends on WATCHDOG && SPARC64 && PCI
  408. ---help---
  409. This is the driver for the hardware watchdog timers present on
  410. Sun Microsystems CompactPCI models CP1400 and CP1500.
  411. To compile this driver as a module, choose M here: the
  412. module will be called cpwatchdog.
  413. If you do not have a CompactPCI model CP1400 or CP1500, or
  414. another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
  415. you should say N to this option.
  416. config WATCHDOG_RIO
  417. tristate "RIO Hardware Watchdog support"
  418. depends on WATCHDOG && SPARC64 && PCI
  419. help
  420. Say Y here to support the hardware watchdog capability on Sun RIO
  421. machines. The watchdog timeout period is normally one minute but
  422. can be changed with a boot-time parameter.
  423. #
  424. # ISA-based Watchdog Cards
  425. #
  426. comment "ISA-based Watchdog Cards"
  427. depends on WATCHDOG && ISA
  428. config PCWATCHDOG
  429. tristate "Berkshire Products ISA-PC Watchdog"
  430. depends on WATCHDOG && ISA
  431. ---help---
  432. This is the driver for the Berkshire Products ISA-PC Watchdog card.
  433. This card simply watches your kernel to make sure it doesn't freeze,
  434. and if it does, it reboots your computer after a certain amount of
  435. time. This driver is like the WDT501 driver but for different
  436. hardware. Please read <file:Documentation/watchdog/pcwd-watchdog.txt>. The PC
  437. watchdog cards can be ordered from <http://www.berkprod.com/>.
  438. To compile this driver as a module, choose M here: the
  439. module will be called pcwd.
  440. Most people will say N.
  441. config MIXCOMWD
  442. tristate "Mixcom Watchdog"
  443. depends on WATCHDOG && ISA
  444. ---help---
  445. This is a driver for the Mixcom hardware watchdog cards. This
  446. watchdog simply watches your kernel to make sure it doesn't freeze,
  447. and if it does, it reboots your computer after a certain amount of
  448. time.
  449. To compile this driver as a module, choose M here: the
  450. module will be called mixcomwd.
  451. Most people will say N.
  452. config WDT
  453. tristate "WDT Watchdog timer"
  454. depends on WATCHDOG && ISA
  455. ---help---
  456. If you have a WDT500P or WDT501P watchdog board, say Y here,
  457. otherwise N. It is not possible to probe for this board, which means
  458. that you have to inform the kernel about the IO port and IRQ that
  459. is needed (you can do this via the io and irq parameters)
  460. To compile this driver as a module, choose M here: the
  461. module will be called wdt.
  462. config WDT_501
  463. bool "WDT501 features"
  464. depends on WDT
  465. help
  466. Saying Y here and creating a character special file /dev/temperature
  467. with major number 10 and minor number 131 ("man mknod") will give
  468. you a thermometer inside your computer: reading from
  469. /dev/temperature yields one byte, the temperature in degrees
  470. Fahrenheit. This works only if you have a WDT501P watchdog board
  471. installed.
  472. If you want to enable the Fan Tachometer on the WDT501P, then you
  473. can do this via the tachometer parameter. Only do this if you have a
  474. fan tachometer actually set up.
  475. #
  476. # PCI-based Watchdog Cards
  477. #
  478. comment "PCI-based Watchdog Cards"
  479. depends on WATCHDOG && PCI
  480. config PCIPCWATCHDOG
  481. tristate "Berkshire Products PCI-PC Watchdog"
  482. depends on WATCHDOG && PCI
  483. ---help---
  484. This is the driver for the Berkshire Products PCI-PC Watchdog card.
  485. This card simply watches your kernel to make sure it doesn't freeze,
  486. and if it does, it reboots your computer after a certain amount of
  487. time. The card can also monitor the internal temperature of the PC.
  488. More info is available at <http://www.berkprod.com/pci_pc_watchdog.htm>.
  489. To compile this driver as a module, choose M here: the
  490. module will be called pcwd_pci.
  491. Most people will say N.
  492. config WDTPCI
  493. tristate "PCI-WDT500/501 Watchdog timer"
  494. depends on WATCHDOG && PCI
  495. ---help---
  496. If you have a PCI-WDT500/501 watchdog board, say Y here, otherwise N.
  497. To compile this driver as a module, choose M here: the
  498. module will be called wdt_pci.
  499. config WDT_501_PCI
  500. bool "PCI-WDT501 features"
  501. depends on WDTPCI
  502. help
  503. Saying Y here and creating a character special file /dev/temperature
  504. with major number 10 and minor number 131 ("man mknod") will give
  505. you a thermometer inside your computer: reading from
  506. /dev/temperature yields one byte, the temperature in degrees
  507. Fahrenheit. This works only if you have a PCI-WDT501 watchdog board
  508. installed.
  509. If you want to enable the Fan Tachometer on the PCI-WDT501, then you
  510. can do this via the tachometer parameter. Only do this if you have a
  511. fan tachometer actually set up.
  512. #
  513. # USB-based Watchdog Cards
  514. #
  515. comment "USB-based Watchdog Cards"
  516. depends on WATCHDOG && USB
  517. config USBPCWATCHDOG
  518. tristate "Berkshire Products USB-PC Watchdog"
  519. depends on WATCHDOG && USB
  520. ---help---
  521. This is the driver for the Berkshire Products USB-PC Watchdog card.
  522. This card simply watches your kernel to make sure it doesn't freeze,
  523. and if it does, it reboots your computer after a certain amount of
  524. time. The card can also monitor the internal temperature of the PC.
  525. More info is available at <http://www.berkprod.com/usb_pc_watchdog.htm>.
  526. To compile this driver as a module, choose M here: the
  527. module will be called pcwd_usb.
  528. Most people will say N.
  529. endmenu