From owner-freebsd-acpi@FreeBSD.ORG Thu May 4 10:20:16 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 8012C16A402; Thu, 4 May 2006 10:20:16 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DB9343D45; Thu, 4 May 2006 10:20:15 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.144] (helo=anti-virus03-07) by smtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1FbawQ-0003No-8P; Thu, 04 May 2006 11:20:14 +0100 Received: from [80.192.58.117] (helo=[192.168.0.2]) by asmtp-out1.blueyonder.co.uk with esmtp (Exim 4.52) id 1FbawP-0002W2-Oi; Thu, 04 May 2006 11:20:13 +0100 Message-ID: <4459D55D.1050202@dial.pipex.com> Date: Thu, 04 May 2006 11:20:13 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: pav@FreeBSD.org References: <20060503180559.863EC45042@ptavv.es.net> <1146694389.7471.12.camel@ikaros.oook.cz> In-Reply-To: <1146694389.7471.12.camel@ikaros.oook.cz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable 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: Thu, 04 May 2006 10:20:16 -0000 Pav Lucistnik wrote: >Kevin Oberman p=ED=B9e v st 03. 05. 2006 v 11:05 -0700: > > =20 > >>Now, why does my mbmon work out of the box and you need a small patch? >> =20 >> > >I guess because they used some fancy new variation of the chip. > >And now we're really off topic :) > > =20 > One more small suggestion. Should you send your patch to the creators=20 of mbmon? Or to the port maintainer? Or perhaps file a PR? I'm never=20 sure of the right way to do this, but if you have a new chip revision=20 you can bet others will too. (For all know, my MB with a winbond chip=20 that won't run mbmon has the new revision :-)) Best, --Alex