summaryrefslogtreecommitdiffstats
path: root/meta-xilinx-bsp/conf/machine/vck-sc-zynqmp.conf
Commit message (Collapse)AuthorAgeFilesLines
* machine: Remove vck-sc-zynqmp machine confSandeep Gundlupet Raju2023-04-071-10/+0
| | | | | | | Remove vck-sc-zynqmp machine conf file from meta-xilinx-bsp layer. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* meta-xilinx-bsp: Align SOC_VARIANT with PetaLinuxMark Hatle2022-01-141-0/+2
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: Remove extra entries, already set by the included defaultsMark Hatle2022-01-141-20/+0
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-bsp: Covert ultra96-zynqmp and vck-sc-zynqmp from BOARD basedMark Hatle2022-01-141-4/+3
| | | | | | | Use the MACHINEOVERRIDES to add the BOARD name so that overrides elsewhere will work as expected. Eventually the overrides will need to be adjusted. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* Deprecate BOARD and BOARD_VARIANT supportMark Hatle2022-01-141-3/+4
| | | | | | | If the BOARD and/or BOARD_VARIANT is set, continue to allow this to work, however warn the user it is deprecated. 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-1/+1
| | | | | | | | | | 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>
* vck-sc-zynqmp.conf: Setting BOARD in MACHINE confJaewon Lee2021-07-141-1/+1
| | | | | | | Set BOARD in MACHINE conf as workaround for build scripts not using generic confs Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
* embeddedsw: Rework plm/pmu/psm firmware and Linux packagingMark Hatle2021-07-141-4/+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>
* 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: 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>
* meta-xilinx-bsp: remove redundant PREFERRED_PROVIDERMark Hatle2020-03-131-3/+0
| | | | | | | PREFERRED_PROVIDER_virtual/kernel and PREFERRED_PROVIDER_virtual/bootloader are normally set by machine-xilinx-default.inc. Only set these if necessary. 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: Remove default valuesMark Hatle2020-03-131-2/+0
| | | | | | Remove the default values, as they are already set by the soc include. 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>
* u-boot-xlnx:Update UBOOT-MACHINE to xilinx_zynqmp_virt_defconfig for all ↵Sai Hari Chandana Kalluri2020-02-071-1/+1
| | | | | | | | | zynqmp machines Update UBOOT MACHINE defconfig to xilinx_zynqmp_virt_defconfig instead of using custom machine specifc defconfigs. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* vck-sc-zynqmp: Machine configuration for vck190 system controllerSai Hari Chandana Kalluri2019-12-091-0/+39
Add machine configuration vck-sc-zynqmp for vck190 system controller with required setting of board specific yocto variables needed for compilation of bootloader, kernel and device-tree. - linux-xlnx is the kernel provider - u-boot-xlnx is the u-boot provider Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>