| Age | Commit message (Collapse) | Author |
|---|
|
Machines: Move baremetal machines to meta-xilinx-standalone
Layers:
- Add new meta-xilinx-standalone-experimental
This layer may require components that may not yet be available to the
general public. It will contain various experiemntal integration work.
- meta-xilinx-standalone
This layer should be functional and contain the necessary items to build a
baremetal toolchain that can use libxil (replacement to libgloss) from
the Xilinx embeddedsw components. (Note, libxil is NOT built as part of
this work!)
The layer also contains the buildable components for the various firmware
components required to startup various Xilinx FPGAs.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
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>
|
|
Changing arch-armv8.inc to arch-armv8a.inc to match upstream name change
Signed-off-by: Jaewon Lee <jaewon.lee@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>
|
|
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>
|
|
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>
|
Mark Hatle
Alejandro Enedino Hernandez Samaniego
Jaewon Lee
Sai Hari Chandana Kalluri