linux/meta-xilinx.git/meta-xilinx-bsp/conf/machine/zc1254-zynqmp.conf, branch master

meta-xilinx-bsp: Move XSCT bsps to meta-xilinx-tools

2024-09-04T14:01:06+00:00

Signed-off-by: Mark Hatle

various: Remove SOC_VARIANT, split versal and versal-net, add machine_features

2024-06-04T23:00:14+00:00

SOC_VARIANT has been remove, we are now only using the YP standard SOC_FAMILY configuration. The defined families are: zynq, zynqmp, versal and versal-net. Our decision of breaking up versal-net from versal, is based on the SoC CPU changes from cortexa72/r5 to cortexa78/r52, thus we're treating it as a different SoC family. In order to capture the individual capabilities that we used to handle via SOC_VARIANT, we have defined the following features (some may have been previously defined): - mali400 (zynqmp eg and ev) - vcu (zynqmp ev) - rfsoc (zynqmp dr RF capabiltiies) - aie - (versal ai & premium) - vdu - (versal ai) SOC_VARIANT_ARCH and SOC_FAMILY_ARCH are now obsolete and replaced by MACHINE_ARCH. This is based on the guideline that any recipes that use MACHINE_FEATURES should be MACHINE_ARCH specific. Signed-off-by: Mark Hatle

meta-xilinx-bsp: Align SOC_VARIANT with PetaLinux

2022-01-14T23:37:05+00:00

Signed-off-by: Mark Hatle

meta-xilinx-bsps: Add board-style overrides to select correct components

2022-01-14T23:37:05+00:00

Add the override expected by device-tree and other recipes to each machine. Signed-off-by: Mark Hatle

meta-xilinx-bsp: Remove extra entries, already set by the included defaults

2022-01-14T23:37:05+00:00

Signed-off-by: Mark Hatle

meta-xilinx-bsp: Convert all BSPs to use the generic configs

2022-01-14T23:37:05+00:00

Signed-off-by: Mark Hatle

manual changes for overrides syntax fixes

2021-09-29T06:06:42+00:00

Signed-off-by: Sai Hari Chandana Kalluri

Convert to new override syntax

2021-09-29T05:12:06+00:00

This is the result of automated script (0.9.0) conversion: oe-core/scripts/contrib/convert-overrides.py . converting the metadata to use ":" as the override character instead of "_". Signed-off-by: Sai Hari Chandana Kalluri

*.conf: use weaker assignment for UBOOT_MACHINE

2021-07-14T21:57:15+00:00

Using weaker assingnment for UBOOT_MACHINE to update this value in petalinux without _forcevariable. Signed-off-by: Raju Kumar Pothuraju Signed-off-by: Sai Hari Chandana Kalluri

embeddedsw: Rework plm/pmu/psm firmware and Linux packaging

2021-07-14T21:49:19+00:00

In order to allow standalone (meta-xilinx-standalone), XSCT (meta-xilinx-tools), and future items to work in the same way the recipes have been restructured. A *-firmware recipe will generate the firmware and stage it to do_deploy. A *fw recipe will take the deployed version and package it for the Linux side of things. This allows the firmware generation to be easily extended without requiring packaging knowledge. Similarly packaging can be extended for alternative boot/upgrade mechanisms as required. In all cases, the MACHINE configuration will specify the default way the components are to be built, along with the names of the item in the deploy directory. The PLM/PSM/PMU_IMAGE_NAME is the name for the generated firmware. PLM/PSM/PMU_DEPLOY_DIR is the path to the constructed firmware. This along with the IMAGE_NAME above can be used to specify the location of an externally generated set of firmware. Addtionally the dependencies for building the plmfw/psmfw/pmufw can be changed easily using PLM/PSM/PMU_DEPENDS and PLM/PSM/PMU_MCDEPENDS. The former specifies dependencies in the same multiconfig, while the later allows the component to require another multiconfig to have finihed. The system has a referenced default, if multiconfig is enabled it will automatically use it, otherwise it will try to use the recipe in the main configuration. (This will fail unless meta-xilinx-tools is available.) Also two multiconfigs hve been implemented: versal-fw and zynqmp-pmufw They can be enabled using BBMULITCONFIG += "zynqmp-pmufw" or versal-fw. Signed-off-by: Mark Hatle