Kconfig 24 KB

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