On Tue, 2007-02-27 at 13:47 -0500, Jon Smirl wrote:
> I'm not too keen on using an ASCII 'S' in the setup field to tell
> whether setup[8] is in use or not. Am I correct in thinking that
> setup[8] is always active on an URB submission and never active on a
> completion or error?
Well, not exactl
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 debuggi
On 2/27/07, Pete Zaitcev <[EMAIL PROTECTED]> wrote:
> On Tue, 27 Feb 2007 13:47:41 -0500, "Jon Smirl" <[EMAIL PROTECTED]> wrote:
>
> > This is the structure being returned:
> >[...]
>
> You are confusing the usbmon's API with the "packet format" which
> Paolo manufactured for Wireshark's internal c
On Tue, 27 Feb 2007 13:47:41 -0500, "Jon Smirl" <[EMAIL PROTECTED]> wrote:
> This is the structure being returned:
>[...]
You are confusing the usbmon's API with the "packet format" which
Paolo manufactured for Wireshark's internal consumption. In his case,
he has to present some kind of stream o
This is the structure being returned:
struct usbmon_packet {
u64 id; /* 0: URB ID - from submission to callback */
unsigned char type; /* 8: Same as text; extensible. */
unsigned char xfer_type; /*ISO (0), Intr, Control, Bulk (3) */
unsigne
On 2/27/07, Paolo Abeni <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-02-26 at 21:29 -0500, Jon Smirl wrote:
> > I'm looking at the request/response record of a get descriptor zero.
> >
> > [...]
> >
> > Response has eight bytes of leading zeros which correspond to the
> > eight bytes of the request.
>
On Mon, 2007-02-26 at 21:29 -0500, Jon Smirl wrote:
> I'm looking at the request/response record of a get descriptor zero.
>
> [...]
>
> Response has eight bytes of leading zeros which correspond to the
> eight bytes of the request.
I'm sorry to see I wasn't able to explain the issue. The usb s
I'm looking at the request/response record of a get descriptor zero.
This is the correct request
80 06 00 03 00 00 ff 00
Response
00 00 00 00 00 00 00 00 04 03 09 04
Response has eight bytes of leading zeros which correspond to the
eight bytes of the request.
I think response should either look
