From: Philippe Gerum <rpm@xenomai.org>
To: hauptmech <hauptmech@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] How does the adeos and xenomai project stay synchronized with the linux kernel project?
Date: Fri, 14 Dec 2012 23:12:28 +0100 [thread overview]
Message-ID: <50CBA44C.5090402@xenomai.org> (raw)
In-Reply-To: <50CB2610.6010905@gmail.com>
On 12/14/2012 02:13 PM, hauptmech wrote:
>
> I've used and followed Xenomai off and on since it forked from RTAI.
It did not. A fork happens when you diverge from a common code base,
which does not apply to Xenomai wrt RTAI. Both used to be independent
projects before they joined forces, then split as we failed to actually
merge both real-time cores. Portions of Adeos might still be shared by
both projects, but incidentally, it is a Xenomai-originated
contribution. Please check
https://www.xenomai.org/index.php/Xenomai:History for facts.
I'm
> building a new xenomai x86 system after a few years of doing other
> things. I'm noticing that the adeos patches are few and relatively old
> compared to the kernel for the x86 architecture.
We published 990 official Adeos patches since 2001, with more than half
of them targeting the x86_32 and _64 architectures. I would not call
these a few. Please check download.gna.org/adeos/patches for more
information.
Kernel version 3.2 has
> moved from .21 to .35 for instance.
>
We never updated the Adeos patches for minor linux releases routinely,
this has never been our policy, and will likely never be the case. This
would just involve way too much work for our bandwidth. We are focusing
on major releases. So you seem to be expecting something we never
delivered in the past anyway.
However, the pace of our Adeos updates for major kernel releases has
slowed down over the past three years, definitely. This said, we have
support for kernel 3.4 and in some cases 3.5, for the main architecture
ports we maintain, it's not lagging that far behind.
> So my question is (with the deepest respect for the effort it must take)
> why?
>
Because we all have to deal with priorities and available resources,
this is no different for the Xenomai maintainers.
> Is
>
>
>
>
>
> _______________________________________________
> Xenomai mailing list
> Xenomai@xenomai.org
> http://www.xenomai.org/mailman/listinfo/xenomai
>
--
Philippe.
next prev parent reply other threads:[~2012-12-14 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 13:13 [Xenomai] How does the adeos and xenomai project stay synchronized with the linux kernel project? hauptmech
2012-12-14 22:12 ` Philippe Gerum [this message]
2012-12-15 11:47 ` Gilles Chanteperdrix
2012-12-16 13:41 ` hauptmech
2012-12-16 14:11 ` Gilles Chanteperdrix
2012-12-17 0:02 ` hauptmech
2012-12-17 7:52 ` Gilles Chanteperdrix
2012-12-18 8:10 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2012-12-14 14:10 hauptmech
2012-12-14 14:27 ` Tim Niemeyer
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=50CBA44C.5090402@xenomai.org \
--to=rpm@xenomai.org \
--cc=hauptmech@gmail.com \
--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.