[meta-xilinx] TUNE* in meta-xilinx

[Nathan Rossi]

Hi Philip,

The reason for the 'tune-zynq.inc' is due to the setting of defaults that are Zynq SOC specific (as opposed to board specific), you are correct though generally speaking it is just inheriting the main substance from its use of the tune-cortexa9. The main reason for it is to make it simpler to make a machine conf that targets a Zynq device, saving a bit of configuration duplication in machine conf files.

The meta-ti layer does a similar thing for their individual SOC Families. (http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/conf/machine/include).

In regards to the soc-family, if you look at the include in oe-core that is all soc-family really is, a MACHINEOVERRIDE. (http://git.openembedded.org/openembedded-core/tree/meta/conf/machine/include/soc-family.inc)

Regards,
Nathan

> -----Original Message-----
> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
> bounces at yoctoproject.org] On Behalf Of Philip Balister
> Sent: Thursday, August 15, 2013 4:51 AM
> To: meta-xilinx at yoctoproject.org
> Subject: [meta-xilinx] TUNE* in meta-xilinx
> 
> Can you explain why you creeate the ynq tune in meta-xilinx? It seems
> like you are still using the default coratexa9 tune features anyway.
> 
> I also had some people suggest using a MACHINEOVERRISE instead of
> soc-family.
> 
> Philip
> _______________________________________________
> meta-xilinx mailing list
> meta-xilinx at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx