From owner-freebsd-stable@FreeBSD.ORG  Thu Jan  7 07:48:07 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 15C46106566B
	for <freebsd-stable@freebsd.org>; Thu,  7 Jan 2010 07:48:07 +0000 (UTC)
	(envelope-from lehmann@ans-netz.de)
Received: from avocado.salatschuessel.net (avocado.salatschuessel.net
	[78.111.72.186]) by mx1.freebsd.org (Postfix) with SMTP id 659C68FC1B
	for <freebsd-stable@freebsd.org>; Thu,  7 Jan 2010 07:48:06 +0000 (UTC)
Received: (qmail 59557 invoked by uid 89); 7 Jan 2010 07:48:05 -0000
Message-ID: <20100107074805.59556.qmail@avocado.salatschuessel.net>
References: <20100105192746.cc627795.lehmann@ans-netz.de>
	<20100107063413.614058fc.lehmann@ans-netz.de>
	<20100107063831.GA53300@icarus.home.lan>
In-Reply-To: <20100107063831.GA53300@icarus.home.lan>
From: Oliver Lehmann <lehmann@ans-netz.de>
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
Date: Thu, 07 Jan 2010 08:48:05 +0100
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-stable@freebsd.org
Subject: Re: smb driver for Nvidia ION (intel ATOM) chipset
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2010 07:48:07 -0000

Re: smb driver for Nvidia ION (intel ATOM) chipset writes: 

> It's easy to get confused by the state of hardware monitoring on not
> only FreeBSD but other OSes as well; they all make it sound like
> monitoring things "just magically works with SMBus", and that isn't the

This is what I was thinking so far - yeah exactly ;)
I'v now went deeper into mbmon's source and found that stuff out sorta... 

Looks like I've to do some more research what really is on my board first. 

Using the ISA-IO access method mbmon thinks I've a LM78 and mbmon even 
works but I'm getting false numbers for probably just everything... 

root@nudel xmbmon205> mbmon 

Temp.= 185.0,  0.0,  0.0; Rot.=  835, 30681, 18750
Vcore = 1.10, 1.81; Volt. = 3.39, 4.95,  8.21,  -7.51, -3.24
^C
root@nudel xmbmon205> mbmon -d
SMBus[NVidia nForce2] found, but No HWM available on it!!
Using ISA-IO access method!!
* Nat.Semi.Con. Chip LM78 found.
root@nudel xmbmon205> 


When working with mbmon -S it comes to the conclusion that I have a lm75 
(or maybe it thinks just that because it is the last of the supported HWM 
entries in the HWM_module array) but when probing it in lm75_probe it 
fails... 

        i = set_smb_Extemp(LM75_ADDR_START, LM75_ADDR_END,
                        &smb_wbtemp1, &smb_wbtemp2);
        temp1_flag = i >> 1;
        temp2_flag = i & 0x01; 

        if (temp1_flag && temp2_flag)
                return 0; 

it returns 0 there and this is what probe_HWMChip does not like (it expects 
!= 0). 

I'll go and find some information about what HWM chip is tied on that 
board...