Re: Design of instructions for Counter/Timer subdevices...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 11 April 2003 12:56 pm, Herman Bruyninckx wrote:
>
> Anyway, I think the double use of the instruction function leads to
> too many misunderstandings. Already now, configuration instructions
> misuse the "data" fields, because their type is lsampl_t. Not really a
> good situation...
>
> Giving counters their own data structure requires a change of the
> Comedi API, but it would be a good occasion to get rid of the
> "chanspec" integer; in fact, this integer is already a mini
> data-structure forced into 32 bits. Giving each channel a real
> configuration data structure would make things much more
> understandable, I think. At the same time, a new configuration
> function should be introduced: comedi_channel_config(), for example.

The real issue here is that comedi has achieved a state of eternal beta.  
What we really need is to reach 1.0 and then we can branch off the stable 
version and start making tweaks to improve the API.  What might help is to 
clearly define exactly what needs to be done for 1.0.  Maybe through using 
the bugzilla, and assigning various bugs to comedi/comedlib version 1.0? 

- -- 
Frank

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+lw3V5vihyNWuA4URAjuLAKC9WaCHmoQfMtxltOGxdUXZTFqDPgCgiuRT
y147QlutDiWcDwQdIcZEJy4=
=ktu/
-----END PGP SIGNATURE-----

Received on 2003-04-11Z17:47:49