How to get a device_t

[Poul-Henning Kamp]

In message <20030806110013.GE32228 at cicely12.cicely.de>, Bernd Walter writes:
>On Wed, Aug 06, 2003 at 12:45:43PM +0200, Poul-Henning Kamp wrote:
>> In message <20030806104001.GD32228 at cicely12.cicely.de>, Bernd Walter writes:
>> >On Wed, Aug 06, 2003 at 12:18:28PM +0200, Poul-Henning Kamp wrote:
>> >> In message <20030806101148.GC32228 at cicely12.cicely.de>, Bernd Walter writes:
>> >> >>From the logicaly standpoint the extensions had to be attached to
>> >> >nexus, but nowhere is the current code path there is a handle for
>> >> >nexus or any other device_t.
>> >> 
>> >> In fact what you may want to do is hang the entire MMCR off the nexus
>> >> as a bus, and hang the various drivers off that bus.
>> >
>> >What needs to be in *_probe() to conditionalize on elan existence?
>> 
>> Well, my idea was to hang the mmcr bus on nexus when we find out it
>> is an elan.
>
>Back to the original question:
>How do I get the device_t from nexus?
>Is there a get_nexus() function somewhere?

That's were I don't know enough newbus :-)

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at 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.