Hi! Since commit 5827f61b641cfd326a9cf2ea534eb4f9481a8187 the config keys have capabilities associated with them. I think '_GET' and '_SET' are more or less obvious, but what are the intended semantics of the '_LIST' capability supposed to be?
Also, how is sr_dev_has_option() supposed to work now? As far as I can tell, currently it kind of doesn't, but what are the intended semantics? And finally, the commit log talks about updating the SR_CONF_MASK if new bits are added. As far as I can see, that mask is part of the ABI and if there is any remote possibility that new bits will be needed, it might be a better idea to reserve some extra bits in the mask now before they are needed. That way there is at least some chance that some "innocuous" bits could be defined there in the future without breaking the ABI, right? ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
