On 22 February 2010 18:33, Paul Alfille <[email protected]> wrote: > It's fine to stay on this list. The discussion is welcome, in fact.
That's great news - many thanks! There's definitely a place for a generic protocol for a device that tells the master the capabilities of each of it's I/O ports. Some initial thoughts - say, a one byte response stating the number of ports it has, followed by two bytes for each port - the first describing the type of I/O including whether in, out or both, and the second to describe the port where required - so, for example, 2^n magnitude for ADC/DACs? Allows a single device code to be used for up to 256 devices with two-bits reserved for I/O flags, up to 64 different types of device and the ability to provide 8-bits of detail about that device. If anything, this could potentially be too much, but could offer any element of future proofing. I'm busy for the next couple of days but will pick the discussion up on my return. Ben ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
