On Tue, 27 Feb 2007 15:12:22 -0500, "Jon Smirl" <[EMAIL PROTECTED]> wrote:
> I'm writing code to undo all of this in Wireshark and turn it back > into a standard USB packet stream. [...] Please keep in mind that USB is not Ethernet, so not everything encoded in the transferred data. Those debugging drivers may want to know if any tokens were circulated, or things of such nature. > But it might be better to leave the kernel interface alone and fix all > of this in libpcap. I'd like the stream to contain the minimum > required information and then let Wireshark compute fields from the > minimal data if necessary. Sounds like a plan. Essentially you are making up a "wire protocol" which encapsulates USB, and not even a real USB, but USB as captured at the interface of in-kernel API. USB as such as no submissions and callbacks, it has tokens and packets. But unfortunately I can't capture them, or else I would. -- Pete ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
