| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Add new metal-xilinx-vendor layer which supports vendor specific
machine configuration files, device-tree, kernel, platform-init etc.
2. Moved below vendor machine conf files, dt and related configs from
meta-xilinx-bsp and meta-xilinx-contrib to meta-xilinx-vendor layer.
- microzed-zynq7.conf
- minized-zynq7.conf
- picozed-zynq7.conf
- zedboard-zynq7.conf
- zybo-zynq7.conf
- zybo-linux-bd-zynq7.conf
- ultra96-zynqmp.conf
3. Obsolete qemu-zynq7, s3adsp1800-qemu-microblazeeb, v350-versal and
vc-p-a2197-00-versal from meta-xilinx-bsp layer. Users should use
zynq-generic.conf for zynq7000 qemu boot should be functionally
equivalent to qemu-zynq7.
4. Add new MAINTAINERS.md file and move maintainers, Mailing list and
Patches content from meta-xilinx-* README.md to MAINTAINERS.md file.
5. Updated README.md file for supported board machines files in
meta-xilinx-bsp, meta-xilinx-contrib and meta-xilinx-vendor layers.
6. Disabled old drm kernel patches for zybo-linux-bd-zynq mahcine in
meta-xilinx-contrib layer as these patches doesn't apply on 5.x
kernel, if we don't hear from patch submitter we will remove these
patches from meta-xilinx-contrib layer.
7. Removed drm kernel cache metadate for zybo-linux-bd-zynq7 machine
as these configs are already available in xilinx_zynq_defconfig.
8. Fixed build issue for u-boot by changing
PREFERRED_PROVIDER_virtual/bootloader from u-boot to u-boot-xlnx.
9. Add meta-xilinx-vendor to bblayers.conf.sample
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@xilinx.com>
Signed-off-by: Mark Hatle <mhatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
populate_sdk_ext step"
This reverts commit 51e48cc7acd766a6d84dbcc65d7b64de6f5d707e.
linux-firmware, linux-firmware-ti-bt, and petalinux-image-minimal
now build successfully.
Signed-off-by: Vishal Patel <vishal.patel@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
PACKAGE_ARCH should not be MACHINE_ARCH, unless a specific override is
being used for compatibility.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
No reason to set any microblaze defaults, unless we're actually building
for microblaze.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Adjust configurations, and users of the generic configuration. The TUNE must
be set BEFOER the inclusion, otherwise there is no way to dynamicly generate
the correct MACHINE_ARCH.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
armrm override is now replaced by armv7r and armv8r overrides. Adjust
recipes to match the new usage.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
This was missed in the prior move of the components to meta-xilinx-standalone
layer.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Manual fixes for overrides syntax changes.
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
| |
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
| |
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
| |
Modify TUNEFILEPATHS to latest directory structure followed in core.
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1096936
Some recipes may require board specific items, such as DTB. Even in a
generic build, we need to use BOARD_ARCH so we do not have duplicate
packages generated that have different contents.
Additionally if the BOARD is not specified MACHINE could appear twice, this
can cause processing errors.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1100158
Previously the final order of the MACHINEOVERRIDES was effectively:
zynqmp_graphics:board_variant:board:soc_variant:soc:aarch64:armv8a:cortexa72-cortexa53:machine
The correct order should be least important to most important:
aarch64:armv8a:cortexa72-cortexa53:zynqmp_graphics:soc:soc_variant:machine:board:board_variant
This change accomplishes that by adjusting the order of the .= / =. of the
MACHINEOVERRIDES values. This changes the order of a few standard requires,
adjusts how the zynqmp_graphics is added, and changes the order of the
soc/soc_variant settings.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
Setting FPGA_MNGR_RECONFIG_ENABLE default to 1 and not dependent on a
feature. At the time of this patch, this flag defaulting to 1 will
enable CONFIG_OF_CONFIGFS and CONFIG_OF_OVERLAY in kernel (it is on in
default configs in xilinx kernel) and enabling packaging wiring for
extra hdfs in fpga-manager-util
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
IMAGE_FEATURES should only control which package are getting included into the
image, it shouldnt control configuration/compile options. Keeping the
fpga-manager IMAGE_FEATURE but also using fpga-overlay DISTRO_FEATURE to
set FPGA_MNGR_RECONFIG_ENABLE which controls config options
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1096936
TOPDIR is only used to find the file to copy in the case of a multiconfig
build. However, even in this case the value of TOPDIR does not effect
the resulting build. Exclude this variable to avoid unnecessary
rebuilds of firmware in the eSDK.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
meta-xilinx-tools and bootgen produced a version called 'fsbl-<machine>',
adjust the name to match expectations.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Match the behavior of the pmu, psm, and plm firmwares. Set the default
deployment directory, filename, and dependencies for the soc-zynq and
soc-zynqmp systems. FSBL is only present on thse two systems.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
The restructure of the code missed the filename structure, the filenames
used by meta-xilinx-tools were intended to be the correct ones.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
Inserting a '-' in between board and boardvariant to align with the
format of soc and soc family
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
Previously machine override for a soc variant was SOC_VARIANT appended
to SOC_FAMILY. A '-' was included in between to align with how versal
handles machine overrides. Updating machine overrides to match this
format
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
| |
Removing the need to prepend a '-' to SOC_VARIANT for versal variants
for ex. '-ai-core'
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
| |
Fixing arch variables, removing SOC_ for BOARD_ARCH and
BOARDVARIANT_ARCH variables
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introducing an include file to add levels of hiearchy to PACKAGE_ARCH,
namely BOARD and BOARD_VARIANT
To use this, future confs will need to have the following line:
require conf/machine/include/xilinx-board.inc
Along with BOARD/BOARD_VARIANT definitions
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
| |
Default versal SOC_FAMILY is changed to "prime" from "s80"
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
|
|
|
|
|
|
| |
Set default PREFERRED_PROVIDER for qemu as qemu-xilinx within
machine-xilinx-qemu.inc. This eliminates the need to use PNBLACKLIST within
local.conf
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
| |
MACHINE_ESSENTIAL_EXTRA_RDEPENDS"
This reverts commit ee6d2b039501f63098831bbff141a9d1ef1ae645.
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
| |
Adding device-tree to MACHINE_ESSENTIAL_EXTRA_RDEPENDS for all xilinx
machines, this will install dtb/dtbo files into the rootfs.
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
For Linux based builds, it should be set to sysv. This will result
in the system using a supported hash type. (GNU hash is not supported
on Microblaze., so sysv will be used instead.)
For baremetal, set the value to "". This will result in no value set,
and the system will use the compiler and linker default.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
All xilinx BSPs that support qemu should use the machine-xilinx-qemu.inc
file. So move all references to the -multiarch extension into that
location.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The various Xilinx FPGAs may have more then one CPU type including
cortexr5, microblaze and regular ARM Cortex CPUs.
Adding a new soc-tune-include.inc will allow the machine to choose a
default tune, and then the correct matching tune will be loaded.
In a perfect world this wouldn't be required, but doing it this way
permits us to target specific optimizations or CPUs in the soc.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Any soc overrides belong in the soc configuration files.
Also move UBOOT_SUFFIX and UBOOT_ELF defaults into the
meta-xilinx-default, as well as specific soc settings in each soc file.
This results in the ability to override the value in multiple places
based on load order:
local.conf (user setting)
machine.conf (machine setting)
soc-....inc (soc setting)
machine-xilinx-default.inc (the actual default)
Each step uses ?=, so if the previous step hasn't set it that level will
define it's default if necessary.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
Move the soc specific contents into the soc configuration file.
Adjust the PACKAGE_EXTRA_ARCHS append to a more generic method for setting
the SOC_FAMILY and SOC_VARIANT package arch.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
Remove the default values, as they are already set by the soc include.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
cortexr5f includes vfp3-d16 support. Enable this and hard float.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|