Re: SOC_FAMILY Rework

[Nikolay Dimitrov <picmaster@mail.bg>]

Hi Daiane,

On 07/09/2015 05:54 PM, Daiane Angolini wrote:
>> It does not work. The point of OVERRIDE is to make changes in a set of
>> SoCs and we cannot contaminate other BSP (Intel, TI, Samsung,
>> Qualcomm...)
>
> GPU is a SoC characteristic, and it's obvious it's the most important
> BSP piece on i.MX6 family. Instead of having a tree like:
>
> imx -> imx6 -> everysingle soc
>
> We could have something like:
>
> imx -> imx6-light -> ligh socs
> imx -> imx6-heavy -> heavy socs
>
> and, instead of list "everysingle soc" when setting GPU BSP, we can
> list only "light and heavy".
>
> The downside is to list "light and heavy" in packages for imx6
>
>
> I don't see how it will contaminate other BSP. I'm trying to stress
> the imx OVERRIDE just included.

This is an excellent example. The OVERRIDEs should generalize, not
specialize (although you can always interpret a root-leaf traversal as
a specialization :D). Detailed specialization will lead to OVERRIDEs
tree explosion while trying to express every single SOC feature on each
level of the tree.

If we try to express SOC features via OVERRIDE mechanism, it's imho
doomed.

Regards,
Nikolay