Messages in this thread | | | Date | Wed, 6 Sep 2006 21:41:49 +0200 | From | Wim Van Sebroeck <> | Subject | Re: [PATCH] watchdog: add support for w83697hg chip |
| |
Hi All,
> | So in the case the BIOS sets the watchdog to 4 mins > | for example the 2 drivers are a little different. > | > | W83627HF resets to timeout seconds on module load > | W83697HG resets to timeout seconds on /dev/watchdog open > > Yes, I'm reluctant at changing anything set by the BIOS before the first > *use* of the module. In particular, if the watchdog was not activated by > default in the BIOS, I'd prefer the box not to reboot just because the > module was loaded (maybe by mistake) if no daemon open /dev/watchdog > at least once.
My feedback: it is important that during the initialization of the module, the watchdog is being disabled. A watchdog should only start working after it has been started via /dev/watchdog.
> In particular, some boxes may take a long time to boot, e.g. if fscks are > needed; if the module is loaded by an initrd before filesystems are mounted > and fscks are done, if I'm not mistaken the box could reboot in loop > every time in the middle of fscks.
Please note that I added 4 days ago a patch of Marcus Junker <junker@anduras.de> in my linux-2.6-watchdog-mm tree for the w83697hf chipset. See: http://www.kernel.org/git/?p=linux/kernel/git/wim/linux-2.6-watchdog-mm.git;a=commitdiff;h=d19ea38e6e99c4924c894cb54440e242179bf27d;hp=19cdb014d58f2c47470d86188a7e556380469008
Greetings, Wim.
- 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/
| |