summaryrefslogtreecommitdiffstats
path: root/meta-xilinx-bsp/conf/machine/zynqmp-generic.conf
Commit message (Collapse)AuthorAgeFilesLines
* Initial restructure/split of meta-xilinx-bspMark Hatle2022-01-141-85/+0
| | | | | | | | | | Create a new meta-xilinx-core, move core functionality to the core, keeping board specific files in the bsp layer. zynqmp-generic changed from require <board> to include, so if meta-xilinx-bsp is not available it will not fail. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* zynqmp-generic.conf: Remove KERNEL_DEVICETREERaju Kumar Pothuraju2022-01-141-1/+0
| | | | | | | | | | | As per the new kernel-fitimage changes in honister it is first adding the dtb from KERNEL_DEVICETREE and then dtb from device-tree.bb file. Which is leading to boot issue using the fitimage in petalinux flow. Disabling the KERNEL_DEVICETREE variable to add only dtb from device-tree.bb file(system.dtb). Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com> Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* manual changes for overrides syntax fixesSai Hari Chandana Kalluri2021-09-281-1/+1
| | | | Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Convert to new override syntaxSai Hari Chandana Kalluri2021-09-281-4/+4
| | | | | | | | | | 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 <chandana.kalluri@xilinx.com>
* ultra96-zynqmp/zynqmp-generic: Specify the ultra96 so BOARD can select itMark Hatle2021-09-281-0/+7
| | | | | | | | | | Move the ultra96-zynqmp.conf into the zynqmp-generic (via a require). This approach can be used for other board specific overrides if necessary. Move MACHINE_FEATURES to the generic zynqmp-generic file, as that is requried to make a superset. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* Revert "zynqmp-generic.conf: Adding MACHINE_FEATURES for ultra96"Mark Hatle2021-09-271-1/+0
| | | | This reverts commit de5e93d2e23e3a3ff084f5f03563dcde5c2b7c65.
* zynqmp-generic.conf: Adding MACHINE_FEATURES for ultra96Raju Kumar Pothuraju2021-09-271-0/+1
| | | | | | | Appending MACHINE_FEATURES for ultra96 "usbgadget wifi bluetooth mipi" Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com> Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* *generic.conf: Using += for MACHINE_FEATURESJaewon Lee2021-07-141-1/+1
| | | | | | | Using += for MACHINE_FEATURES to allow addition to MACHINE_FEATURES in confs using += and _append Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
* *.conf: use weaker assignment for UBOOT_MACHINERaju Kumar Pothuraju2021-07-141-1/+1
| | | | | | | | Using weaker assingnment for UBOOT_MACHINE to update this value in petalinux without _forcevariable. Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* embeddedsw: Rework plm/pmu/psm firmware and Linux packagingMark Hatle2021-07-141-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <mark.hatle@xilinx.com>
* Cleanup QB_MACHINE for xilinx machinesSai Hari Chandana Kalluri2020-12-221-1/+0
| | | | | | | Pick correct QB_MACHINE name for each of the machine from qemuboot-xilinx.bbclass. Remove QB_MACHINE from machine.conf Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Adding BOARD and BOARD_VARIANT level hierarchyJaewon Lee2020-12-221-0/+1
| | | | | | | | | | | Going to generic machine confs, we can no longer use machine overrides for specific machine changes. Adding BOARD and BOARD_VARIANT level hierarchy for packaging for zynqmp/zynq/versal generic machines confs. BOARD and BOARD_VARIANT must be set accordingly to use these hierarchy levels properly Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
* versal-generic.conf:zynqmp-generic.conf: Add ↵Raju Kumar Pothuraju2020-10-231-0/+2
| | | | | | | | | MACHINE_ESSENTIAL_EXTRA_RDEPENDS variable only for specific machines. Add MACHINE_ESSENTIAL_EXTRA_RDEPENDS variable for zynqmp and versal platforms. Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* machines: Remove default SERIAL_CONSOLES_CHECKMark Hatle2020-04-031-1/+0
| | | | | | | | | | | | | | | | | | By default the machines should not check and remove declared consoles that are not available on first boot. It's up to the user to add this to their build configuration. The recommended user behavior is: SERIAL_CONSOLES_CHECK = ${SERIAL_CONSOLES} but the side effect of this is that if the device configuration changes after the first boot, the additional devices will not be available. (Note, this may result in warning messages with getty unable to connect to certain devices.) Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* machines: Allow the user to override SERIAL_CONSOLESMark Hatle2020-04-031-1/+1
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* machines: Move from SERIAL_CONSOLE (deprecated) to SERIAL_CONSOLESMark Hatle2020-04-031-1/+1
| | | | | | | Usage of 'SERIAL_CONSOLE' was deprecarted in late 2013. Move to the using 'SERIAL_CONSOLES', where the format is slightly different. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* *-generic.conf: Add QEMU support to each of the generic BSPsMark Hatle2020-03-171-1/+72
| | | | | | | Additionally ensure that all u-boot defconfigs use the common configuration for each platform. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: cleanup qemu referencesMark Hatle2020-03-171-2/+0
| | | | | | | | | | Move IMAGE_CLASSES setting to common machine-xilinx-qemu.inc, also add preferred provider for the xilinx specific qemu components. Adjust the various BSPs to remove duplicate references to these and non-Xilinx versions of qemu. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: rename machine-xilinx-override to xilinx-soc-family.incMark Hatle2020-03-131-1/+0
| | | | | | | | | | The machine-xilinx-override is really just an extension to the standard soc-family.inc file. So rename this, move the include of soc-family.inc to this file, move the include to the soc includes to each soc file, and finally adjust the machines to remove machine-xilinx-override as it's no longer necessary. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: Rename soc configuration masquerading as a tune fileMark Hatle2020-03-131-1/+1
| | | | | | | The tune files were really soc configuration files. Tune files should only specify toolchain flags that affect optimiation and abi. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* -generic.conf: Add generic machines for Zynq and ZU+Manjukumar Matha2019-08-151-0/+15
Add generic machines for Zynq and ZU+. These are used to build sstate-cache and feeds for respective machines Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-06 11:35:18 +0000