From owner-freebsd-drivers@FreeBSD.ORG Tue Apr 6 14:03:31 2010 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65AD6106566C; Tue, 6 Apr 2010 14:03:31 +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 116688FC1D; Tue, 6 Apr 2010 14:03:30 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o36Dlaiw010793; Tue, 6 Apr 2010 07:47:37 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 06 Apr 2010 07:43:13 -0600 (MDT) Message-Id: <20100406.074313.364718154403381345.imp@bsdimp.com> To: rpaulo@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <20100405055947.GA3544@hita.home.const.name> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, freebsd-hardware@freebsd.org, freebsd-drivers@freebsd.org, cnst@freebsd.org Subject: Re: aibs(4): ASUSTeK AI Booster (ACPI ATK0110) Hardware Monitor X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Apr 2010 14:03:31 -0000 In message: Rui Paulo writes: : Hi, : : On 5 Apr 2010, at 06:59, Constantine A. Murenin wrote: : : > Dear freebsd-{acpi,drivers,hardware}@, : > : > Attached patch provides support for the hardware monitoring capabilities that are present in many modern desktop motherboards from ASUS featuring the ATK0110 ACPI device. : > : > This driver, aibs(4), is a fresh replacement for FreeBSD's existing acpi_aiboost(4). The new aibs(4) driver has the following advantages when compared to the old acpi_aiboost(4): : > * the sensors are now provided through the user-serviceable hw.acpi.aibs0 tree (with a subtree for each sensor type), instead of the Newbus-internal dev.acpi_aiboost.0 tree that contains various nonprime data at the same level as the actual sensors : : I was under the impression that this the right way in FreeBSD. To be clear, this is a regression. They should be through the dev tree. We've been migrating exposed functionality from the hw. tree to the dev. tree for quite some time now. hw. isn't any more user-serviceable than dev. is. Warner