sorry to be a pain..
>> that's all, and I'll be happy ever after even after the merge with
>> RT_PREEMPT ;-?
>
> Yes, that is the point, the port of RTDM over the Linux kernel API already
> exists, though AFAIK it is not merged yet in the xenomai-forge tree.
porting native->RTDM: mapping the tas
Michael Haberler wrote:
> sorry to be a pain..
>
>>> that's all, and I'll be happy ever after even after the merge with
>>> RT_PREEMPT ;-?
>>
>> Yes, that is the point, the port of RTDM over the Linux kernel API
>> already
>> exists, though AFAIK it is not merged yet in the xenomai-forge tree.
>
>
Michael Haberler wrote:
>
> Gilles,
> Am 03.11.2012 um 10:37 schrieb Gilles Chanteperdrix:
>>
>> http://www.xenomai.org/index.php/I-pipe:Tracer
>
> thanks for the version hint - it was all in place, just needed to
> configure - building now.
>
>> Also note that if LinuxCNC code runs in kernel-spac
Gilles,
Am 03.11.2012 um 10:37 schrieb Gilles Chanteperdrix:
>
> http://www.xenomai.org/index.php/I-pipe:Tracer
thanks for the version hint - it was all in place, just needed to configure -
building now.
> Also note that if LinuxCNC code runs in kernel-space, you should not be
> using the nati
Michael Haberler wrote:
> - the timedelta module just samples with rtapi_get_time():
>
> http://git.mah.priv.at/gitweb/emc2-dev.git/blob/5979d84f31c0ef8e9dccdb26426732d0b83f3a87:/src/hal/components/timedelta.comp
> (this _is_ a kernel module, it's in preprocessor language).
>
> rtapi_get_time() in
Michael Haberler wrote:
> I should have also noted the following:
>
> this is a 3.2.21 kernel homegrown like so:
> http://git.mah.priv.at/gitweb/linuxcnc-kernel.git/shortlog/refs/heads/linuxcnc-3.2.21-xenomai-x86
>
> I just see the ipipe tracer is for 2.6x only; I had dropped the 2.6 line
> becaus
I should have also noted the following:
this is a 3.2.21 kernel homegrown like so:
http://git.mah.priv.at/gitweb/linuxcnc-kernel.git/shortlog/refs/heads/linuxcnc-3.2.21-xenomai-x86
I just see the ipipe tracer is for 2.6x only; I had dropped the 2.6 line
because of a module unloading issue but i
Gilles,
thanks for the fast reply, I will look into the I-pipe tracer.
as for the current code: yes, it uses the native API - I started with existing
RTAI code and massaged that - but I'll rewrite it to RTDM if that's how it's
supposed to be done.
--
as for how the LinuxCNC latency-test works
Michael Haberler wrote:
> I'm porting the LinuxCNC realtime support to Xenomai, and that has its own
> latency-test program.
>
> I observe:
> - the xenomai latency test is generally acceptable
> - with the LinuxCNC latency-test program I see occasional spikes up to
> maybe 80-100uS
>
>
> the only
I'm porting the LinuxCNC realtime support to Xenomai, and that has its own
latency-test program.
I observe:
- the xenomai latency test is generally acceptable
- with the LinuxCNC latency-test program I see occasional spikes up to maybe
80-100uS
the only difference in the code I could discern i
10 matches
Mail list logo
