All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH] let skins select nucleus features
Date: Tue, 18 Apr 2006 12:50:02 +0200	[thread overview]
Message-ID: <4444C45A.7050308@domain.hid> (raw)
In-Reply-To: <444419E1.6040100@domain.hid>

Jan Kiszka wrote:
> Philippe Gerum wrote:
> 
>>Jan Kiszka wrote:
>>
>>>Hi,
>>>
>>>this patch aims at avoiding to select unneeded nucleus features if no
>>>user is requiring it in the skins. Particularly, it addresses the
>>>nucleus registry and the pipes.
>>>
>>>I have spent no effort on 2.4 yet as I first want to wait for comments.
>>>Furthermore, 2.4. is lacking "select", so the feature selection has to
>>>remain manually there anyway.
>>
>>Looks good. Merged, thanks.
>>
> 
> 
> In the same sense, but not that comfortable, here is the a 2.4 variant
> of the patch.

I don't agree with the logic of this patch. All user-space enabled skins 
may also run in pure kernel-space in non pervasive mode. A core 
dependency exists from CONFIG_XENO_OPT_REGISTRY on 
CONFIG_XENO_OPT_PERVASIVE, and it should be defined explicitely. In any 
case, maybe it's not worth trying to be too smart with the 2.4 
configuration system when it comes to dealing with features 
inter-dependencies, since we really miss the proper support to do that.

-- 

Philippe.


  reply	other threads:[~2006-04-18 10:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 18:34 [Xenomai-core] [PATCH] let skins select nucleus features Jan Kiszka
2006-04-16 17:01 ` Philippe Gerum
2006-04-17 22:42   ` Jan Kiszka
2006-04-18 10:50     ` Philippe Gerum [this message]
2006-04-18 12:14       ` Jan Kiszka
2006-04-18 12:20         ` Philippe Gerum

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=4444C45A.7050308@domain.hid \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@domain.hid \
    --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.