I think as far as the source tree is concerned, we should support any variant of realtime that an active developer wishes to support and which does not impose a big technical burden or create technical debt.
Judging from the patches in the rtai-5 branch of linuxcnc, we have an active developer and the changes are not burdensome. And in fact, some small bits of technical debt have been paid off in that branch (removal of code pertaining to even older versions of RTAI) When we decide what to ship to our users, that depends on the choice of whoever is doing the packaging work, but hopefully that is tempered by a willingness to be responsive to real world feedback about RT performance of one kernel+patchset+rtai vs another. In this case, we owe Seb a lot of thanks for doing packaging work for this kernel and RTAI packaging work. And now we can find out how the latency is on this combination vs others we have shipped from linuxcnc.org. Jeff ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
