ok. any advice for the sniffer? i found this:
http://www.pcausa.com/Utilities/UsbSnoop/default.htm
athos
On 28 December 2011 12:05, Daniel Mack zon...@gmail.com wrote:
My guess is that it only takes a different initialization mechanism, but
I might me wrong. Once you have any more insight or
On 27 December 2011 15:36, alexander axeldenst...@gmail.com wrote:
I'm guessing it's the usbpre1 ? I have the USBpre2 and it works very
well on linux, except not in usb2 mode, even tho it's class compliant
even in usb2 mode.
yes, it's the usbpre 1. I found this old post:
On 17 November 2011 19:26, Daniel Mack zon...@gmail.com wrote:
As I suspected - wonderfully class compliant.
Do you have access to a Mac? Would be interesting to see if that device
would be handled well by the generic driver in OS X (that is, without
their proprietary driver). Any chance you
2011/11/17 Daniel Mack zon...@gmail.com
This is usually a sign that the device is in fact incompatible to the
audio class, even though appearantly, it has class compliant headers.
Can you send the output of lsusb -v?
Thanks for the help. The result of lsusb -v is in the textfile attached.
