On Monday 12 October 2009 23:09:13 Jeff Epler wrote:
by implementing rtai/rtapi-inspired threads and shared memory (the two
One question about SHM. In the rtapi_app concept, is SHM ever accessed from
outside of rtapi_app, or is it only used for communication between the RT
threads?
(Sorry for
On Tue, Oct 13, 2009 at 03:50:00PM +0200, Michael Buesch wrote:
On Monday 12 October 2009 23:09:13 Jeff Epler wrote:
by implementing rtai/rtapi-inspired threads and shared memory (the two
One question about SHM. In the rtapi_app concept, is SHM ever accessed from
outside of rtapi_app, or is
So I created a quilt directory on my server where I will always publish my
latest work on this.
Just go to
http://bu3sch.de/patches/emc-linux-rt/
The constant link to the latest patchset is
http://bu3sch.de/patches/emc-linux-rt/LATEST/
There you can get the quilt series, split out and as
This is very interesting -- thanks for working on it. I have a few
questions, though.
How do hardware drivers work with --realtime=linux?
Is there a reason to keep --enable-simulator?
(I suspect the answers here may be tied together: hardware driver
support will require something, perhaps
I find that --enable-simulator works fine in a virtual machine. Will
--realtime=linux also work? If not, I think we need to keep
--enable-simulator.
Ken
Jeff Epler wrote:
This is very interesting -- thanks for working on it. I have a few
questions, though.
How do hardware drivers work
On Sunday 11 October 2009 16:36:38 Jeff Epler wrote:
This is very interesting -- thanks for working on it. I have a few
questions, though.
How do hardware drivers work with --realtime=linux?
They don't, yet. I'm currently focussing on the latency tester.
However, in x86 it's easy to do raw
This patch is an attempt to port EMC to run on realtime capable linux
without a realtime hypervisor.
Linux-RT currently is not ready to support the hard realtime requirements
of EMC, but I think it's a good idea to start playing with it.
The patch is based on an earlier patchset published by
