From owner-freebsd-acpi@FreeBSD.ORG Wed May 3 14:24:09 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB40916A423; Wed, 3 May 2006 14:24:09 +0000 (UTC) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FB7843D5F; Wed, 3 May 2006 14:24:09 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1FbIGu-00005H-00; Wed, 03 May 2006 16:24:08 +0200 Date: Wed, 3 May 2006 16:24:08 +0200 To: Pav Lucistnik Message-ID: <20060503142408.GD31815@poupinou.org> References: <1146231595.94164.25.camel@pav.hide.vol.cz> <20060502154819.GA16135@poupinou.org> <1146585606.31507.38.camel@pav.hide.vol.cz> <20060503134248.GB31815@poupinou.org> <1146664632.38125.65.camel@pav.hide.vol.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1146664632.38125.65.camel@pav.hide.vol.cz> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-acpi@FreeBSD.org Subject: Re: acpi_thermal on nforce 4 board X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 14:24:10 -0000 On Wed, May 03, 2006 at 03:57:12PM +0200, Pav Lucistnik wrote: ... > No, it just fails to work. And I just tried and it now fails to work on > boards where it used to work. Fishy... > > # mbmon -D -p winbond > Probe Request: winbond > >>> Testing Reg's at ISA-IO <<< > [ISA Port IO-Base:0x290] > Probing Winbond/Asus/LM78/79 chip: ... > CR4C:0x18, CR4D:0x15, CR4E:0x80, CR4F:0x5C ^^ ^^ I'm pretty sure it's a winbond (which one, well I can't tell, but looking at the mother board should tell you which one exactly) and you can access it's register via io port 0x295 -- 0x296. You just have to find the correct tool to handle it, or fix mbmon :) -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.