diff options
| author | Mark Hatle <mark.hatle@amd.com> | 2024-06-04 16:51:04 -0600 |
|---|---|---|
| committer | Mark Hatle <mark.hatle@amd.com> | 2024-06-12 15:31:46 -0600 |
| commit | 2ad533417a52e37554f18434f3e4e12df68f6455 (patch) | |
| tree | 1d5e284c66fd11402f557d05b84fda878133ac75 /meta-xilinx-core/recipes-devtools/qemu/qemu-8.1/0002-python-qemu-rename-command-to-cmd.patch | |
| parent | 70dd9fbeb2316237667d5274b1ab4af9d3a7b7bf (diff) | |
| download | meta-xilinx-2ad533417a52e37554f18434f3e4e12df68f6455.tar.gz | |
various: Remove SOC_VARIANT, split versal and versal-net, add machine_features
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 <mark.hatle@amd.com>
(cherry picked from commit b472558db7d7da5fca63c498e45cac58ae8855fe)
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Diffstat (limited to 'meta-xilinx-core/recipes-devtools/qemu/qemu-8.1/0002-python-qemu-rename-command-to-cmd.patch')
0 files changed, 0 insertions, 0 deletions