aboutsummaryrefslogtreecommitdiffstats
path: root/epan/dissectors/packet-usb.h
diff options
context:
space:
mode:
authorRonnie Sahlberg <ronnie_sahlberg@ozemail.com.au>2006-10-22 11:49:23 +0000
committerRonnie Sahlberg <ronnie_sahlberg@ozemail.com.au>2006-10-22 11:49:23 +0000
commitac67085436e7ee0148289e564568a7b4cc3d5b27 (patch)
tree7d5132b6677ee3718cead672dbd3eed012f36a5b /epan/dissectors/packet-usb.h
parent7a62c1f5fe5bd225a3956c517bb94ff8b7abe106 (diff)
add a dissector table for class specific control input/output pdus
implement class specific control commands : reset and getmaxlun for mass storage now with a better understanding of the problem space for usb and device classes we can start cleaning the code up and make it nice svn path=/trunk/; revision=19659
Diffstat (limited to 'epan/dissectors/packet-usb.h')
-rw-r--r--epan/dissectors/packet-usb.h15
1 files changed, 9 insertions, 6 deletions
diff --git a/epan/dissectors/packet-usb.h b/epan/dissectors/packet-usb.h
index 972a1fcb95..2c55681d1d 100644
--- a/epan/dissectors/packet-usb.h
+++ b/epan/dissectors/packet-usb.h
@@ -24,12 +24,7 @@
#ifndef __PACKET_USB_H__
#define __PACKET_USB_H__
-/* there is one such structure for each device/endpoint conversation */
-typedef struct _usb_conv_info_t {
- guint16 class; /* class for this conversation */
- emem_tree_t *transactions;
- void *masstorage; /* mass storage data */
-} usb_conv_info_t;
+typedef struct _usb_conv_info_t usb_conv_info_t;
/* there is one such structure for each request/response */
typedef struct _usb_trans_info_t {
@@ -54,6 +49,14 @@ typedef struct _usb_trans_info_t {
usb_conv_info_t *interface_info;
} usb_trans_info_t;
+/* there is one such structure for each device/endpoint conversation */
+struct _usb_conv_info_t {
+ guint16 class; /* class for this conversation */
+ emem_tree_t *transactions;
+ void *masstorage; /* mass storage data */
+ usb_trans_info_t *usb_trans_info; /* pointer to the current transaction */
+};
+
/* This is the endpoint number user for "no endpoint" or the fake endpoint
* for the host side since we need two endpoints to manage conversations