Kconfig 25 KB

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