On 01/29/2013 06:54 AM, Michael Haberler wrote:
> I'm testing linuxcnc with John's 3.5.7 - 2.6.2.1 kernel and found an
> issue with the deprecated linuxcnc xenomai-kernel threads version
> (the userland threads version is fine; both using native skin). I
> traced that back to rt_timer_ticks2ns(30000) returning zero.
>
> The config difference I see is: CONFIG_XENO_OPT_TIMING_PERIODIC=y on
> 3.5.7, unset on 3.2.21
The periodic timing option =y made it into my kernel
script-kiddie-style: I copied it directly from Gilles's config without
trying to understand every option.
>
> The way I read back messages I'd think that should be unset for
> native and Posix skins; these are compiled in:
>
> CONFIG_XENO_SKIN_NATIVE=y
> CONFIG_XENO_SKIN_POSIX=y
> CONFIG_XENO_SKIN_PSOS=m
> CONFIG_XENO_SKIN_UITRON=m
> CONFIG_XENO_SKIN_VRTX=m
> CONFIG_XENO_SKIN_VXWORKS=m
> CONFIG_XENO_SKIN_RTDM=y
Now that I've gone back and read, I don't understand either. Native and
posix styles need periodic timing unset.
At least the VXWorks skin needs periodic timing, so loading the VXWorks
skin module with periodic timing unset has no purpose, since RT programs
using the skin won't work.
>
> (not that we're about to use the other skins soon, but I understand
> John is shooting for a most generic setup)
Yes, that's right, and of course with a preference to support the work
you did on LinuxCNC. :) Luckily, its interface with Xenomai is pretty
simple and uses the native skin, which I would have picked for a generic
kernel anyway.
>
> Am I correct to assume the right thing to do is to set
> CONFIG_XENO_OPT_TIMING_PERIODIC=n for that purpose?
Still scratching my head on this.
John
>
> thanks in advance,
>
> Michael
>
>
> _______________________________________________
> Xenomai mailing list
> [email protected]
> http://www.xenomai.org/mailman/listinfo/xenomai
>
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
