From owner-freebsd-arch@FreeBSD.ORG  Thu Feb 26 12:03:50 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 C275516A4CE
	for <arch@freebsd.org>; Thu, 26 Feb 2004 12:03:50 -0800 (PST)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4C8C743D1D
	for <arch@freebsd.org>; Thu, 26 Feb 2004 12:03:50 -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 i1QK3lkj081561;
	Thu, 26 Feb 2004 13:03:47 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Thu, 26 Feb 2004 13:03:30 -0700 (MST)
Message-Id: <20040226.130330.54448406.imp@bsdimp.com>
To: phk@phk.freebsd.dk
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <2468.1077825069@critter.freebsd.dk>
References: <xzpbrnllnj6.fsf@dwp.des.no>
	<2468.1077825069@critter.freebsd.dk>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: des@des.no
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 20:03:50 -0000

In message: <2468.1077825069@critter.freebsd.dk>
            "Poul-Henning Kamp" <phk@phk.freebsd.dk> writes:
: In message <xzpbrnllnj6.fsf@dwp.des.no>, Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=
:  writes:
: 
: >BTW, the dev tree on my laptop looks like this:
: >
: >des@des ~% sysctl dev
: >dev.nexus0.npx0.%class: npx
: >dev.nexus0.npx0.%desc: math processor
: >dev.nexus0.npx0.%driver: npx
: >dev.nexus0.acpi0.acpi_timer0.%class: acpi_timer
: >dev.nexus0.acpi0.acpi_timer0.%desc: 24-bit timer at 3.579545MHz
: >dev.nexus0.acpi0.acpi_timer0.%driver: acpi_timer
: 
: Just for the record:  Having based this on newbus it only documents
: hardware-anchored device drivers.  I don't know if this is going to
: be a limitation we will have to address or not, but I think you should
: reserve the toplevel name "pseudo" or "sw" or similar as a placeholder
: for non-hardware device drivers, just in case.

There's not really a tree for pseudo devices right now.  They just are
kludged into the system any old way that they can be at the moment.
They aren't part of the hardware device hierarchy.

Warner