thanks for replying.
At 12:24 30.09.2003 +0200, Eric Spakman wrote:
Hello Erich,
I took a look at the driver source, but it looks like it also need a /dev/wd entry to function.
Where did you take the driver from, I posted the new driver at the end of my development cycle. Unless you took it from my CVS you may not have the latest.
Looking at the Bering watchdog source (which is a very basic implementation looking only at /dev/watchdog) I don't see how this can work.
Look where /dev/watchdog points to:
# ls -l /dev/watchdog crw-rw---- 1 root root 10, 130 Sep 30 07:22 /dev/watchdog
Driver are typically accessed by their major/minor number.
This is the major/minor assigned to watchdogs, wherever they are from and whatever they do. So we can easily use wd1100.
I also think that loading a driver in /etc/init.d/watchdog is not the right place to do it. Modules should be load in /etc/modules.
You may be right here, however the watchdog program needs something to play with, so either softdog or another watchdog should be loaded.
Do you also need to set some /proc entries? Can they be set without interfering the normal softdog driver? Or is this something that should be placed in the documentation?
The /proc entries are built by the wd1100 driver on the fly.
I requested that the documentation be updated to reflect the gxb=0xnnnn parameter support, else, at least with the current bios on the wrap board it is not even needed. The file contents in the /proc filesystem could need some docs, however, he who wants to play with that better read the driver source anyway.
regards Erich
THINK Püntenstrasse 39 8143 Stallikon mailto:[EMAIL PROTECTED] PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf
_______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
