From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] Next Xenomai Release?
Date: Fri, 24 May 2013 11:01:50 +0200 [thread overview]
Message-ID: <519F2C7E.6050808@siemens.com> (raw)
In-Reply-To: <519F08C1.6060306@xenomai.org>
On 2013-05-24 08:29, Gilles Chanteperdrix wrote:
> On 05/23/2013 11:33 PM, Wolfgang Denk wrote:
>
>> Dear "Poole Jr, Donald R.",
>>
>> In message <E9605457112439448B6B3ED284E06533317AC337@mbx256-1.adm.swri.edu> you wrote:
>>>
>>> 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?
>>
>> Adding support for a v3.8.x kernel appears to be not really
>> attractive, given that v3.8 has already reached EOL...
>
>
> From what I understand from this post:
> http://www.linuxfoundation.org/news-media/blogs/browse/2013/02/linux-38-not-longterm-kernel
>
> And this page:
> https://www.kernel.org/category/releases.html
>
> Every stable kernel until october 2013 will be EOLed when the next
> kernel is out.
>
> So, any other kernel than 3.0 and 3.4 is not "attractive" until october
> 2013.
>
> As it turns out however, 3.8 is a bit less unattractive than the others,
> because Canonical seem to have announced they would be maintaining it
> for a while longer (until August 2014, it seems) in the following post:
> https://lwn.net/Articles/550581/
Indeed. On x86, the only currently available I-pipe alternative to 3.8
is 3.5. And that one is in EOL for an even longer time now.
We will move on to 3.9 or 3.10 soon, but most probably not soon enough
for the next Xenomai release.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2013-05-24 9: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
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 [this message]
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=519F2C7E.6050808@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gilles.chanteperdrix@xenomai.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.