From owner-freebsd-current@FreeBSD.ORG Mon Dec 12 20:26:09 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 940971065700 for ; Mon, 12 Dec 2011 20:26:09 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 561AE8FC12 for ; Mon, 12 Dec 2011 20:26:09 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.5/8.14.4) with ESMTP id pBCKQ3NY041993; Mon, 12 Dec 2011 15:26:03 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <4EE66352.8090801@sentex.net> Date: Mon, 12 Dec 2011 15:25:54 -0500 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Keith Simonsen References: <4E0A5689.2020302@delphij.net> <20111207092907.GA1645@garage.freebsd.pl> <7BD6CA15-3329-4684-8127-665CDC171B22@lists.zabbadoz.net> <4EE65AB4.1010405@elite.net> In-Reply-To: <4EE65AB4.1010405@elite.net> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.71 on IPv6:2607:f3e0:0:1::12 Cc: FreeBSD Current Subject: Re: [RFC] winbond watchdog driver for FreeBSD/i386 and FreeBSD/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2011 20:26:09 -0000 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/