From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] xenomai: move arch restriction to Cobalt core, no restriction for Mercury
Date: Mon, 4 Feb 2019 22:00:31 +0100 [thread overview]
Message-ID: <20190204220031.19daf588@windsurf> (raw)
In-Reply-To: <20190121195005.17768-1-patrickdepinguin@gmail.com>
On Mon, 21 Jan 2019 20:50:04 +0100
Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
> From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
>
> Xenomai has two mutually exclusive cores:
> - Cobalt: dual-kernel approach: patched kernel + userland
> - Mercury: only userland
>
> In the Cobalt core, not all architectures are supported. This is the source
> of the existing ARCH_SUPPORTS variable.
>
> In the Mercury core, there is no imposed architecture restriction.
>
> Rename the XENOMAI_ARCH_SUPPORTS flag to XENOMAI_COBALT_ARCH_SUPPORTS and
> move its check from the Xenomai package to the Cobalt core.
>
> Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> ---
> linux/Config.ext.in | 4 ++--
> package/xenomai/Config.in | 5 ++---
> 2 files changed, 4 insertions(+), 5 deletions(-)
The patch looks good, but it needs more testing. Because it lifts all
the architecture dependencies, one can now try to build Xenomai for
funky architectures/configurations, and it doesn't always work. For
example, building with our br-arm-cortex-m4-full configuration fails
with a pthread_atfork issue.
I think this requires running a test-pkg run to check a couple of
architectures/configurations.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-04 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 19:50 [Buildroot] [PATCH] xenomai: move arch restriction to Cobalt core, no restriction for Mercury Thomas De Schampheleire
2019-02-04 21:00 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-05 16:09 Thomas De Schampheleire
2019-02-09 14:38 ` Thomas Petazzoni
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=20190204220031.19daf588@windsurf \
--to=thomas.petazzoni@bootlin.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