On Thu, 11 Jan 2007 10:04:26 +0100, Paolo Abeni <[EMAIL PROTECTED]> wrote:
> The issue rises because in the pcap code I don't modify the event header
> (and I can't, at least when I use memory mapped access to usbmon). So
> the event header is written in pcap files in host byte order.
But in suc
On Wed, 2007-01-10 at 10:56 -0800, Pete Zaitcev wrote:
> > I'm sorry to have came to this a little too late...
>
> Yeah, that's the main issue. We could have defined the status
> to be structured and have a guaranteed alignment earlier, if anyone
> cared back then.
>
> How much of a problem is it
On Wed, 10 Jan 2007 10:25:54 +0100, Paolo Abeni <[EMAIL PROTECTED]> wrote:
> I have an issue related to the new usbmon binary API.
> AFAIK the header added from the kernel to each event is in host byte
> order, except for the setup header part, which is in little endian byte
> order. All the rema
hello,
I have an issue related to the new usbmon binary API.
AFAIK the header added from the kernel to each event is in host byte
order, except for the setup header part, which is in little endian byte
order. All the remaining data is little endian, too.
Shouldn't be reasonable to update the cod
