Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Dec 2011 15:25:54 -0500
From:      Mike Tancsa <mike@sentex.net>
To:        Keith Simonsen <bangel@elite.net>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64
Message-ID:  <4EE66352.8090801@sentex.net>
In-Reply-To: <4EE65AB4.1010405@elite.net>
References:  <4E0A5689.2020302@delphij.net>	<20111207092907.GA1645@garage.freebsd.pl>	<7BD6CA15-3329-4684-8127-665CDC171B22@lists.zabbadoz.net> <4EE65AB4.1010405@elite.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EE66352.8090801>