From owner-freebsd-arch@FreeBSD.ORG  Sun Jan  8 22:27:27 2012
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E809C106564A
	for <freebsd-arch@freebsd.org>; Sun,  8 Jan 2012 22:27:27 +0000 (UTC)
	(envelope-from stb@lassitu.de)
Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea])
	by mx1.freebsd.org (Postfix) with ESMTP id A35958FC17
	for <freebsd-arch@freebsd.org>; Sun,  8 Jan 2012 22:27:27 +0000 (UTC)
Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 03F6511AA11;
	Sun,  8 Jan 2012 22:27:25 +0000 (UTC)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Stefan Bethke <stb@lassitu.de>
In-Reply-To: <20120108130039.GG88161@alchemy.franken.de>
Date: Sun, 8 Jan 2012 23:27:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <23477898-8D85-498C-8E30-192810BD68A8@lassitu.de>
References: <8D025847-4BE4-4B2C-87D7-97E72CC9D325@lassitu.de>
	<20120104215930.GM90831@alchemy.franken.de>
	<47ABA638-7E08-4350-A03C-3D4A23BF2D7E@lassitu.de>
	<1763C3FF-1EA0-4DC0-891D-63816EBF4A04@lassitu.de>
	<20120106182756.GA88161@alchemy.franken.de>
	<95372FB3-406F-46C2-8684-4FDB672D9FCF@lassitu.de>
	<20120106214741.GB88161@alchemy.franken.de>
	<F60B2B70-049F-4497-BBA8-3C421088C1EA@lassitu.de>
	<20120108130039.GG88161@alchemy.franken.de>
To: Marius Strobl <marius@alchemy.franken.de>
X-Mailer: Apple Mail (2.1251.1)
Cc: freebsd-arch@freebsd.org
Subject: Re: Extending sys/dev/mii
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
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: Sun, 08 Jan 2012 22:27:28 -0000

Am 08.01.2012 um 14:00 schrieb Marius Strobl:

> Okay, this is the kind of information I was looking for as coupling
> devices with newbus that have no close relation in the hierarchy is
> tedious. However, when not using newbus the question arises how do
> you intend to associate the device_t of say arge0 with the mdiobus0
> hanging off somewhere beneath iicbus0?

In my experimental tree, I've hacked together a small function that =
parses a string for a devclass name and unit number, and looks that up.

I'm also trying a number of other approaches; mainly I'm trying to =
understand how newbus works, and what kind of driver I want at the =
various points, ideally auto-attached, or configured by hints, instead =
of by custom code.  I think I'll need another couple of days to get a =
good enough understanding of drivers, devclasses and their tree, and the =
device tree.


Stefan

--=20
Stefan Bethke <stb@lassitu.de>   Fon +49 151 14070811