aboutsummaryrefslogtreecommitdiffstats
path: root/wiretap/wtap.h
diff options
context:
space:
mode:
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>2008-12-17 23:24:51 +0000
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>2008-12-17 23:24:51 +0000
commit3ab6ccdcd3188ad94ecc8a1403addc2e1057c212 (patch)
tree45fb24e91e95fa917b078719f866521e37c4137c /wiretap/wtap.h
parente9549cfaaffd130d015948fa2b108bd6a09eba69 (diff)
Clarify that, in the Linux USB capture format, the header is always
followed by 8 bytes of "struct usb_device_setup_hdr", even if there's no setup information, but it should be interpreted only if setup_flag is 0. (That's what those mysterious 8 bytes are.) git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@27043 f5534014-38df-0310-8fa8-9805f1628bb7
Diffstat (limited to 'wiretap/wtap.h')
-rw-r--r--wiretap/wtap.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/wiretap/wtap.h b/wiretap/wtap.h
index c4e54158f3..c5cde96077 100644
--- a/wiretap/wtap.h
+++ b/wiretap/wtap.h
@@ -604,8 +604,8 @@ struct usb_device_setup_hdr {
/*
* Header prepended by Linux kernel to each USB event.
- * Followed by a struct usb_device_setup_hdr, although that header is valid
- * only if setup_flag is 0.
+ * Always followed by a struct usb_device_setup_hdr, although that header
+ * is valid only if setup_flag is 0; otherwise it's 8 bytes of junk.
* (Setup flag is '-', 'D', 'Z', or 0. Data flag is '<', '>', 'Z', or 0.)
* See linux/Documentation/usb/usbmon.txt and libpcap/pcap/usb.h for details.
*