I have a user-space daemon for driving the watchdog. I see it uses the
same user-space interface as sbc60xxwdt.c, except it can't be disabled :)
Did you write one too ?
Should we find somewhere to actually publish these watchdog-daemons ?
Or have I completely missed that there already is a place for these
daemons, and that there already exist publicly available daemons for
driving the sbc60xxwdt and ZFmicro ?
Btw. Alan, the documentation somehow got lost to the sbc60xxwdc driver
when you so kindly converted it to 2.4 - it's here below :)
-- ................................................................ : jakob@unthought.net : And I see the elder races, : :.........................: putrid forms of man : : Jakob Østergaard : See him rise and claim the earth, : : OZ9ABN : his downfall is at hand. : :.........................:............{Konkhra}...............:
diff -Nru linux/Documentation/Configure.help linux.loaded/Documentation/Configure.help --- linux/Documentation/Configure.help Wed Apr 26 20:03:13 2000 +++ linux.loaded/Documentation/Configure.help Wed Apr 26 19:31:41 2000 @@ -9371,6 +9371,18 @@ module, say M here and read Documentation/modules.txt. Most people will say N. +SBC-60XX Watchdog Timer +CONFIG_60XX_WDT + This driver can be used with the watchdog timer found on some + single board computers, namely the 6010 PII based computer. + It may well work with other cards. It reads port 0x443 to enable + and re-set the watchdog timer, and reads port 0x45 to disable + the watchdog. If you have a card that behave in similar ways, + you can probably make this driver work with your card as well. + + You can compile this driver directly into the kernel, or use + it as a module. The module will be called sbc60xxwdt.o. + Enhanced Real Time Clock Support CONFIG_RTC If you say Y here and create a character special file /dev/rtc with - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/