From owner-freebsd-hackers@FreeBSD.ORG Thu Oct 20 10:58:13 2005 Return-Path: X-Original-To: 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 4221016A423 for ; Thu, 20 Oct 2005 10:58:13 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from ant.bwct.de (ant.bwct.de [85.159.14.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7773443D62 for ; Thu, 20 Oct 2005 10:58:12 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by ant.bwct.de (8.12.11/8.12.11) with ESMTP id j9KAvaBb026356; Thu, 20 Oct 2005 12:57:36 +0200 (CEST) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id j9KAvWsD012640 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2005 12:57:33 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id j9KAvWEC031997; Thu, 20 Oct 2005 12:57:32 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id j9KAvUAY031996; Thu, 20 Oct 2005 12:57:30 +0200 (CEST) (envelope-from ticso) Date: Thu, 20 Oct 2005 12:57:30 +0200 From: Bernd Walter To: "M. Warner Losh" Message-ID: <20051020105729.GB31913@cicely12.cicely.de> References: <20051017143356.GA12188@zoopee.org> <20051019.093808.123396894.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051019.093808.123396894.imp@bsdimp.com> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Report: * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on cicely12.cicely.de Cc: freebsd-hackers@freebsd.org, alsbergt@cs.huji.ac.il Subject: Re: How to determine link of umass/da devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2005 10:58:13 -0000 On Wed, Oct 19, 2005 at 09:38:08AM -0600, M. Warner Losh wrote: > In message: <20051017143356.GA12188@zoopee.org> > Tom Alsberg writes: > : With tools like usbdevs and sysctl, I can find out what USB devices > : are connected, and also what USB drivers handle them (so I can see, > : for example, that there is a SanDisk Cruzer Micro connected to port 2 > : in bus 3 and the umass driver under it). > > You can find this out best via the devinfo interface. > > : I can also find out what da devices there are using camcontrol. > > Right. cam doesn't hook the da devices into the device tree. > > : However, how can I find out which da device was assigned to which > : umass/usb device? > > Generally, you can't. There's not really an interface to get this > information. devinfo assumes that things like disk drives would be in > the device tree and except for cam, all other drivers conform to this > world view. There's some efforts to update and lock cam which I think > will rectify this. Not absolutely technicaly correct, but currently one can savely assume that the umass-sim number from camcontrol devlist -v is identic with the umass number from devinfo. This assumption likely won't hold forever. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de