[meta-freescale] [meta-fsl-arm][PATCH v2] imx-base.inc mxs-base.inc: Add imx MACHINEOVERRIDES

[Otavio Salvador]

On Wed, Jul 8, 2015 at 12:56 PM, Daiane Angolini <daiane.list at gmail.com> wrote:
> On Wed, Jul 8, 2015 at 11:41 AM, Otavio Salvador
> <otavio at ossystems.com.br> wrote:
>> On Wed, Jul 8, 2015 at 11:33 AM, Ann Thornton
>> <Ann.Thornton at freescale.com> wrote:
>>> It is true that mx6 can be used today but soon there will be mx7 and mx8 and
>>> the list will get longer.  Also qoriq and automotive will be added in which
>>> we will want to exclude from i.mx.  There are recipes, images, and
>>> packagegroups that currently don't need to check for the machine that will
>>> need to coming up and bbappends that will be needed to differentiate between
>>> machines. imx would be a convenience that will be useful in the near future.
>>> The alternative is a long list of i.MX machines.
>>
>> As I said, I understand the value of this addition and I think this
>> should go in. However I want to make sure people understand that this
>> will be rarely used. Several things will end with a huge list of SoCs
>> as this should be used ONLY when it is i.MX specific and globally
>> supported by all the SoCs.
>
> I'm not against including imx now. I think it does not hurt what we have today.
>
> However, meta-freescale is a perfect opportunity to really rework the
> SOC_FAMILY tree (a never used meta layer is the ideal timing to make a
> huge change on SOC_FAMILY as it's really needed.
>
> And this includes the discussion around packagegroup being part of the BSP.

I fully agree in this regard. This also needs to be discussed and I
think each of those items is worth a email thread.

Can you share your thoughts in the SoC family and package groups
issues in two emails?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750