From owner-freebsd-hackers@FreeBSD.ORG  Wed Aug  6 17:37:53 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 479F937B401
	for <freebsd-hackers@freebsd.org>;
	Wed,  6 Aug 2003 17:37:53 -0700 (PDT)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7F6C143FDD
	for <freebsd-hackers@freebsd.org>;
	Wed,  6 Aug 2003 17:37:52 -0700 (PDT)	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.9/8.12.3) with ESMTP id h770bgFL038357;
	Wed, 6 Aug 2003 18:37:42 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Wed, 06 Aug 2003 18:37:10 -0600 (MDT)
Message-Id: <20030806.183710.132444148.imp@bsdimp.com>
To: ticso@cicely.de, ticso@cicely12.cicely.de
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20030807001244.GF35859@cicely12.cicely.de>
References: <20030806110013.GE32228@cicely12.cicely.de>
	<20030806.175257.106532450.imp@bsdimp.com>
	<20030807001244.GF35859@cicely12.cicely.de>
X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-hackers@freebsd.org
cc: phk@phk.freebsd.dk
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: Thu, 07 Aug 2003 00:37:53 -0000

In message: <20030807001244.GF35859@cicely12.cicely.de>
            Bernd Walter <ticso@cicely12.cicely.de> writes:
: On Wed, Aug 06, 2003 at 05:52:57PM -0600, M. Warner Losh wrote:
: > In message: <20030806110013.GE32228@cicely12.cicely.de>
: >             Bernd Walter <ticso@cicely12.cicely.de> writes:
: > : Back to the original question:
: > : How do I get the device_t from nexus?
: > 
: > You don't.  You are assigned one.
: > 
: > : Is there a get_nexus() function somewhere?
: > 
: > No.  You don't need it.
: > 
: > Chances are you could create an identify routine that would attach the
: > bus to.  The identify routine should be all you need.
: 
: The point is that this special CPU can only be identified by its
: host bridge.
: That's the place were the MMCR bus has to be attached to nexus, so
: we need the handle within this function.

Then why not just hang the bus off the host bridge?  There's really no
compelling reason to have it on the nexus.

Warner