From owner-freebsd-hackers@FreeBSD.ORG Wed Aug 6 16:53:06 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 7441637B401 for ; Wed, 6 Aug 2003 16:53:06 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80CF943F93 for ; Wed, 6 Aug 2003 16:53:05 -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 h76Nr0FL037980; Wed, 6 Aug 2003 17:53:00 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 06 Aug 2003 17:52:57 -0600 (MDT) Message-Id: <20030806.175257.106532450.imp@bsdimp.com> To: ticso@cicely.de, ticso@cicely12.cicely.de From: "M. Warner Losh" In-Reply-To: <20030806110013.GE32228@cicely12.cicely.de> References: <20030806104001.GD32228@cicely12.cicely.de> <40470.1060166743@critter.freebsd.dk> <20030806110013.GE32228@cicely12.cicely.de> X-Mailer: Mew version 2.2 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Aug 2003 23:53:06 -0000 In message: <20030806110013.GE32228@cicely12.cicely.de> Bernd Walter 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. Warner