All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	Gary Thomas <gary@mlbassoc.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm-extra][PATCH] nitrogen6x.conf: Allow kernel provider override
Date: Wed, 30 Oct 2013 09:16:24 -0700	[thread overview]
Message-ID: <527130D8.3070102@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKpsf7TiwUQ-3zUpA+zAELrRQjdX9G_Yu_3hXOBNaRZmKw@mail.gmail.com>

On 10/30/2013 09:01 AM, Otavio Salvador wrote:
> On Wed, Oct 30, 2013 at 12:44 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> On 2013-10-30 08:33, Otavio Salvador wrote:
>>> On Wed, Oct 30, 2013 at 12:25 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>> On 2013-10-30 08:10, Otavio Salvador wrote:
>>>>> On Wed, Oct 30, 2013 at 11:41 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>>>>
>>>>>> This change lets the user override the choice of kernel in local.conf
>>>>>> Without it, there is no way to build any kernel, e.g. linux-imx, other
>>>>>> than the linux-boundary version.
>>>>>>
>>>>>> Signed-off-by: Gary Thomas <gary@mlbassoc.com>
>>>>>
>>>>> I really dislike this.
>>>>>
>>>>> I understand your need, and it is a valid one, but it'd be better you
>>>>> to make a new machine (which includes this one) and override it there.
>>>>
>>>> Even if I did that (and I have), if I include this config file, I can
>>>> never override this setting in a soft (user settable) way.
>>>
>>> Then you can force it in your machine.
>>>
>>>>> If we start allow all kind of override in machine configuration it
>>>>> loses its meaning and complicates the support.
>>>>>
>>>>> Eric? comments?
>>>>>
>>>> Eric has already approved this change.
>>>
>>> This is not up to me but I'd like to discuss it a little bit further
>>> before merging it...
>>>
>>> My main concern about this is the support. As I said it is a valid
>>> use-case but /most/ people will end with a .conf for the custom
>>> settings in the end with their internal fork or so. Do it in
>>> local.conf or environment is not advised as it is easy to be forgotten
>>> or do wrong so for every product it is better to have a .conf in case
>>> it needs specific kernel/u-boot patches.
>>
>> A reasonable concern.  I do note that having this be soft in <MACHINE>.conf
>> seems to be common practice in the rest of the Yocto world.
>
> Ok; you guys won :-)
>
> I applied it to dora and master (I manually applied it as it has not
> applied cleanly).
>
> Eric, please, if you have time do the same change in nitrogen6x-lite
> so it is kept in sync.
>

Will do.


  reply	other threads:[~2013-10-30 16:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 13:41 [meta-fsl-arm-extra][PATCH] nitrogen6x.conf: Allow kernel provider override Gary Thomas
2013-10-30 14:06 ` Eric Nelson
2013-10-30 14:10 ` Otavio Salvador
2013-10-30 14:25   ` Eric Nelson
2013-10-30 14:28     ` Otavio Salvador
2013-10-30 14:42       ` Eric Nelson
2013-10-30 14:25   ` Gary Thomas
2013-10-30 14:33     ` Otavio Salvador
2013-10-30 14:44       ` Gary Thomas
2013-10-30 16:01         ` Otavio Salvador
2013-10-30 16:16           ` Eric Nelson [this message]
2013-10-30 16:56           ` Daiane Angolini
2013-10-30 17:29             ` Otavio Salvador
2013-10-30 17:46               ` Eric Nelson
2013-10-30 17:51                 ` Otavio Salvador
2013-10-30 18:04                 ` Gary Thomas

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=527130D8.3070102@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=gary@mlbassoc.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.