Age | Commit message (Collapse) | Author |
|
git cherry-pick b80c6d4
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Set layer compat to dunfell and gatesgarth
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Based on performance measurements as well as recent presentations at ELC
it is believed the correct default should always be -O2. -Os should only
be selectively used per module instead of default.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
The key is using COMPATIBLE_HOST to declare, for each recipe, which
OS they are compatible with. This is a regex, so we need to
carefully specify the arch/vendor wild cardscomponents so that we match
only the OS parts.
In the distro configuration, default to the standard Linux HOST_SYS
setting.
In the various baremetal recipes (or esw class) set the specific
compatibility to allow baremetal recipes to build.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
compatibility"
This reverts commit 4f3edb6da405ffff957d6f194bc7db7bdd9f1463.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
This patch updates the CMAKE_SYSTEM_NAME variable for freertos.
Signed-off-by: Anirudha Sarangi <anirudha.sarangi@xilinx.com>
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
This patch adds new distro xilinx-freertos for compiling
esw freertos use cases in yocto flow.
Signed-off-by: Anirudha Sarangi <anirudha.sarangi@xilinx.com>
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Commit fb62f071f94fc45444357865665fec6d4b11d1ca added a workaround for a
mingw runtime issue, but did not label it as mingw32 specific. QEMU may
cause failures in some non-linux configurations.
Make this option mingw32 specific, and also avoid qemu making the
dependency on the missing mingw32 component explicit.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Both xilinx-standalone (w/ lto) and xilinx-standalone-nolto need to use
a common set of system settings. A few settings were missed in the
merge of the decoupling work. Move these to the common settings file.
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>
|
|
The embeddedsw expects -DARMR5 when building for a cortexr5. Enable this
globally within the distribution configuration. This ensures that the
tunings remain generic.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
There is a bug upstream, which explains this problem further [1],
but basically when there are several multiconfigs they could be
polluted with the events of each other, in this specific case,
a multiconfig that uses the DISTRO=petalinux which itself inherits
the buildhistory class will cause an error on the multiconfig that
builds xilinx-standalone, while the correct fix is t fix this upstream
I have not had the time to do that, and currently an easy and not very
conflicting workaround is to simply inherit the builhistory class on
the xilinx-standalone DISTRO as well.
[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=13071
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Instead of using ESW_CFLAGS for the optimization level, fall back to the
default Yocto Project method of 'FULL_OPTIMIZATION' and
'SELECTED_OPTIMIZATION'.
FULL_OPTIMIZATION is moved from -O2 to -Os, the other components retain
the default Yocto Project setitng of '-pipe ${DEBUG_FLAGS}'.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Some builds may require LTO, while others do not want it. The LTO components
are only enabled when using the esw.bbclass and the xilinx-standalone distro.
A second xilinx-standalone-nolto was added specifically to provide a default
where LTO was disabled.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
We need to increase the layer priority for meta-xilinx-standalone,
otherwise its not possible to set a branch for decoupling on the DTG
flow, since meta-xilinx-internal overrides our changes
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
When running gcc built for xilinx-standalone using mingw sdk machine, it
would throw an error saying the winpthread dll was missing. this is
because in tclibc-newlib, TOOLCHAIN_HOST_TASK was being overwritten and
omitting nativesdk-packagegroup-sdk-host which pulled in the appropriate
package nativesdk-mingw-w64-winpthreads. Manually adding the following
to TOOLCHAIN_HOST_TASK to bypass this issue:
nativesdk-qemu-xilinx
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Alejandro Enedino Hernandez Samaniegoi <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>
|
|
Unify the meta-xilinx-bsp and meta-xilinx-standalone layers
by moving the machine confs to the BSP layer and keeping the
standalone layer as a DISTRO layer
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
to its name
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Due to the large amount of recipes required from the ESW repo,
include a pattern to parse recipes without requiring a directory
per recipe
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Changing arch-armv8.inc to arch-armv8a.inc to match upstream name change
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
Update XILINX_RELEASE_VERSION to v2020.1
Signed-off-by: Varalaxmi Bingi <varalaxmi.bingi@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Previously the GCC configure options per MACHINE were inside the
MACHINE.confs, this was wrong since the BSPs are contaminated
by the DISTRO options and it should be the other way around.
Avoid this contamination by using MACHINE OVERRIDES along with
DISTRO OVERRIDES to get the required gcc and binutils configure
options by the Xilinx SDK
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
dependencies
For the cross canadian toolchain we need to have both the libc.a and libgloss.a.
We add them to the LIBC_DEPENDENCIES which are wired in core to be added
to the sdk via the TOOLCHAIN_TARGET_TASK variable
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Instead of overriding the append, we need to append the override.
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Since we need specific configuration for the SDK toolchain, we need
to override the configuration coming from oe-core, this configuration
needs to be per MACHINE.
Use GCC_CONFIGURE_COMMON_XILINX_STANDALONE to define the default config
shared amongst MACHINES, and use a GCC_CONFIGURE_<MACHINE> variable to
append to this common configuration options on each MACHINE that we
want.
Use the same procedure for binutils
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
for versal components like plm, psm-firmware
versal-mb.conf supports versal SOC standalone component builds such as
plm, psm-firmware. It provides required configuration to use microblaze
toolchain needed for the builds.
|
|
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Update u-boot, kernel, ATF, QEMU, pmu-firmware, multimedia recipes for
2019.2 release.
The patch also upgrades gcc microblaze, newlib and libgloss versions.
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
components
This layer is meant to augment Yocto/OE functionality to provide a
toolchain to build standalone components for Xilinx architectures.
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|