On 28 August 2012 10:08, Lars Segerlund <[email protected]> wrote:
> RT-Preempt runs the interrupts as threads, in order to do priority > inversion and such, so things got a lot better after the BKL went > away. Looking at the sample code, it seems that the way to use RT-preempt is to use a busy-wait loop with a nanosleep on it. Would the LinuxCNC solution require all the HAL drivers to be re-coded to follow this pattern, or would 1-3 sections of code of this shape become the realtime threads, calling the function lists? I confess I have never bothered to track down where the realtime threads "run" in the current LinuxCNC, I have just been content to addf my code and watch it run. (Run thread, run. See thread run. Janet and John go driver hacking) -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
