linux/meta-xilinx.git/conf/machine/include, branch master

meta-xilinx: Restructuring meta-xilinx to support multiple layers

2017-12-14T00:11:14+00:00

As discussed previously on mailing list, we are proceeding with layer restructuring. For rocko release we will have the following layers meta-xilinx ->meta-xilinx-bsp (current meta-xilinx) ->meta-xilinx-contrib In the subsequent releases we will add other layers from Xilinx meta-xilinx ->meta-xilinx-bsp (current meta-xilinx) ->meta-petalinux ->meta-xilinx-tools ->meta-xilinx-contrib This will provide one clone to get all the required meta layers from Xilinx for a complete solution, and the users can blacklist any layer which they don't want to use using bblayer.conf. This will enables us to help our vendors/partners to add their reference designs, board definitions etc. Recipe changes : * Move reference design zybo-linux-bd.bb to meta-xilinx-contrib * Move kernel patches realted to zybo-linux-bd-zynq7 board to meta-xilinx-contrib * Update README Signed-off-by: Manjukumar Matha

arch-microblaze.inc: Add 'frequency-optimized' tune

2017-12-06T23:45:16+00:00

With MicroBlaze v10.0 an additional AREA_OPTIMIZED value of 2 was added named Frequency. This optimization adds additional pipeline stages, and code can be optimized differently to achieve better tuned performance for these targets. The '-mxl-frequency' flag has been added to GCC (not in mainline) to enable specific tune optimizations for CPUs configured this way. Whilst this tune does not change any ABI the addition of the 'fo' package arch flag is added to allow for building both target optimized and un-optimized without mixing packages. Signed-off-by: Nathan Rossi Signed-off-by: Manjukumar Matha

arch-microblaze.inc: Add v10.0 conflict for bigendian

2017-12-06T23:45:16+00:00

As of v10.0 MicroBlaze is no longer configurable as a bigendian CPU. This change prevents the ability to configure the tunes of a MicroBlaze machine with v10.0 and bigendian. Signed-off-by: Nathan Rossi Signed-off-by: Manjukumar Matha

feature-microblaze-versions.inc: Rework and expand version conflicts

2017-12-06T23:45:16+00:00

This change removes the use of the python function to expand the TUNECONFLICTS definitions for version tunes. Instead this is replaced with hardcoded definitions. This is preferred due to reduced complexity of the python code as well as streamlining the include, this is also done to make the includes align better with expectations of tune includes in OE-Core. This change also moves the version conflicts for the reorder tune into arch-microblaze. Additional documentation is added to cover details of MicroBlaze CPU versions, and the change between different version formats. Signed-off-by: Nathan Rossi Signed-off-by: Manjukumar Matha

conf/machine: Add virtual/boot-bin dependency and set provider

2017-12-04T22:24:31+00:00

Add virtual/boot-bin to EXTRA_IMAGEDEPENDS for all Zynq and ZynqMP targets that use the deployed boot.bin from U-Boot. Set the default provider for virtual/boot-bin to the current virtual/bootloader provider. This handles the differing u-boot/u-boot-xlnx defaults and also sets up the default provider for consumers of machine-xilinx-default.inc. Signed-off-by: Nathan Rossi Signed-off-by: Manjukumar Matha

pmu-firmware: Fix the pmu-firmware provider

2017-11-29T13:02:49+00:00

Fix the issue while switching between different pmu-firmware providers Signed-off-by: Manjukumar Matha Signed-off-by: Nathan Rossi

tune-zynqmp.inc: Add default tune for multilib lib32 builds

2017-11-09T22:50:35+00:00

On ZU+ machines, we set the default tune for the lib32 multilib configuration.This allows users to select multilib by simply requiring conf/multilib.conf in their build setups. Signed-off-by: Cyril Chemparathy Tested-by: Bhargava Sreekantappa Gayathri Signed-off-by: Nathan Rossi Signed-off-by: Manjukumar Matha

tune-*.inc: Remove KMACHINE

2017-10-18T08:00:09+00:00

KMACHINE is now set by the kernel recipe, this is due to different kernels providing different kmeta sources which can provide one or more different KMACHINEs for a specific machine. Additionally linux-xlnx no longer uses KMACHINEs and is defaulted to the linux-xlnx trees defconfigs. Signed-off-by: Nathan Rossi

zynqmp-pmu-config.inc: Restrict BPNs further

2017-10-18T07:59:25+00:00

Restrict binutils and gcc to their -cross variant only. This prevents world targets from selecting zynqmp-pmu-gcc/binutils which require more dependencies. Signed-off-by: Nathan Rossi Acked-by: Alistair Francis

zynqmp-pmu-config.inc: Limit to specific recipes

2017-08-27T09:13:47+00:00

Limit the appending/enabling of the zynqmp-pmu BBCLASSEXTEND to only specific recipes which are used for the building of pmu-firmware. This is just binutils, gcc, newlib, libgloss and pmu-firmware itself. The limiting is done based on the BPN of the recipe, which is not provided as an override so the conditional is tested with an inline python function. This change removes the need for the extender class to be enabled globally which can conflict with certain recipes that were not written to be extended by the BBCLASSEXTEND mechanism. This change also improves the parse time avoiding the need to parse all recipes for both target and zynqmp-pmu. Add comment for the PACKAGE_EXTRA_ARCHS setting, so it is clear why it is set. Signed-off-by: Nathan Rossi Acked-by: Alistair Francis Tested-by: Alistair Francis