From: hauptmech <hauptmech@gmail.com>
To: xenomai@xenomai.org
Subject: [Xenomai] How does the adeos and xenomai project stay synchronized with the linux kernel project?
Date: Fri, 14 Dec 2012 15:10:15 +0100 [thread overview]
Message-ID: <50CB3347.8060000@gmail.com> (raw)
(apologies for the previous incomplete email)
I've used and followed Xenomai off and on since it forked from RTAI. 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. Kernel version 3.2 has
moved from .21 to .35 for instance. Meanwhile my (non-rt) systems all
use 3.4 or 3.6.
So my question is (with the deepest respect for the effort it must take)
why? Why do the adeos patches lag so much?
Also why were the linux-3.2.21 x86 patch typos which prevent compilation
not fixed? When such basic thing is not taken care of it makes me doubt
the integrity of the whole project.
In my community (robotics) xenomai is the go-to RT system for me and
most of my peers. However the xenomai roadmap and task-market are
bitrotted and there don't seem to be project status updates on the wiki
or mailing list which makes it hard to contribute or make plans.
I guess I just want to call attention to the fact that things are
looking a little rough at xenomai.org and ask whether passers by like
myself should try to help a little or move on?
kind regards,
hauptmech
next reply other threads:[~2012-12-14 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 14:10 hauptmech [this message]
2012-12-14 14:27 ` [Xenomai] How does the adeos and xenomai project stay synchronized with the linux kernel project? Tim Niemeyer
-- strict thread matches above, loose matches on Subject: below --
2012-12-14 13:13 hauptmech
2012-12-14 22:12 ` Philippe Gerum
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
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=50CB3347.8060000@gmail.com \
--to=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.