On Fri, 2009-10-09 at 00:00 +0200, Alexis Berlemont wrote:

> If I understand well, I have gone too far too soon; the idea should be
> to keep the current framework as it is for 2.5.
> However, my former mail was not a definitive plan. The first goal was
> to share ideas. So, do not worry too much. :)

Maintaining two different frameworks for the same purpose won't fly. I'm
worried because the future of Comedi/RTDM as merged in the 2.5 tree just
became unclear - to say the least - as from you introduced the idea of
changing its architecture.

Your potential user-base has to know whether using the current
Comedi/RTDM framework for new designs based on 2.5.x will still make
sense in six months from now, when Analogy eventually emerges. 

In other words, is there any upgrade path planned? What would this

Would one have to rewrite custom DAQ drivers to port them from
Comedi/RTDM to Analogy, or could rely on a some compat wrapper for
supporting legacy Comedi/RTDM Driver-Kernel interface on top of the
Analogy core?

Would that new architecture bring changes in the applications, i.e. what
about the impact of such changes on the way userland interfaces to the
acquisition framework and/or its drivers?

I would have thought that Comedi/RTDM in the 2.5 tree would become
Analogy as is, and evolve over time in a careful manner so that people
always have a reasonable upgrade path. But now, I'm unsure whether this
is going to be the case, or we would end up with two different
frameworks. So, what is the _exact_ plan?


Xenomai-core mailing list

Reply via email to