That's why I think the other direction and put the real time stuff on a micro controller, there are no graphic drivers to think about. I think it is the motion-command-handler and motion-controller threads.
I expect bandwidth required to communicate with the GUI would be rather low. With real time demand removed from the GUI it could be more freely deployed on for example a wireless device. > That's why we'd need the kernel police to enforce the rules, if there > were kernel rules that everyone would agree on. > > On 03/16/2016 02:36 PM, Jerry Scharf wrote: > > The real problem is > > in the kernel and drivers, where you can and often have to lock out > > interrupts. If those are not designed to work correctly and cooperatively, > > things stop being RT. When the person writing the graphics card driver is > > told to get as much performance as they can, they often stop thinking about > > how polite they are to other time critical things. They have almost no > > incentive to be careful and lots of incentive to do what makes things go > > the fastest. > > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
