From: Pete Zaitcev <zaitcev@redhat.com>
To: Guy Harris <guy@alum.mit.edu>
Cc: Developer support list for Wireshark
<wireshark-dev@wireshark.org>,
linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: usbmon: size of different fields?
Date: Wed, 10 Nov 2010 08:21:23 -0700 [thread overview]
Message-ID: <20101110082123.2dc1d361@lembas.zaitcev.lan> (raw)
In-Reply-To: <E6FD75ED-7E13-47DC-B9F9-6C8C09C3C4AC@alum.mit.edu>
On Tue, 9 Nov 2010 13:23:28 -0800
Guy Harris <guy@alum.mit.edu> wrote:
> On Nov 9, 2010, at 12:05 PM, Németh Márton wrote:
>
> > OK, that's clear, the byte order of the API structure fields are in "host endian"
> > order. The API structures are already saved by Wireshark into file for quite some
> > time.
>
> ...and tcpdump. Support for capturing on USB on Linux has been in
> libpcap since at least libpcap 1.0.
I imagined that Nemeth wanted to implement an alternative to that.
Surely he knows how libpcap works. In that case a new, host-independent
format may be introduced. But userland is mysterious to me.
I'll make sure to document ISO descriptors properly. I was sure
I had done that, sorry.
-- Pete
next prev parent reply other threads:[~2010-11-10 15:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 6:40 Németh Márton
2010-11-09 14:50 ` Pete Zaitcev
2010-11-09 20:05 ` Németh Márton
2010-11-09 21:23 ` [Wireshark-dev] " Guy Harris
2010-11-10 15:21 ` Pete Zaitcev [this message]
2010-11-10 17:36 ` Guy Harris
2010-11-13 22:15 ` [PATCH, RFC] usbmon: correct computing of the ISO packets with mmap Németh Márton
2010-11-14 19:40 ` Pete Zaitcev
2010-11-14 20:24 ` Németh Márton
2010-11-14 21:08 ` Pete Zaitcev
2010-11-14 23:25 ` Pete Zaitcev
2010-11-15 3:01 ` Alan Stern
2010-11-15 3:42 ` Pete Zaitcev
2010-11-15 15:01 ` Alan Stern
2010-11-15 5:48 ` Németh Márton
2010-11-15 6:12 ` Pete Zaitcev
2010-11-15 15:06 ` Alan Stern
2010-11-16 6:00 ` Németh Márton
2010-11-09 15:05 ` usbmon: size of different fields? Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101110082123.2dc1d361@lembas.zaitcev.lan \
--to=zaitcev@redhat.com \
--cc=guy@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=wireshark-dev@wireshark.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®