* [Xenomai-help] Xenomai on kernel 3.x and x86
@ 2012-05-14 7:45 Leopold Palomo-Avellaneda
2012-05-14 8:13 ` Philippe Gerum
0 siblings, 1 reply; 3+ messages in thread
From: Leopold Palomo-Avellaneda @ 2012-05-14 7:45 UTC (permalink / raw)
To: xenomai
Hi,
sorry if the question it's obvious but I have not understood the information
that I have found. I have read the roadmap of Xenomai [1] and it's not clear
to me what should I have to do if I would want to use xenomai in a kernel
3.x.
As far as I understand the idea it's to go to Xenomai 3 with the prempt patch
or a co-kernel option. Then xenomai will be the interface to the realtime
kernel. From the user point of view, no matter if xenomai will use the rt-
preemt or the co-kernel option. Also, the driver option will be the rtdm.
But I don't understand if the Adeos patch will survive (at least in x86) or
what will happen. I understand that the co-kernel option is the same that we
have now (2.6) with the adeos patch, but I have not be able to find an Adeos
patch for a x86 platform in a 3.x kernel.
Please, someone could clarify this.
Thanks in advance,
Leo
[1] http://www.xenomai.org/index.php/Xenomai:Roadmap
--
--
Linux User 152692
Catalonia
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Xenomai-help] Xenomai on kernel 3.x and x86
2012-05-14 7:45 [Xenomai-help] Xenomai on kernel 3.x and x86 Leopold Palomo-Avellaneda
@ 2012-05-14 8:13 ` Philippe Gerum
2012-05-14 23:06 ` Gilles Chanteperdrix
0 siblings, 1 reply; 3+ messages in thread
From: Philippe Gerum @ 2012-05-14 8:13 UTC (permalink / raw)
To: Leopold Palomo-Avellaneda; +Cc: xenomai
On 05/14/2012 09:45 AM, Leopold Palomo-Avellaneda wrote:
> Hi,
>
> sorry if the question it's obvious but I have not understood the information
> that I have found. I have read the roadmap of Xenomai [1] and it's not clear
> to me what should I have to do if I would want to use xenomai in a kernel
> 3.x.
>
> As far as I understand the idea it's to go to Xenomai 3 with the prempt patch
> or a co-kernel option. Then xenomai will be the interface to the realtime
> kernel. From the user point of view, no matter if xenomai will use the rt-
> preemt or the co-kernel option. Also, the driver option will be the rtdm.
>
> But I don't understand if the Adeos patch will survive (at least in x86) or
> what will happen. I understand that the co-kernel option is the same that we
> have now (2.6) with the adeos patch, but I have not be able to find an Adeos
> patch for a x86 platform in a 3.x kernel.
The interrupt pipeline will be maintained for running the co-kernel
incarnation of Xenomai 3, and for updating the 2.6.x maintenance branch
as well. To run 3.2 kernels and above, using Xenomai 2.6.1 or later will
be a requirement.
There is an upcoming patch for linux 3.2, which is the first of the new
pipeline "core" series, a massive refactoring of the I-pipe
implementation and API, aimed at a better integration with Xenomai:
http://git.denx.de/?p=ipipe-2.6.git;a=shortlog;h=refs/heads/core-3.2
It currently supports powerpc, arm, x86 and blackfin, and can be used
with Xenomai 2.6.1+ and Xenomai 3 systems in dual kernel mode. I will
roll this patch out officially when Gilles and I are done with fixing
the rough edges. The plan is to have it shipped with the upcoming 2.6.1.
To sum up: the interrupt pipeline for x86 is maintained, a release for
3.x kernels is upcoming.
>
> Please, someone could clarify this.
>
> Thanks in advance,
>
> Leo
>
>
>
> [1] http://www.xenomai.org/index.php/Xenomai:Roadmap
>
--
Philippe.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-05-14 23:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-14 7:45 [Xenomai-help] Xenomai on kernel 3.x and x86 Leopold Palomo-Avellaneda
2012-05-14 8:13 ` Philippe Gerum
2012-05-14 23:06 ` Gilles Chanteperdrix
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.