From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031301AbXDQXuf (ORCPT ); Tue, 17 Apr 2007 19:50:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1031304AbXDQXuf (ORCPT ); Tue, 17 Apr 2007 19:50:35 -0400 Received: from nz-out-0506.google.com ([64.233.162.230]:11584 "EHLO nz-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031303AbXDQXue (ORCPT ); Tue, 17 Apr 2007 19:50:34 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gvv77k7V+NR9GRva7DdLGAx/qLivZbCRvb9xiQo9uFhPgd1Itk9W8t22x4vdM/SW2tzdLnpFrhuxvpi41xnjULqs0z/ZPAmKpiZmnYRBChR6y0uFQjYRpmURDE8NwU4uLwhr3oN3BeHfVnvbNwrjPtaBPDdC21Ro81hpKfXUkbM= Message-ID: <68676e00704171650t604e30f4j3749b7c5a8ddc5c5@mail.gmail.com> Date: Wed, 18 Apr 2007 01:50:29 +0200 From: "Luca Tettamanti" To: "Bjorn Helgaas" Subject: Re: [lm-sensors] Could the k8temp driver be interfering with ACPI? Cc: "Jean Delvare" , "Pavel Machek" , linux-kernel , lm-sensors@lm-sensors.org, linux-acpi@vger.kernel.org, "Chuck Ebbert" In-Reply-To: <200704161628.47707.bjorn.helgaas@hp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45D5EA88.7090300@redhat.com> <200704151857.03115.bjorn.helgaas@hp.com> <20070416211411.GA16150@dreamland.darkstar.lan> <200704161628.47707.bjorn.helgaas@hp.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 4/17/07, Bjorn Helgaas wrote: > On Monday 16 April 2007 15:14, Luca Tettamanti wrote: > > Problem is that ACPI methods are not documented at all (how am I > > supposed to know that "G6T6" is the reading of the 12V rail?) while the > > datasheet of hw monitoring chips (w83627ehf in my case) are public (more > > or less). > > Yes, I see that it's attractive to use a single w83627ehf.c driver. > For an ACPI driver, we'd have to build a list of PNP IDs, and possibly > information about which methods read which information. That's > certainly more work. > > On the other hand, the ACPI driver would avoid the synchronization > issues that started this whole thread. That's a pretty compelling > advantage. > > > Furthermore, sensor driver exposes all the reading of the chip > > (e.g. in the DSDT I can't find the VSB or battery voltage). > > Maybe Asus didn't hook up those readings on the board. I would > guess that PC Probe doesn't expose the VSB or battery voltage either. PC Probe does not. But the lines are wired and the readings (from Linux) are sensible. > I'm sure you've seen these: > http://lists.lm-sensors.org/pipermail/lm-sensors/2005-October/014050.html > http://www.lm-sensors.org/wiki/AsusFormulaHacking Actually I haven't, I've happily ignored ACPI until now ;-) My DSDT doesn't look too bad, I may give it a try... Luca