From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Xenomai 3.0.1?
Date: Fri, 29 Jan 2016 09:36:35 +0100 [thread overview]
Message-ID: <20160129093635.3e265ab2@free-electrons.com> (raw)
In-Reply-To: <0eb901d159ee$a8a7e900$f9f7bb00$@chordia.co.uk>
Hello Jerry,
On Thu, 28 Jan 2016 17:09:33 -0000, jerry at chordia.co.uk wrote:
> Running the xenomai prepare-kernel script against an externally sourced
> 3.18.26 kernel. Buildroot builds a bootable kernel and working FS but the
> Xenomai userland tools appear to be related to 2.X.
>
> How do I best get BR to install the latest stuff?
You need to adapt the Xenomai package in package/xenomai/ and also
probably the Xenomai Linux extension logic in
linux/linux-ext-xenomai.mk.
Note however that there is a *big* difference between Xenomai 2 and
Xenomai 3, and therefore this update is certainly not the easiest
Buildroot modification that you can imagine. Xenomai 3 can run on top
of PREEMPT_RT kernels, without the Xenomai co-kernel and Adeos
interrupt pipeline. This probably requires some fairly significant
changes in the Xenomai packaging.
In addition, since Xenomai 3 is rather new and so different from
Xenomai 2, we probably want to keep support for Xenomai 2 for a while,
which adds even more challenge to the task.
In fact, I didn't notice that Xenomai 3 was officially released, last
time I looked they were at the 3.0-rc stage, so I didn't bother doing
the Buildroot packaging. I might have a look some day, but that's
pretty far away on my TODO list, so if someone else wants to look at
it, it would definitely be great!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-29 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 17:09 [Buildroot] Xenomai 3.0.1? jerry at chordia.co.uk
2016-01-29 8:36 ` Thomas Petazzoni [this message]
2016-01-29 12:53 ` jerry at chordia.co.uk
2016-01-30 7:59 ` Arnout Vandecappelle
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=20160129093635.3e265ab2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox