On Wed, Jul 13, 2016 at 7:21 AM, Ting Liu <[email protected]> wrote: >> - please don't include soc-family.inc and instead use MACHINEOVERRIDES (I >> am preparing same change for i.MX) > > [Liu Ting-B28495] why? could you please elaborate? I did not see any > discussion on the Maillist. Do I miss something?
We are working, for the i.MX team, in a way to reduce code duplication for BSP of similar SoCs. So the approach we are following uses: Author: Otavio Salvador <[email protected]> Date: Fri Jul 1 12:12:55 2016 -0300 machine-overrides-extender.bbclass: Automatically set extend the MACHINEOVERRIDES This allow to grouping of different settings for similar platforms. To use the class, specify, for example: MACHINEOVERRIDES_EXTENDER_soc = "group1:group2" Change-Id: I4a7dcd353b8bedf9d8f213827d7de768783c3d5d Signed-off-by: Otavio Salvador <[email protected]> Mixing SoC family seeing and MACHINEOVERRIDES makes it quite difficult to understand so, pior this change, I did commit be092137d7908e01e7a94b5dc35bb9af84bc08cf Author: Otavio Salvador <[email protected]> Date: Fri Jul 1 11:15:40 2016 -0300 Convert SOC_FAMILY to MACHINEOVERRIDES The SOC_FAMILY is an indirection which makes the understanding, from OpenEmbedded versed developers and users, more difficult. Instead of using the SOC_FAMILY indirection which is rarely used, we now move to the MACHINEOVERRIDES mechanism as this is in fact what is in use. Change-Id: Ic6e58b79bdc990ac853c87761c3fff635786e4e5 Signed-off-by: Otavio Salvador <[email protected]> I should be sending this patchset soon but it does reduce a lot code duplication and I believe QorIQ will end reusing this once this lands on the layer. -- 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 -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
