| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
| |
This patch updates the COMPATIBLE_MACHINE and DTBFILE
variables to compile esw use cases for cortexr5 processor
on versal platform.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
| |
Some of the components have been moved to internal configuration layers
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Following the example of base.bbclass in OE-Core, a new COMPATIBLE_OS
variable is defined. Similar to COMPATIBLE_MACHINE, it is a regex that
can be used to declare TARGET_OS string compatibility on a per-recipe
basis. Either the distro configuration or the recipes themselves will
need to inherit this class.
By default the class assumes we're building a Linux based system, and
thus any recipe who has not declared compatibility is compatible with
Linux. The default compatible field was copied from bitbake.conf to
ensure there are no surprised.
Additionally, enable the usage of this class throughout
meta-xilinx-standalone layer.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
|
| |
meta-xilinx-standalone is only for baremetal work. Theoretically the
newlib items can be used on other configurations, so move the microblaze
newlib/libgloss work into meta-xilinx-bsp. This mirrors how other
microblaze specific work has been handled.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The deocupling device-tree repo does not currently work with
machines like the zcu102-zynqmp, while the default repo does
work fine.
Set overrides for the decoupling working machines, while keeping
the REPO as it was by default for other machines to avoid this
error.
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
This patch updates the COMPATIBLE_MACHINE and DTBFILE
variables to compile esw use cases for cortexr5 processor
on ZynqMP platform.
This patch also updates the TUNE_CCARGS in the cortexr5-zynqmp.conf
file as per baremetal requirements.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
|
| |
|
|
| |
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
| |
|
|
|
|
|
| |
cortexa72 processor machine name changed from cortexa72 to coretexa72-versal
update the naming convention in the recipes for the same.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
|
| |
|
|
|
|
|
| |
This patch updates the COMPATIBLE_HOST and COMPATIBLE_MACHINE
and DTBFILE variables to compile esw use cases for cortexa72 processor.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This layer has been used as testing for the decoupling effort
hence there was (and still is) code that needed to be cleaned up
in general.
Put #TODO on things that are still left to do, either clean up
code, move machine confs to the bsp layer or remove the
deprecated pmu-firmware recipe and handle dependencies correctly
by bitbake'
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
There was a typo in the patch that installed the psu_init code
which initially tried to install files on the /var directory.
Since this is a baremetal component, there is basically no
convention on where files should be installed, for now
to comply a bit more with bitbake, install these files on
includedir to fix the install-vs-shipped issue.
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
| |
|
|
|
| |
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
| |
zynqmp-pmu to microblaze-pmu
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Distro Changes:
When building a multilib, we need to disable configsite cache. Otherwise
the system will fail to generate the SDK as there are no configsite entries
due to newlib based multilibs.
Recipe Changes:
gcc - globally disable multilib configuration
- Disable Linux specific configurations (EXTRACONFFUNCS)
gcc-cross-canadian - enable multilib on a recipe specific basis
libgcc - add a noop override to do_multilib_install to avoid Linux specific
multilib processing
newlib - arm/v6+m/nofp and arm/v8-m.base/nofp do not have newlib trap
implementations. libgloss contains these, workaround by
disabling builtin trap syscall handler.
- misc workarounds for multilib installs
libgloss - Allow MLPREFIX for newlib dependencies
meta-toolchain - adjust to install only the items we want/need
packagegroup-newlib-standalone-sdk-target - new pkggroup for the
custom baremetal SDK to select the right set of packages
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
| |
zynqmp-pmu to microblaze-pmu
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
|
recipes-bsp
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
