From: Tim Niemeyer <tim.niemeyer@corscience.de>
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 15:27:00 +0100 [thread overview]
Message-ID: <1355495220.2190.6.camel@herbert.er.corscience.de> (raw)
In-Reply-To: <50CB3347.8060000@gmail.com>
Hi
Am Freitag, den 14.12.2012, 15:10 +0100 schrieb hauptmech:
> 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.
I use 3.4 on my rt system. You can find the adeos work from the
Xenomai-Team here:
http://git.xenomai.org/?p=ipipe-gch.git;a=shortlog;h=refs/heads/for-core-3.4
It was quite confused to get it working on 3.4.14. As the work is based
on 3.4.6.
There is also a branch 'for-core-3.5'.
--
Tim Niemeyer
Corscience GmbH & Co. KG
Henkestr. 91
D-91052 Erlangen
Germany
e-mail: tim.niemeyer@corscience.de
Internet: www.corscience.de
next prev parent reply other threads:[~2012-12-14 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 14:10 [Xenomai] How does the adeos and xenomai project stay synchronized with the linux kernel project? hauptmech
2012-12-14 14:27 ` Tim Niemeyer [this message]
-- 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=1355495220.2190.6.camel@herbert.er.corscience.de \
--to=tim.niemeyer@corscience.de \
--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.