[RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64
Bjoern A. Zeeb
bzeeb-lists at lists.zabbadoz.net
Tue Dec 13 13:18:59 UTC 2011
On 13. Dec 2011, at 00:01 , Keith Simonsen wrote:
> 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
You probably don't need eisa but if using my variant make sure you have the
hint enabled or the hints file installed/updated to include it.
You should see the debug sysctls for the watchdog or it did not attach and
is not used.
Bjoern A. Zeeb You have to have visions!
Stop bit received. Insert coin for new address family.
More information about the freebsd-current