Hi,
we wrote for wireshark a custom dissector to analyze custom protocol
traffic. However, we need to analyze this data in an extra GUI element
and we’ve chosen PulseView. To integrate PulseView as a plugin into
wireshark, from our current perspective, it would be most efficient if
PulseView would be refactored into 3 parts, the sigrok interface, the
core components including the widgets and the application itself. This
way 3rd party projects (like ours) could integrate PulseView and
potentially extend PulseView easily. In order to get into a discussion
with you, we have some questions:
1. Is there already a (thaught / planning / implementation) process in
progress about a separation of the sigrok interface form PulseView
core?
2. Is there already a (thaughts / planning / implementation) process
in progress about providing a PulseView core library?
3. Is there a dedicated group we should join to enter these discussions
or meeting taking place, e.g. alongside FOSS events, such as FOSDEM?
4. What are your thoughts about our ideas?
The background behind or question is our goal to create an open source
tool to analyze communication within SoCs, e.g. SoC FPGAs, by providing
both insight into protocol structure as well as bit and timing accurate
analysis at the same time with cross-references. You may think about
this like an analyzer for video data transport protocols, which provides
the ability to cross-reference actual pixels within the frames to the
protocol entities that contained them by showing the picture and enables
clicking through the pixels / areas of the frames and the frames within
the timeline of the video. When you click on an images pixel/area, the
respective protocol unit containing the pixel is highlighted and vice
versa. This allows for much better interpretation than going through the
payload view or the image separately.
When we move forward together with PulseView, we do have some features
that we would like to see in place and we are happy to help enhance
PulseView, e.g. being able to show more than 64 signals or providing
multi-level signal grouping.
We already built a proof of concept, but we feel that following this
approach we would basically forced to create a fork PulseView to bypass
the the libsigrok input. As this is neither maintainable nor efficient
this is not want we want to do and we think it is not what the community
is looking for. However, as we do not use sigrok to gather the data, we
need to pass the data to PulseView directly without passing it through
libsigrok.
We hope to get into a fruitful discussion with you! Please share any
comments / ideas / proposals!
Björn Petersen
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
