From owner-freebsd-arch@FreeBSD.ORG  Thu Feb 26 12:41:43 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 2FBC416A4CE
	for <arch@freebsd.org>; Thu, 26 Feb 2004 12:41:43 -0800 (PST)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AB79343D2F
	for <arch@freebsd.org>; Thu, 26 Feb 2004 12:41:42 -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 i1QKfdkj082140;
	Thu, 26 Feb 2004 13:41:39 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Thu, 26 Feb 2004 13:41:20 -0700 (MST)
Message-Id: <20040226.134120.71093962.imp@bsdimp.com>
To: phk@phk.freebsd.dk
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <3045.1077827869@critter.freebsd.dk>
References: <20040226.125904.08946359.imp@bsdimp.com>
	<3045.1077827869@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=iso-8859-1
Content-Transfer-Encoding: quoted-printable
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:41:43 -0000

In message: <3045.1077827869@critter.freebsd.dk>
            "Poul-Henning Kamp" <phk@phk.freebsd.dk> writes:
: In message <20040226.125904.08946359.imp@bsdimp.com>, "M. Warner Losh=
" writes:
: >In message: <xzp8yipk4gh.fsf@dwp.des.no>
: >            des@des.no (Dag-Erling Sm=F8rgrav) writes:
: >: "Poul-Henning Kamp" <phk@phk.freebsd.dk> writes:
: >: > Dag-Erling =3D?iso-8859-1?q?Sm=3DF8rgrav?=3D writes:
: >: > > "M. Warner Losh" <imp@bsdimp.com> writes:
: >: > > > That is a good reason to transitioning to this, so long as w=
e can come
: >: > > > up with a good way to represent detached nodes.
: >: > > As long as they have a device_t, it should be a piece of cake.=

: >: > Having a device_t is a property of having hardware, not of being=
 a
: >: > device driver.
: >: =

: >: I believe that by "detached nodes", Warner means hardware that doe=
s
: >: not have a driver.
: >
: >They have a device_t, however.  All nodes in the tree have a device_=
t
: >(kind of by definition). Not all nodes in the tree have a devclass
: >associated with their device_t (eg, not all devices are attached).
: >this is why you'll see lots of 'unknown' nodes in the devinfo output=
.=

: =

: GEOM, NETGRAPH pty, tun, tap, nmdm and similar have no newbus
: infestation and there would have to really good reasons to infest the=
m.

If they want to use this mechanism, they need to use the mechanism.
I'm cool with them not using this mechanism, but I don't think we
should kludge it to allow for them to use it.  That's what I'm
saying...  This is a newbus only mechanism and let's not get bogged
down in accomidatnig non-newbus things until we have the newbus parts
of it working.

Warner