Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64

2011-12-12 Thread Keith Simonsen 



On 12/7/2011 02:17, Bjoern A. Zeeb wrote:

On 7. Dec 2011, at 09:29 , Pawel Jakub Dawidek wrote:


On Tue, Jun 28, 2011 at 03:32:41PM -0700, Xin LI wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

I'd like to request for comments on the attached driver, which supports
watchdogs on several Winbond super I/O chip models and have been tested
on a few of recent Supermicro motherboards.


Is there any reason this is not yet committed? Please commit, pretty
please.


Yes we have 2+ of them and are trying to merge.  The other one sits here
and allows you even longer timeouts as well as time setting the timeout
independent of watchdogd in case you have two watchdogs and want to do tricks
like NMI/reset with the other one... but is lacking the man page yet.
I have added another one or two IC revisions I think that I had found
and tested privately.

http://people.freebsd.org/~bz/patch-20110710-03-wbwd.diff



I've  been using 20110718-02-wbwd.diff for a few months now on a project 
with PC Engines Alix 1.d boards (http://pcengines.ch/alix1d.htm). They 
have a  Winbond W83627HG chip. I don't see any probing/attach messages 
on boot but the driver seems to be properly configuring the chip - if I 
kill watchdogd with -9 the board reboots with watchdog timeout.


I'm also trying to use the above winbond chip for GPIO (userland bit 
banging at this point).



/bz



-Keith
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64

2011-12-12 Thread Keith Simonsen 



On 12/12/2011 12:25, Mike Tancsa wrote:

On 12/12/2011 2:49 PM, Keith Simonsen wrote:


I've  been using 20110718-02-wbwd.diff for a few months now on a project
with PC Engines Alix 1.d boards (http://pcengines.ch/alix1d.htm). They
have a  Winbond W83627HG chip. I don't see any probing/attach messages
on boot but the driver seems to be properly configuring the chip - if I
kill watchdogd with -9 the board reboots with watchdog timeout.


Are you sure thats the watchdog thats doing the 'killing' so to speak ?
If you have
option  CPU_GEODE
in your kernel config, you will get the watchdog code there no ?
( /usr/src/sys/i386/i386/geode.c)


Yes I do have CPU_GEODE in my kernel and I see the geode MFGPT probed in 
the verbose dmesg output. I'm not sure how I can tell what piece of 
hardware /dev/fido is linked to but I think you're correct and I'm using 
the geode watchdog and not the winbond chip. Maybe this has something do 
with me not having 'device eisa' in my kernel config!


I'm going to start compiling a new nanobsd image right now with eisa and 
the newer wbwd.c driver and see how it goes Thanks





---Mike



-Keith

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org