On Thu, 18 Dec 2014, Udo van den Heuvel wrote: > On 2014-12-17 18:25, Alan Stern wrote: > > On Sat, 13 Dec 2014, Udo van den Heuvel wrote: > > What are we supposed to see? The lsusb output in the bug report lists > > a bunch of devices, but it's not clear which one is the airspy. > > I did not program the tools. But the other devices are keyboard, webcam > and some USB erupters. Let me put it this way: Why did you bother to include the "lsusb -t" output in the bug report, with no explanation, if readers can't tell which device is the one causing your problem? > > The bug report says there should be 10 M samples per second. How many > > bytes are in a sample? 2? > > I and Q samples are two bytes each. What is an I sample? What is a Q sample? Are there any samples that aren't two bytes? You need to keep in mind that the people reading this mailing list know a lot about USB but don't know anything about Airspy devices. > > Now, maybe the transfer isn't just raw data. Protocol overhead would > > reduce the total throughput. But since I don't know what the protocol > > is, all I can tell you is the raw data rate. > > I'll ask some usbmon folks to comment. One of them just did... :-) Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html