Kconfig 24 KB

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