All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] xenomai: Add choice for Cobalt/Mercury core
Date: Sat, 8 Apr 2017 15:34:52 +0200	[thread overview]
Message-ID: <20170408153452.54837e4c@free-electrons.com> (raw)
In-Reply-To: <20170406234139.31532-2-sikor6@gmail.com>

Hello,

On Fri,  7 Apr 2017 01:41:39 +0200, Pawel Sikora wrote:

> +choice
> +	prompt "Xenomai core"
> +	default BR2_PACKAGE_XENOMAI_MERCURY
> +	help
> +	  Manually select the Xenomai core. Default option depends if
> +	  you selected BR2_LINUX_KERNEL_EXT_XENOMAI.
> +	  If yes, then default option will be Cobalt.
> +	  Otherwise you can use just the Mercury core with the
> +	  native Linux kernel.
> +
> +config BR2_PACKAGE_XENOMAI_MERCURY
> +	bool "Mercury"
> +	depends on !BR2_LINUX_KERNEL_EXT_XENOMAI
> +	help
> +	  Select Mercury core for the Xenomai userspace.
> +	  If you want Cobalt core, you need to enable
> +	  BR2_LINUX_KERNEL_EXT_XENOMAI in the Linux Kernel ->
> +	  Linux Kernel Extensions menu.
> +
> +config BR2_PACKAGE_XENOMAI_COBALT
> +	bool "Cobalt"
> +	depends on BR2_LINUX_KERNEL_EXT_XENOMAI
> +	help
> +	  Select Cobalt core for the Xenomai userspace.
> +	  If you want Mercury core, you need to disable
> +	  BR2_LINUX_KERNEL_EXT_XENOMAI in the Linux Kernel ->
> +	  Linux Kernel Extensions menu.

Does it really make sense to have a "choice" when in fact it's
impossible to have both options of the choice visible at the same time?
One option depends on !BR2_LINUX_KERNEL_EXT_XENOMAI and the other
option depends on BR2_LINUX_KERNEL_EXT_XENOMAI.

I'm not sure how to handle this. Do we automatically switch between
Cobalt and Mercury depending on whether the Xenomai kernel extension is
enabled?

Do we use Mercury by default, and offer a sub-option to explicitly
enable Cobalt when the Linux kernel extension is available?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-04-08 13:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 23:41 [Buildroot] [PATCH 0/1] xenomai: Add choice for Cobalt/Mercury core Pawel Sikora
2017-04-06 23:41 ` [Buildroot] [PATCH 1/1] " Pawel Sikora
2017-04-07  5:58   ` Thomas De Schampheleire
2017-04-07  8:27     ` Thomas Petazzoni
2017-04-08 14:25       ` Arnout Vandecappelle
2017-04-08 13:34   ` Thomas Petazzoni [this message]
2017-04-08 14:22     ` Arnout Vandecappelle
2017-04-09 22:51       ` Pawel Sikora
2017-04-10  9:08         ` Arnout Vandecappelle
2017-04-10 11:51           ` Thomas Petazzoni
2017-04-10 13:33             ` Arnout Vandecappelle
2017-04-10 20:21               ` Pawel Sikora
2017-04-10 21:19                 ` Arnout Vandecappelle
2017-04-10 19:20           ` Thomas De Schampheleire
2017-04-10 21:14             ` Arnout Vandecappelle
2017-04-11 14:18               ` Thomas De Schampheleire
2017-04-09 23:54   ` [Buildroot] [PATCH v2] xenomai: Add choice for enabling/disabling " Pawel Sikora
2017-04-10 11:11     ` Arnout Vandecappelle
2017-04-10 12:36       ` Pawel Sikora
2017-04-10 12:32     ` [Buildroot] [PATCH v3] " Pawel Sikora
2017-04-10 13:44       ` Arnout Vandecappelle
2017-04-10 19:31       ` Thomas De Schampheleire
2017-04-10 20:01         ` Pawel Sikora
2017-04-10 21:10           ` 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=20170408153452.54837e4c@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 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.