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: Sat, 9 Feb 2019 15:38:07 +0100 [thread overview]
Message-ID: <20190209153807.57481152@windsurf.home> (raw)
In-Reply-To: <20190205160959.25927-1-patrickdepinguin@gmail.com>
On Tue, 5 Feb 2019 17:09:59 +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.
>
> Nevertheless, even for Mercury, there are some restrictions:
> - pthread_atfork is used, which requires an MMU
> - sync functions like __sync_sub_and_fetch and __sync_add_and_fetch are
> expected.
>
> As the corresponding 'linux extension' selects Xenomai, we add the
> MMU and sync dependencies there too. They may or may not already be covered
> by XENOMAI_COBALT_ARCH_SUPPORTS flag.
>
> Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
> ---
> linux/Config.ext.in | 12 ++++++++----
> package/xenomai/Config.in | 11 +++++++----
> 2 files changed, 15 insertions(+), 8 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-09 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 16:09 [Buildroot] [PATCH] xenomai: move arch restriction to Cobalt core, no restriction for Mercury Thomas De Schampheleire
2019-02-09 14:38 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-21 19:50 Thomas De Schampheleire
2019-02-04 21:00 ` 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=20190209153807.57481152@windsurf.home \
--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