Difference between revisions of "34C3"
m (→Handling of RLE data: Added some context (for the uninitiated).) |
|||
| Line 14: | Line 14: | ||
Should there be a common format that drivers have to convert custom formats to? | Should there be a common format that drivers have to convert custom formats to? | ||
Should there be a new session bus packet type? What are the implications? | Should there be a new session bus packet type? What are the implications? | ||
See also the discussion from 30C3 [[30C3#Compression|here]]. | |||
== Analog I/O for libsigrokdecode == | == Analog I/O for libsigrokdecode == | ||
Revision as of 18:22, 1 October 2017
We're getting together at the annual CCC conference, 34C3, for a sigrok hackathon. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier. If you want to be part of the conversation and decision-making process, show up!
What's decided here is what goes.
New sigrok file format
What's missing to make it happen?
Handling of RLE data
What is needed to make libsigrok able to handle RLE data? Should there be a common format that drivers have to convert custom formats to? Should there be a new session bus packet type? What are the implications?
See also the discussion from 30C3 here.
Analog I/O for libsigrokdecode
What are the requirements/use cases? What's needed to make it happen?
Flowgraph architecture
How do we achieve this step-by-step? It won't ever happen if it's a huge change :) Currently, plans are to make PV have a modularized internal structure and use flowgraphs internally to gather experience and have something working
PV: Decode table view
The decode table view isn't going to be very usable at the moment because it lacks metadata that libsigrokdecode should provide. We should discuss what the decode table view should offer in terms of functionality and what's needed in libsigrokdecode to make it happen.
PV: Scope UI
PV is getting closer and closer to being usable for analog scopes. We should discuss ideas how a UI could look like that allows for full remote-control operation. There are good and bad UI examples to draw ideas from.