From owner-freebsd-acpi@FreeBSD.ORG Thu May 4 11:46:29 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 92C9016A404 for ; Thu, 4 May 2006 11:46:29 +0000 (UTC) (envelope-from pav@FreeBSD.org) Received: from e0-a11.b1.lan.prg.vol.cz (e0-a11.b1.lan.prg.vol.cz [195.122.204.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id D30FB43D48 for ; Thu, 4 May 2006 11:46:28 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from pav.hide.vol.cz (localhost [127.0.0.1]) by e0-a11.b1.lan.prg.vol.cz (8.13.6/8.13.6) with ESMTP id k44BkPXU053362; Thu, 4 May 2006 13:46:25 +0200 (CEST) (envelope-from pav@FreeBSD.org) Received: (from pav@localhost) by pav.hide.vol.cz (8.13.6/8.13.6/Submit) id k44BkPV5053361; Thu, 4 May 2006 13:46:25 +0200 (CEST) (envelope-from pav@FreeBSD.org) X-Authentication-Warning: pav.hide.vol.cz: pav set sender to pav@FreeBSD.org using -f From: Pav Lucistnik To: Alex Zbyslaw In-Reply-To: <4459D55D.1050202@dial.pipex.com> References: <20060503180559.863EC45042@ptavv.es.net> <1146694389.7471.12.camel@ikaros.oook.cz> <4459D55D.1050202@dial.pipex.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-F+VpdpZOV3rKUc6gdzsg" Date: Thu, 04 May 2006 13:46:24 +0200 Message-Id: <1146743184.18447.8.camel@pav.hide.vol.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port 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 Reply-To: pav@FreeBSD.org 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 11:46:29 -0000 --=-F+VpdpZOV3rKUc6gdzsg Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Alex Zbyslaw p=C3=AD=C5=A1e v =C4=8Dt 04. 05. 2006 v 11:20 +0100: > Pav Lucistnik wrote: >=20 > >Kevin Oberman p=C3=AD=C2=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 :-)) Actually, the patch is already part of the port. As for sending the patch to the mbmon author, I doubt it would make any difference, as the mbmon wasn't updated in 3 years. --=20 Pav Lucistnik An arrow (+0,+0) {@f0} finds a mark. It dies. --=-F+VpdpZOV3rKUc6gdzsg Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEWemQntdYP8FOsoIRAp9QAJ9+/G7VYs5dnXlPp/MqjUB9GDsrkwCgyCnI 8iP8jREbhkAPWZkoxwUM4xY= =xnwo -----END PGP SIGNATURE----- --=-F+VpdpZOV3rKUc6gdzsg--