Drivers publish driver-wide options ONLY when SR_CONF_DEVICE_OPTIONS is queried without specifying an sdi. Right now, driver-wide options are:
- device type (SR_CONF_LOGIC_ANALYZER, SR_CONF_OSCILLOSCOPE etc)
- limits (sample limits, frame limits etc)
PulseView doesn't do this, so misses out on finding out the limits a device can set. This is evident with the demo driver, for example.
Surely these queries should still work if an sdi is passed?