Re: [meta-fsl-arm-extra][PATCH] nitrogen6x.conf: Allow kernel provider override

[Eric Nelson <eric.nelson@boundarydevices.com>]

Hi Otavio,

On 10/30/2013 07:10 AM, 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.
>

I'm not sure I understand why. It seems perfectly reasonable to me
to build a new kernel recipe and use it, while retaining other
information from the machine configuration.

I'm thinking specifically of a user who may have a custom kernel
tree with pin-muxing based on their usage.

> If we start allow all kind of override in machine configuration it
> loses its meaning and complicates the support.
>
> Eric? comments?
>

I'm not sure I understand the concern. This seems pretty
straightforward. The default is there, but a user can
over-ride it.

Regards,


Eric