summaryrefslogtreecommitdiffstats
path: root/meta-xilinx-core/classes/xilinx-vars.bbclass
Commit message (Collapse)AuthorAgeFilesLines
* meta-xilinx-core: Move generic machines to be firmware-lessMark Hatle2024-09-131-9/+0
| | | | | | | | | | | | | Generic machines no longer depend on firmware (ESW) components. Thus they will now build a full Linux system, where possible, without XSCT or SDT modes. It is up to the specific machine.conf files to enable the correct build flow and that will enable the necessary firmware dependencies for the SoC. This also means HDF_MACHINES is no longer required. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* xilinx-vars.bbclass: Skip Xilinx license warning for per-package license flagAdrian Fiergolski2024-07-171-1/+1
| | | | | | | | | As described in the README.md, user can enable the 'xilinx' license on a per-package basis (i.e. 'xilinx_pmu-rom-native') in LICENSE_FLAGS_ACCEPTED. This patch updates the license flag check to reflect that possibility. Signed-off-by: Adrian Fiergolski <Adrian.Fiergolski@fastree3d.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com> (cherry picked from commit ded63a5cd9cf05bb91f75d79f9d3e42cce99c04e) Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* qemu-xilinx-system-native: Move pmu-rom enablement to recipeMark Hatle2023-04-101-0/+6
| | | | | | | | | | | | Setting the pmu-rom being required by QEMU within the machine.conf will cause the recipe's hash to change, which can cause a ripple effect causing other things to rebuild. Moving this to the recipe, and switching it on based on what licenses the user allows will avoid this conflict. Additionally add a warning message to the xilinx-vars.bbclass if the user has not enabled the license. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* conf/machine: Better document inheritence expectationsMark Hatle2022-11-101-0/+26
See the README files for specific requirements, but we have designed the machine configurations into an inheritance model. This module can be further broken into 3 distinct categories of variables: 1 - Variables that MUST be declared BEFORE inheriting the base machine 2 - Variables that SHOULD be declared BEFORE inheriting the base machine, as they are commonly overridden. (This will need continual review.) 3 - All remaining variables that should only be declared in the machine .conf file, and MUST be declared AFTER inheriting the base machine. Signed-off-by: Mark Hatle <mark.hatle@amd.com>