https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11743
Joel Holdsworth <j...@airwebreathe.org.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |j...@airwebreathe.org.uk
--- Comment #16 from Joel Holdsworth <j...@airwebreathe.org.uk> ---
I just commented on the Gerrit review:
I'm not sure if I'm interpreting this correctly, but I'm not sure that the
dissector is completely decoding my captures:
https://opentechlab.org.uk/_media/videos:021:20200128-ftdi-usb-disection-fail.png
Many of the packets in my capture have tail bytes labelled "Not dissected yet"
Here is my capture file:
https://opentechlab.org.uk/_media/videos:021:20200128-glamomem-connect.pcapng.gz
Is this expected behavior? Or should it be able to decode this data?
In addition I will say, this is a capture taken from a programming tool for ITE
media processors called "glamomem". In the above trace, I triggered the
initialization sequence which consists of 3x 5-byte SPI transfers.
glamomem uses FT2XX.dll and FTCSPI.dll.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
