From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 6 04:26:55 2003 Return-Path: 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 9EC8737B401 for ; Wed, 6 Aug 2003 04:26:55 -0700 (PDT) Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.86.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id A94A943F85 for ; Wed, 6 Aug 2003 04:26:54 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by phk.freebsd.dk (8.12.8/8.12.8) with ESMTP id h76BQmV3029888; Wed, 6 Aug 2003 11:26:48 GMT (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 h76BQlPI040819; Wed, 6 Aug 2003 13:26:47 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: ticso@cicely.de From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 06 Aug 2003 13:00:13 +0200." <20030806110013.GE32228@cicely12.cicely.de> Date: Wed, 06 Aug 2003 13:26:47 +0200 Message-ID: <40818.1060169207@critter.freebsd.dk> cc: freebsd-hackers@freebsd.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Aug 2003 11:26:55 -0000 In message <20030806110013.GE32228@cicely12.cicely.de>, Bernd Walter writes: >On Wed, Aug 06, 2003 at 12:45:43PM +0200, Poul-Henning Kamp wrote: >> In message <20030806104001.GD32228@cicely12.cicely.de>, Bernd Walter writes: >> >On Wed, Aug 06, 2003 at 12:18:28PM +0200, Poul-Henning Kamp wrote: >> >> In message <20030806101148.GC32228@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@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.