From owner-freebsd-arch@FreeBSD.ORG  Thu Feb 26 10:21:27 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D2CD516A4CE
	for <arch@freebsd.org>; Thu, 26 Feb 2004 10:21:27 -0800 (PST)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5EF8243D1F
	for <arch@freebsd.org>; Thu, 26 Feb 2004 10:21:27 -0800 (PST)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.10/8.12.9) with ESMTP id i1QILMkj080040;
	Thu, 26 Feb 2004 11:21:23 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Thu, 26 Feb 2004 11:20:45 -0700 (MST)
Message-Id: <20040226.112045.82374099.imp@bsdimp.com>
To: des@des.no
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <xzpk729lnq7.fsf@dwp.des.no>
References: <xzpk729lnq7.fsf@dwp.des.no>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
cc: arch@freebsd.org
Subject: Re: per-device sysctls
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Feb 2004 18:21:28 -0000

In message: <xzpk729lnq7.fsf@dwp.des.no>
            des@des.no (Dag-Erling Sm=F8rgrav) writes:
: The first of the attached patches creates a sysctl context and node
: for every device in the system named for its nameunit.  Each device's=

: sysctl node is a child of the parent device's sysctl node, so the
: resulting sysctl tree resembles the "show devices by attachment" mode=

: of Windows's device manager.  Standard entries in each device's tree
: include %class, %desc and %driver (device class, device description
: and driver name).  I also plan to add entries for device IDs, irq /
: drq lines etc., but this will require additional bus-specific code an=
d
: is not yet implemented.

How is this different than the sysctl stuff that already exsists for
this and is accessed by devinfo?

Warner