Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64
- From: Mike Tancsa <mike@xxxxxxxxxx>
- Date: Mon, 12 Dec 2011 15:25:54 -0500
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)
---Mike
--
-------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, mike@xxxxxxxxxx
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada http://www.tancsa.com/
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64
- From: Keith Simonsen
- Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64
- References:
- Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64
- From: Pawel Jakub Dawidek
- Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64
- From: Bjoern A. Zeeb
- Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64
- From: Keith Simonsen
- Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64
- Prev by Date: Re: amd64 packages
- Next by Date: Re: SCHED_ULE should not be the default
- Previous by thread: Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64
- Next by thread: Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64
- Index(es):
Relevant Pages
|