[meta-freescale] [PATCH 18/24] reorg the qoriq include files
Otavio Salvador
otavio.salvador at ossystems.com.br
Mon Sep 28 04:40:44 PDT 2015
On Fri, Sep 25, 2015 at 7:49 PM, Bob Cochran <yocto at mindchasers.com> wrote:
> On 08/12/2015 06:22 AM, Zhenhua Luo wrote:
>> +MACHINEOVERRIDES .= ":qoriq-ppc"
>>
>
> I don't think this is what we want since I get the following:
>
> MACHINEOVERRIDES="e5500-64b:qoriq:t1:t1040:t1040rdb-64b:qoriq-ppc"
>
> And this means that the generic files under meta-freescale like
> init-ifupdown/qoriq-ppc/interfaces is overriding my machine specific
> interfaces file.
>
> I believe we want it to be like:
>
> MACHINEOVERRIDES="e5500-64b:qoriq:qoriq-ppc:t1:t1040:t1040rdb-64b"
>
>
> I propose we simplify things a bit and just do the following in
> qoriq-ppc.inc:
>
> MACHINEOVERRIDES =. "qoriq:qoriq-ppc:"
>
> and yank the MACHINEOVERRIDES specifier in qoriq-base.inc. I would do the
> same sort of thing in qoriq-arm.inc. This way, there would be less chance
> of these overrides moving around again later because their relocation tends
> to pop up as an occasional nuisance during builds.
I think the machine overrides could be used as we do in i.MX. We
merged i.MX and MXS in a single imx-base.inc file and control
everything using the SoC family.
In my point of view we ought to have a single .inc (qoriq-base.inc) to
handle ARM and PPC SoCs so people have the SoC family information in
the board files.
--
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
More information about the meta-freescale
mailing list