From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Poole Jr, Donald R." <donald.poole@swri.org>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Next Xenomai Release?
Date: Thu, 23 May 2013 21:01:19 +0200 [thread overview]
Message-ID: <519E677F.9050001@xenomai.org> (raw)
In-Reply-To: <E9605457112439448B6B3ED284E06533317AC337@mbx256-1.adm.swri.edu>
On 05/23/2013 05:57 PM, Poole Jr, Donald R. wrote:
> On 5/23/13 10:51 AM, "Jeff Webb" <jeff.webb@nta-inc.net> wrote:
>
>
>> On 05/23/2013 09:32 AM, Poole Jr, Donald R. wrote:
>>> Hello Fellow Xenomai Developers/Users,
>>>
>>> I've have be following the development of Xenomai over the last few
>>> months on this mailing list and have noticed a lot of good features
>>> being added and bugs being fixed since the last 2.6.2.1 release. So, my
>>> question is when is the next stable version of Xenomai going to be
>>> released? I'm particularly interested in the Bealgebone 3.8 kernel
>>> patch since this is the hardware I'm working with. I have read the post
>>> regarding the Raspberry Pi/Beaglebone I-pipe patches, but I it was
>>> unclear to me how they were to be applied and to what code base they
>>> were to be applied to.
>>>
>>> If someone could clarify to me how to use the patches in there current
>>> state (if they are stable enough), that would be great. Otherwise, I
>>> could wait until the next official release, that I presume would have
>>> the RaspberryPi/Beaglebone 3.8.x kernel patches.
>>
>> Someone just asked basically the same question (about the next release) a
>> few days ago:
>>
>> http://www.xenomai.org/pipermail/xenomai/2013-May/028515.html
>>
>> Gilles gave a nice response:
>>
>> http://www.xenomai.org/pipermail/xenomai/2013-May/028516.html
>>
>> I'm surprised you didn't notice these posts if you've been on the list
>> for a few months...
>>
>> -Jeff
>>
>
>
> I guess I overlooked that post and response. Any clarifying words/steps on
> what needs to be done to get the 3.8.x kernel patched with Xenomai for
> running on the Beaglebone/Raspberry Pi in the meantime?
For beaglebone, it is integrated in the I-pipe tree for the ARM
architecture (git://git.xenomai.org/ipipe-gch.git, branch for-core-3.8),
which is currently based on 3.8.0 but will probably be rebased on a more
recent version for the I-pipe 3.8 release, for the raspberry pi, you can
try the patch which has been posted by Paul, but probably needs rebasing
once the I-pipe for 3.8 is released.
--
Gilles.
next prev parent reply other threads:[~2013-05-23 19:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 14:32 [Xenomai] Next Xenomai Release? Poole Jr, Donald R.
2013-05-23 15:51 ` Jeff Webb
2013-05-23 15:57 ` Poole Jr, Donald R.
2013-05-23 19:01 ` Gilles Chanteperdrix [this message]
2013-05-23 22:52 ` Paul
2013-05-23 23:15 ` Poole Jr, Donald R.
2013-05-24 5:36 ` Gilles Chanteperdrix
2013-05-24 5:39 ` Gilles Chanteperdrix
2013-09-10 18:46 ` Gilles Chanteperdrix
2013-09-10 23:57 ` Paul
2013-09-17 15:26 ` Paul
2013-09-17 18:22 ` Gilles Chanteperdrix
2013-05-23 21:33 ` Wolfgang Denk
2013-05-23 21:57 ` Gilles Chanteperdrix
2013-05-24 7:15 ` Wolfgang Denk
2013-05-24 6:29 ` Gilles Chanteperdrix
2013-05-24 7:22 ` Wolfgang Denk
2013-05-24 12:07 ` Gilles Chanteperdrix
2013-05-24 9:01 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=519E677F.9050001@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=donald.poole@swri.org \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.