From owner-freebsd-arch@FreeBSD.ORG Tue Jul 10 23:41: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 02BAF16A46B; Tue, 10 Jul 2007 23:41:44 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id BD0FA13C448; Tue, 10 Jul 2007 23:41:43 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 401EE476B3; Tue, 10 Jul 2007 19:41:43 -0400 (EDT) Date: Wed, 11 Jul 2007 00:41:43 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp In-Reply-To: <53705.1184107078@critter.freebsd.dk> Message-ID: <20070711003958.V8913@fledge.watson.org> References: <53705.1184107078@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Rui Paulo , Shteryana Shopova , freebsd-arch@FreeBSD.org, "Constantine A. Murenin" 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: Tue, 10 Jul 2007 23:41:44 -0000 On Tue, 10 Jul 2007, Poul-Henning Kamp wrote: > Physical measurements are only relevant in the context of their physical > location and the OpenBSD enumeration doesn't even encode this, it is only > interested in the logical location of the sensor, what kind of bus it is on, > what kind of address it has. > > For any hw-sensor namespace to make sense, it must, as a minimum, identify > the sensors in terms of the device(-drivers) associated with the hardware > where the sensor senses, not the device-driver of the sensor itself. > > The OpenBSD stuff is a 1980 style hack, and should not be propagated. This argument would be more convincing if accompanied by a concrete example, fabricated or otherwise. Are you suggesting, for example, adding newbus sensor methods associated with existing driver attachments? Robert N M Watson Computer Laboratory University of Cambridge