| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Lopper comes from meta-virtualization, the python modules are required by
it and the related changes.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
PACKAGE_ARCH is not relevant to native recipes, remove this
do_configure is not used as the package is simply loading in a binary. Skip
this as an optimization
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This patch will define the device-tree required memory and uart params.
Due to recent board/board_variant and machine changes in yocto caused
this issue.To work with these new changes we need this.
In plnxtool.conf we will define the default values but if we set board
value in that case due to the changes in new microblaze-generic.conf file
the plnxtool.conf changes will not work.
Signed-off-by: Varalaxmi Bingi <varalaxmi.bingi@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Enable SYSTEMD hooks by default as DISTRO_FEATURE is systemd.
Enable sysvinit hooks only if DISTRO_FEATURE is sysvinit.
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Neel Gandhi <neel.gandhi@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Move the pmu-rom to pmu-rom-native recipe. The ROM is only deployed in the
standard directory for qemu-xilinx usage when required by a zynqmp-generic
system.
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>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add the override expected by device-tree and other recipes to each machine.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Change rootfs to cpio.gz, and runqemu will automatically load it as an initrd
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use the MACHINEOVERRIDES to add the BOARD name so that overrides elsewhere
will work as expected. Eventually the overrides will need to be adjusted.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
All machines are now capable of heterogenous configuration by selecting
the correct DEFAULTTUNE and other values.
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>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Each inherited BSP must set a MACHINEOVERRIDES and PACKAGE_EXTRA_ARCHS to
ensure that various overrides can be set along the way. The general format
for this is (in the caller):
require conf/machine/<inherited machine>.conf
The callee is responsible for adding to the MACHINEOVERRIDES and
PACKAGE_EXTRA_ARCHS. It does this by setting the following at the beginning
and end of the file, respectively.
MACHINEOVERRIDES =. "${@['', '<machine>:']['<machine>' != '${MACHINE}']}"
...
...
PACKAGE_EXTRA_ARCHS_append = "${@['', ' <machine_arch>']['<machine>' != '${MACHINE}']}"
where <machine> is the <machine>.conf file the line appears in;
<machine_arch> is the <machine>.replace('-', '_') (matching MACHINE_ARCH) if
the machine file was used by itself.
The MACHINEOVERRIDES uses =. or .= everywhere in the Yocto Project. Doing it
via =. in the load order ensures in order evaluation.
PACKAGE_EXTRA_ARCHS is set via 'append', but needs to be the last operation
to ensure that we are always added AFTER anything we include along the way.
Effectively this is a late binding evaluation.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the BOARD and/or BOARD_VARIANT is set, continue to allow this to
work, however warn the user it is deprecated.
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>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Cleanup some of the override syntax.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The board config matches the default config, it's not needed.
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>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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>
|
| | | |
| | | |
| | | |
| | | | |
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>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The new generic will be the default microblaze configuration, with the other
remaining temporarily for compatibility.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
As per the new kernel-fitimage changes in honister it is first adding
the dtb from KERNEL_DEVICETREE and then dtb from device-tree.bb file.
Which is leading to boot issue using the fitimage in petalinux flow.
Disabling the KERNEL_DEVICETREE variable to add only dtb from
device-tree.bb file(system.dtb).
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@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>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
For some reason build no longer works in a separate directory. It fails
with a message indicating the system was unable to load 'the cache'.
Until this is resolved, set B = S.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
README file was updates, as uninative no longer needs to be separately
included.
The meta-xilinx-setup needs to be updated from ?= to =, as a distro (poky)
may configure it's own default TOOLCHAIN_HOST_TASK, which causes the wrong
items to be loaded.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The user may have specified additional host tools for the toolchain, allow
this -- as a new meta-xilinx-toolchain was introduced for the cut-down
prebuilt toolchain.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rename a mispelled patch name
Add a patch that defines the microblaze syscalls.
Disable stack-protection, as it is not supported on Microblaze at this
time.
Add a patch to resolve an undefined gcc internal, that is not enabled
on microblaze.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These tools require knowledge of the stack direction, since we are cross
compiling they are unable to detect the stack growth direction so it must
be defined in the m4 macro.
It turns out the direction was already set, but defined as
'microblaze' instead of 'microblaze*' which caused problems on little
endian.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Using symver related functions results in:
| ../git/lib/crypt-static.c:32:1: error: symver is only supported on ELF platforms
| 32 | SYMVER_crypt;
| | ^~~~~~~~~~~~
Microblaze does not support these functions at this time, so fall back
to the older approach to resolve this issue.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|