Date: Wed, 06 Aug 2003 18:37:10 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: ticso@cicely.de, ticso@cicely12.cicely.de Cc: phk@phk.freebsd.dk Subject: Re: How to get a device_t Message-ID: <20030806.183710.132444148.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030806.183710.132444148.imp>