Date: Thu, 20 Oct 2005 12:57:30 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-hackers@freebsd.org, alsbergt@cs.huji.ac.il Subject: Re: How to determine link of umass/da devices Message-ID: <20051020105729.GB31913@cicely12.cicely.de> In-Reply-To: <20051019.093808.123396894.imp@bsdimp.com> References: <20051017143356.GA12188@zoopee.org> <20051019.093808.123396894.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 19, 2005 at 09:38:08AM -0600, M. Warner Losh wrote: > In message: <20051017143356.GA12188@zoopee.org> > Tom Alsberg <alsbergt@cs.huji.ac.il> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051020105729.GB31913>