On Tue, Jul 23, 2019 at 8:27 AM Guy Harris wrote:
> So "USB 2.0" really means "USB 2.0", and we could describe this as something
> such as
>
> LINKTYPE_USB_2_0XXX DLT_USB_2_0 USB 2.0, 1.1, or 1.0
> packet, beginning with a PID, as described by Chapter 8 "Protocol Layer" o
So "USB 2.0" really means "USB 2.0", and we could describe this as something
such as
LINKTYPE_USB_2_0XXX DLT_USB_2_0 USB 2.0, 1.1, or 1.0
packet, beginning with a PID, as described by Chapter 8 "Protocol Layer" of the
Universal Serial Bus Specification Revision 2.0.
wit
Hello Guy,
On 23 Jul 2019, at 3:43, Guy Harris wrote:
So should we just say something such as
LINKTYPE_Z_WAVE_SERIAL XXX DLT_Z_WAVE_SERIAL Serial frames
transmitted between a host and a Z-Wave chip over an RS-232 or USB
serial connection, as described in section 5 of the Z-Wave Serial API
On Tue, Jul 23, 2019 at 3:59 AM Guy Harris wrote:
> The issue isn't the hardware signals.
The link layer protocols are so different that in order for USB 3.0
SuperSpeed devices to be compatible with USB 2.0 hosts, such device
have to implement *both* USB 3.0 link layer and USB 2.0 link layer.
USB
On Jul 21, 2019, at 9:22 PM, Tomasz Moń wrote:
> On Sun, Jul 21, 2019 at 10:47 PM Guy Harris wrote:
>> It looks as if USB 3.1's packets are different from USB 2.0's packets, so
>> this would be 2.0-specific.
>
> USB 3 operates on different hardware signals. USB 3 hubs do contain
> USB 3 and US
On Jul 21, 2019, at 2:19 PM, Mikhail Gusarov wrote:
> On 21 Jul 2019, at 23:07, Guy Harris wrote:
>
>> So a "garbage frame" would be any frame that begins with a value other than
>> 0x06, 0x15, 0x18, or 0x01?
>
>> Is there any reason for whatever capture mechanism produces these packets
>> no
