From owner-freebsd-current@FreeBSD.ORG Tue Dec 13 00:00:41 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 39AFA10656AA for ; Tue, 13 Dec 2011 00:00:41 +0000 (UTC) (envelope-from bangel@elite.net) Received: from mail.elite.net (svr08.atwtca02.fire2wire.net [67.118.192.24]) by mx1.freebsd.org (Postfix) with ESMTP id 396AA8FC1E for ; Tue, 13 Dec 2011 00:00:29 +0000 (UTC) Received: from adsl-99-110-156-21.dsl.irvnca.sbcglobal.net ([99.110.156.21] helo=[192.168.123.220]) by mail.elite.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1RaFnI-000123-1E; Mon, 12 Dec 2011 16:00:28 -0800 Message-ID: <4EE695DD.1000206@elite.net> Date: Mon, 12 Dec 2011 16:01:33 -0800 From: Keith Simonsen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Mike Tancsa References: <4E0A5689.2020302@delphij.net> <20111207092907.GA1645@garage.freebsd.pl> <7BD6CA15-3329-4684-8127-665CDC171B22@lists.zabbadoz.net> <4EE65AB4.1010405@elite.net> <4EE66352.8090801@sentex.net> In-Reply-To: <4EE66352.8090801@sentex.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Tue, 13 Dec 2011 00:00:41 -0000 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