[Libdlo] Just got a Cables Unlimited usb-av2010 to test

[akephart at akephart.org]

First, get the usb pid/vid values (XXXX:YYYY) for the target device with
'lsusb'.  Then, list the full descriptor set with 'lsusb -v -d
XXXX:YYYY'.  In the listing, you'll see one or more interface
descriptors, and each of those will have a value for bInterfaceClass. 
That value will tell you what usb class the particular interface
supports, if any.  There is also a device class indication in the device
descriptor, but it will usually be set to a value that isn't directly
useful (e.g. defined at interface level or miscellaneous device, that
kind of thing).
 
If it's a spec-compliant HWA, it'll have bInterfaceClass=E0h (wireless
controller) and bInterfaceSubclass=02h (WUSB wire adapter).
 
It may also be defined as some kind of firmware download device (DFU or
similar), and sit expectantly for an intermediate driver to download the
firmware, which will then require the HWA driver.
 
It may also be completely vendor-specific, in which case all bets are
off.
 
-andrew
 
 
 


On April 6, 2011 at 9:36 AM Chris Hill <hill101 at gmail.com> wrote:


> How would I do this?
> 
> On Wed, Apr 6, 2011 at 9:34 AM, akephart at akephart.org
> [mailto:akephart at akephart.org] <akephart at akephart.org
> [mailto:akephart at akephart.org] >wrote:
> 
> > Most of these wireless USB adapters (WUSB that is, not WiFi from a
> > USB
> > adapter) treat the host dongle as a host wire adapter (HWA) device,
> > which requires its own driver, that then tunnels to and from the
> > downstream device.  I don't know that that is the case here, but you
> > should be able to tell from the device and config descriptors.
> >  
> > -andrew 

> 
> --
> <a href="http://www.finalescape.com/home.php?refcode=AgKF5C">Join
> FinalEscape!</a> 
> 
> For those of you who like text adventuring with a touch of cyberpunk.
>