From owner-freebsd-arch@FreeBSD.ORG Wed Jul 11 02:59:44 2007 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0CB3316A421; Wed, 11 Jul 2007 02:59:44 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id BB9FF13C457; Wed, 11 Jul 2007 02:59:43 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l6B2vpLq021388; Tue, 10 Jul 2007 20:57:52 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 10 Jul 2007 20:57:51 -0600 (MDT) Message-Id: <20070710.205751.-1962670861.imp@bsdimp.com> To: ambrisko@ambrisko.com From: "M. Warner Losh" In-Reply-To: <200707101833.l6AIX0xl049962@ambrisko.com> References: <20070708081511.GX1221@funkthat.com> <200707101833.l6AIX0xl049962@ambrisko.com> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 10 Jul 2007 20:57:57 -0600 (MDT) Cc: rpaulo@fnop.net, gurney_j@resnet.uoregon.edu, andre@freebsd.org, perforce@freebsd.org, cnst@freebsd.org, syrinx@freebsd.org, freebsd-arch@freebsd.org Subject: Re: Porting OpenBSD's sysctl hw.sensors framework to FreeBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2007 02:59:44 -0000 In message: <200707101833.l6AIX0xl049962@ambrisko.com> Doug Ambrisko writes: : John-Mark Gurney writes: : | Constantine A. Murenin wrote this message on Sat, Jul 07, 2007 at 21:43 -0400: : | > Hardware sensors tree is going to be pretty deep down. Under sysctl(8) : | > the variable names will look like this: : | > : | > hw.sensors.lm0.temp0 : | > : | > whereas in reality, the tree has five levels: : | > : | > hw.sensors.lm0.temp.0 : | : | I'm curious, why do we want/need these in the kernel as opposed to a : | userland library/utility to provide this info? : : I agree. There are so many different flavours of HW monitoring chips : and several tools that can read them live in ports. Lots of them are : slightly different, intefaces can be i2c or direct I/O. We are already : somewhat battling with the various ways IPMI controllers can be attached : to the system. Now in the case of IPMI there is a good win in providing : a device driver interface for the HW and user land tools to get info. : out of them. I don't see a win with this in the various HW monitoring : chips. My big concern is the 'automatic' probing. It doesn't mix well with i2c eeprom chips :-( Warner