From owner-freebsd-arch@FreeBSD.ORG  Thu Feb 26 12:39:26 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 1D93B16A4D0
	for <arch@freebsd.org>; Thu, 26 Feb 2004 12:39:26 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 640C043D31
	for <arch@freebsd.org>; Thu, 26 Feb 2004 12:39:25 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i1QKdMfH003063;
	Thu, 26 Feb 2004 21:39:22 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: "M. Warner Losh" <imp@bsdimp.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 26 Feb 2004 13:03:30 MST."
             <20040226.130330.54448406.imp@bsdimp.com> 
Date: Thu, 26 Feb 2004 21:39:22 +0100
Message-ID: <3062.1077827962@critter.freebsd.dk>
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:39:26 -0000

In message <20040226.130330.54448406.imp@bsdimp.com>, "M. Warner Losh" writes:

>: 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.

As long as we agree that this is for hardware only and limited to
that, then I have no problems.

I still think it prudent to nail down "pseudo" or "sw" or something
should we change our mind.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.