Date: Tue, 22 Feb 2011 13:31:25 -0800 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Raoul <rmgls@free.fr> Subject: Re: Dell 370 bluetooth minicard Message-ID: <AANLkTi=1makgRcLwY5RS6AANMfMDvYODp2QY5qX-KA9G@mail.gmail.com> In-Reply-To: <20110222211252.12195A6338@smtp3-g21.free.fr> References: <20110222211252.12195A6338@smtp3-g21.free.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 22, 2011 at 1:12 PM, Raoul <rmgls@free.fr> wrote: > > Hi Maksim, > > i have some more informations now. > > 1. right, the modem is behind the hub in the BCM2046B1. > its vendor id is 413C: DELL. > his product id is 8156. > > 2. usbconfig do not see it at all why? could you please provide device descriptor as i asked? if you have ugen(4) device attached, then usbconfig(8) should be able to see it and extract information from it. > There is no switch to put it on/off. it is always on. thanks -- its good to know. > here is the true configuration obtained from debian: > for documentation i keep other divices. thanks, but this is not very much help. i'd like to know what freebsd thinks about this device and not linux. > Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor > Bus 002 Device 005: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card > Bus 002 Device 004: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick > Bus 002 Device 003: ID 413c:8157 Dell Computer Corp. Integrated Keyboard > Bus 002 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) i _think_ that device that freebsd sees as ugen(4) is the "ID 0a5c:4500" device. notice that "missing devices" are on the same usb bus (bus 002) with the increasing id's. i guess this means that "missing devices" are behind the hub. we already know that interface class is reported by the device as "hub". what i'd like to know is what device class is set to. freebsd uhub(4) driver uses device class to identify device as usb hub. obviously, if freebsd does not recognize device as usb hub it is not going to "explore" and find all the devices that might be attached to the usb hub. quick look at linux's usb hub driver suggest that linux might be using interface class to identify device as usb hub. to test the theory, quick hack would be to change uhub_probe() in /sys/dev/usb/usb_hub.c and forcefully make uhub(4) attach to device/vendor id 0a5c:4500. thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=1makgRcLwY5RS6AANMfMDvYODp2QY5qX-KA9G>