From: "Németh Márton" <nm127@freemail.hu>
To: linux-usb@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Developer support list for Wireshark
<wireshark-dev@wireshark.org>
Subject: usbmon: size of different fields?
Date: Tue, 09 Nov 2010 07:40:36 +0100 [thread overview]
Message-ID: <4CD8ECE4.1090206@freemail.hu> (raw)
Hi,
I'm looking at the struct mon_bin_hdr and struct mon_bin_isodesc in file
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/usb/mon/mon_bin.c;h=44cb37b5a4dc1f9b27075e3db5346b9ebe307b22;hb=HEAD
As far as I understand u64, s64, u32 and s32 have always fixed bit lengths.
What about "unsigned char", "char", "unsigned int" and "int"? May their size in bits
differ in different architecture?
I'm asking this because I was dealing with the USB packet dissectors for Wireshark
and it is possible to capture the USB traffic on one computer and then transfer
the file to another computer.
Márton Németh
next reply other threads:[~2010-11-09 6:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 6:40 Németh Márton [this message]
2010-11-09 14:50 ` usbmon: size of different fields? 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
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=4CD8ECE4.1090206@freemail.hu \
--to=nm127@freemail.hu \
--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