From owner-freebsd-hackers@FreeBSD.ORG  Fri Aug  8 00:44:40 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8BA3937B401; Fri,  8 Aug 2003 00:44:40 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 660AA43F75; Fri,  8 Aug 2003 00:44:39 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h787i81f006422;
	Fri, 8 Aug 2003 09:44:09 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: John Birrell <jb@cimlogic.com.au>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 08 Aug 2003 08:36:17 +1000."
             <20030808083617.E7321@freebsd1.cimlogic.com.au> 
Date: Fri, 08 Aug 2003 09:44:08 +0200
Message-ID: <6421.1060328648@critter.freebsd.dk>
cc: ticso@cicely12.cicely.de
cc: freebsd-hackers@freebsd.org
cc: ticso@cicely.de
Subject: Re: How to get a device_t 
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Aug 2003 07:44:40 -0000

In message <20030808083617.E7321@freebsd1.cimlogic.com.au>, John Birrell writes
:

>I'm not convinced that any hacking is required other than passing the
>device_t parent to nexus_pcib_is_host_bridge (in STABLE) as Bernd says.
>I traced the boot on my system and the MMCR is initialised early (when
>the Timecounter "ELAN" output occurs). Immediately following that
>initialisation, 'pcib' is added as a child of 'nexus'. I don't see why
>'mmcr' couldn't be added as a child of 'nexus' too. At this point,
>nexus isn't walking through it's children so there shouldn't be a problem.
>Then the ELAN specific devices (like GPIO and flash) can attach to 'mmcr'.
>
>This seems straight forward. Maybe I'm missing something. 8-)

That's my take too.  And MMCR belongs on nexus not on legacy from an
architectural point of view.

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