Kconfig 25 KB

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