Comment # 3
on bug 10452
from Michal Labedzki
I hope ADB dissector will be ready in next month (October). I have some task to
do in it before release it. But there is a problem... In your capture file I
see that your device specify different endpoints for ADB channel over USB.
INTERFACE DESCRIPTOR (1.0): class Vendor Specific
bLength: 9
bDescriptorType: 0x04 (INTERFACE)
bInterfaceNumber: 1
bAlternateSetting: 0
bNumEndpoints: 2
bInterfaceClass: Vendor Specific (0xff)
bInterfaceSubClass: 0x42
bInterfaceProtocol: 0x01
iInterface: 0
ENDPOINT DESCRIPTOR
bLength: 7
bDescriptorType: 0x05 (ENDPOINT)
bEndpointAddress: 0x85 IN Endpoint:5
1... .... = Direction: IN Endpoint
.... 0101 = Endpoint Number: 0x05
bmAttributes: 0x02
.... ..10 = Transfertype: Bulk-Transfer (0x02)
.... 00.. = Synchronisationtype: No Sync (0x00)
..00 .... = Behaviourtype: Data-Endpoint (0x00)
wMaxPacketSize: 512
.... ..10 0000 0000 = Maximum Packet Size: 512
bInterval: 0
ENDPOINT DESCRIPTOR
bLength: 7
bDescriptorType: 0x05 (ENDPOINT)
bEndpointAddress: 0x04 OUT Endpoint:4
0... .... = Direction: OUT Endpoint
.... 0100 = Endpoint Number: 0x04
bmAttributes: 0x02
.... ..10 = Transfertype: Bulk-Transfer (0x02)
.... 00.. = Synchronisationtype: No Sync (0x00)
..00 .... = Behaviourtype: Data-Endpoint (0x00)
wMaxPacketSize: 512
.... ..10 0000 0000 = Maximum Packet Size: 512
bInterval: 0
In other devices I see only one endpoint for both direction. The problem is
currently Wireshark does not know about interfaces configuration, so ADB
dissector do not know that these two endpoints are pair for ADB.
I guess that this should be fixed by extend "DecodeAs" for interfaces and
endpoints+direction (two separate things: DecodeBy interfaces; DecodeBy
endpoint+direction). There is a need to spend more time on it, but I hope I can
release ADB dissector with this "small" issue (USB issue = new feature).
You are receiving this mail because:
- You are watching all bug changes.
