| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|\
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
libxil warnings are obversed in multiconfig builds.
WARNING: mc:cortexa53-0-zynqmp-fsbl-baremetal:libxil-2023_sdt_experimental+gitAUTOINC+742a608800-r0 do_configure: QA Issue: libxil: invalid PACKAGECONFIG: rtc [invalid-packageconfig]
WARNING: mc:cortexa53-0-zynqmp-fsbl-baremetal:libxil-2023_sdt_experimental+gitAUTOINC+742a608800-r0 do_configure: QA Issue: libxil: invalid PACKAGECONFIG: qemu-usermode [invalid-packageconfig]
This is due to rtc and qemu-usermode was enabled for all targets in
MACHINE_FEATURES_BACKFILL, Hence disable rtc and qemu-usermode for
multiconfig targets by adding to MACHINE_FEATURES_BACKFILL_CONSIDERED
list in inclusion file.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Inclusion of security_flags.inc lead to a number of problems with the
baremetal distributions:
*ARM v8*
aarch64-xilinx-elf-ld: testA53.elf: error: PHDR segment not covered by LOAD segment
aarch64-xilinx-elf-ld: warning: testA53.elf has a LOAD segment with RWX permissions
*ARM v7*
arm-xilinx-eabi-ld: .../aarch32-xilinx-eabi/usr/lib/thumb/v7-a+fp/hard/crtbegin.o:
relocation R_ARM_THM_MOVW_ABS_NC against `a local symbol' can not be used when
making a shared object; recompile with -fPIC
The configuration that works:
export CFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types "
export CXXFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types "
export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-z,relro,-z,now"
export CPPFLAGS=""
Configuration that provides the warnings/errors:
export CFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types "
export CXXFLAGS=" -O2 -pipe -g -feliminate-unused-debug-types "
export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed "
export CPPFLAGS=""
The LDFLAGS was introdued by the security_flags.inc, the
SECURITY_CFLGAS:class-target ?= "" and
SECURITY_LDFLAGS:class-target ?= "" was supposed to prevent this, however
the cross compiler is built in the cross or canadian-cross or other
context and NOT target. Additionally the SDK environment is configured
in the nativesdk environment, so the default values may not match the
configured (target) compiler and CFLAGS. Removing security_flags.inc
resolves both of these issues, as the security flags don't really do
anything on a baremetal configuration, by default, anyway.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| | |
The special toolchains are really only applicable to a PetaLinux/Vitis
toolchain build.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Many of the settings/workaround have been replaced by changes in the upstream
OE-Core tclibc-newlib.
Additionally adding the DISTROVERRIDES with an append was potentially changing
-native recipes hashes. Move this only where needed to avoid this behavior.
Also sync settings with meta-petalinux, such as the buildhistory. This is now
moved to the local.conf file.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Certain settings appear to have an overall affect on recipe hashes. Use
petalinux (poky) distro as an example for base settings to ensure native
items built in one config SHOULD also be re-usable in the bareemetal config.
This has a side effect of NOT disabling static binaries in baremetal, but
this seems like a reasonable default, since there really isn't a concept
of dynamically loaded libraries. If necessary, the user can still override
this, but will need to specifically select class-target to do so.
Similarly SECURITY_CFLAGS and SECURITY_LDFLAGS are available by empty by
default. The default cflags/ldflags for baremetal usage are likely
different from a Linux system, so can be used in the future if requried.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| | |
Each Xilinx machine.conf should include the qemu file to ensure the correct
PREFERRED_PROVIDERS_qemu (and related) are defined properly.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| | |
The special toolchains are really only applicable to a PetaLinux/Vitis
toolchain build.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Many of the settings/workaround have been replaced by changes in the upstream
OE-Core tclibc-newlib.
Additionally adding the DISTROVERRIDES with an append was potentially changing
-native recipes hashes. Move this only where needed to avoid this behavior.
Also sync settings with meta-petalinux, such as the buildhistory. This is now
moved to the local.conf file.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Certain settings appear to have an overall affect on recipe hashes. Use
petalinux (poky) distro as an example for base settings to ensure native
items built in one config SHOULD also be re-usable in the bareemetal config.
This has a side effect of NOT disabling static binaries in baremetal, but
this seems like a reasonable default, since there really isn't a concept
of dynamically loaded libraries. If necessary, the user can still override
this, but will need to specifically select class-target to do so.
Similarly SECURITY_CFLAGS and SECURITY_LDFLAGS are available by empty by
default. The default cflags/ldflags for baremetal usage are likely
different from a Linux system, so can be used in the future if requried.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|/
|
|
|
|
|
| |
Each Xilinx machine.conf should include the qemu file to ensure the correct
PREFERRED_PROVIDERS_qemu (and related) are defined properly.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
|\
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|\|
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |\
| | |
| | |
| | | |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This will in-turn select the preferred version for various components to match
a given release.
It is advise that the user use the latest version whenever possible, but if
they are stuck on an older version of Vivado they may need to select the
older release.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We do not maintain support for hardknott so it is being removed
Signed-off-by: John Toomey <jtoomey@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We do not build, test or support gatesgarth in any of our layers so it
makes sense to remove this for the various layer.conf files
Signed-off-by: John Toomey <jtoomey@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These machines are no longer necessary, as the regular "generic" machine with
an alterantive DEFAULTTUNE should be used instead.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit a6d0eac8564fd02425b1260e58c552589586cf3d.
The toolchain itself has internal expectations of big-endian libraries
being available, even when building little-endian components. It uses
relative paths that include certain big-endian path locations.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
After moving from Xilinx specific cortex r5 turning file, the 5f is no
longer defined. Move to the now standard 'cortexr5' definition.
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>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The big endian variants as they are not used much anymore. This
preserved all of the little endian variants, and saves roughly
90 MiB of space and speeds up the build time considerably.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
(cherry picked from commit 77aea7992df133d04a5cef4d40878fbe372bfaa3)
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|/ /
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rename recipes from 2021.2 to 2022.1 as necessary.
Move internal references to 2022.1 (layer.conf and local.conf.sample)
Move kernel to 2022.1 branch, as well as various kernel modules.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
| |
| |
| |
| |
| |
| |
| | |
We do not maintain support for hardknott so it is being removed
Signed-off-by: John Toomey <jtoomey@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
We do not build, test or support gatesgarth in any of our layers so it
makes sense to remove this for the various layer.conf files
Signed-off-by: John Toomey <jtoomey@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
| |
| |
| |
| |
| |
| | |
These machines are no longer necessary, as the regular "generic" machine with
an alterantive DEFAULTTUNE should be used instead.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
| |
| |
| |
| |
| |
| | |
After moving from Xilinx specific cortex r5 turning file, the 5f is no
longer defined. Move to the now standard 'cortexr5' definition.
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>
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The latest embeddedsw components no longer need integration workarounds,
other then the couple of patches being applied. This simplifies eliminates
the custom do_configure, and simplifies the do_compile.
EXTRA_COMPILER_FLAGS is now different then the default version.
The versal defaults were also adjusted to match the expected output.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
Update the PMU machine and multiconfig files to match the current version
of the embeddedsw.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
standalone target
In case of open-amp, there are multiple version of open-amp. For case of
standalone, specify usage of meta-standalone-experimental layer for BSP
that is provided.
Signed-off-by: Ben Levinsky <ben.levinsky@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
standalone target
In case of libmetal, there are multiple version of libmetal. For case of
standalone, specify usage of meta-standalone-experimental layer for BSP
that is provided.
Signed-off-by: Ben Levinsky <ben.levinsky@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Default Link Time Optimization flags should contain Os option along with
flto and ffat-lto-objects flags to inline with the regular esw default
compiler flags.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
|