Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Dec 2004 02:20:10 +0100 (CET)
From:      Barry Bouwsma <freebsd-misuser@remove-NOSPAM-to-reply.NOSPAM.dyndns.dk>
To:        freebsd-usb@freebsd.org
Subject:   Re: fingerprints
Message-ID:  <200412270120.iBR1K9o07904@Mail.NOSPAM.DynDNS.dK>
References:  <20041224010759.N1763@april.chuckr.org> <200412241756.56900.doconnor@gsoft.com.au> <200412242250.iBOMot433057@Mail.NOSPAM.DynDNS.dK> <20041226160637.H54135@april.chuckr.org> <20041226205543.GA76551@cicely12.cicely.de>

next in thread | previous in thread | raw e-mail | index | archive | help
> > Bernd Walter (ticso) has a ports skeleton for the NetBSD USB utilities
> 
> I didn't see any extra email postings on this, I hope it doesn't just
> disappear.  Can I ask one favor?  I would VERY much appreciate it if you
> would pick a single one of the usb devices, and I will read everything I

Erm, if I understand you right, how about a D-Link DU-128+ TA?
Here are some hints:
bLength=18 bDescriptorType=1 bcdUSB=1.10 bDeviceClass=255 bDeviceSubClass=0
                                         ^^^^^^^^^^^^^^^^
  bNumEndpoints=0 bInterfaceClass=255 bInterfaceSubClass=0
                  ^^^^^^^^^^^^^^^^^^^
  bNumEndpoints=5 bInterfaceClass=255 bInterfaceSubClass=0
                  ^^^^^^^^^^^^^^^^^^^
Also, src/sys/dev/usb/usb.h .

If I'm not understanding you right, then sorry...


> usbctl is the tool to get an overview of the device layout.
> It's old and has a number of bugs in respect to port system compliance

Also `usbgen' is useful too.  Although I'm not sure that as it exists,
it's doing everything it should, as I seem to have some errors pulling
some strings out of some devices.
getstring 1 failed (error=5)
getstring 2 failed (error=5)
I wonder if the recent NetBSD language delta has anything to do with
this; as recent NetBSD can retrieve the vendor of my sound card while
the old FreeBSD code I'm still running can't...


(usbctl is the tool I was thinking of -- I happened to have an old
binary compiled for an old kernel with a different ioctl() to query
the device.)  Also of interest is `testlibusb' in the devel/libusb port.
They pretty much present the same info in different ways.


barry bouwsma



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412270120.iBR1K9o07904>