We document using oe-core and bitbake but the environment was setting
for poky, this fixes that, plus riscv64 is not enabled as default tatget
in poky where as it is in oe-core
Signed-off-by: Khem Raj <raj.khem@gmail.com>
They result in linking errors, -fstack-protector-strong wants libssp
libdrm errors when using -fstack-protector-strong
drm@sha/xf86drmSL.c.o: relocation R_RISCV_HI20 against `__stack_chk_guard@@GLIBC_2.27' can not be used when making a shared object; recompile with -fPIC
libdrm errors when using fortify options
rm@sha/xf86drm.c.o(.text+0x3ce2): unresolvable R_RISCV_CALL relocation against symbol `strdup@@GLIBC_2.27'
For now just disable the whole shebang
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Since we do not have kmeta infrastructure for kernel
the qemu builds fail due to this file not being there and
qemu sort of forcing it.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
RISC-V support is now included in the OE-Core NSPR package, this patch
is no longer required so let's remove it.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
bbl_payload requires the kernel deployed artifacts (e.g. vmlinux) during
compile time in order to generate the final bbl binary, so add
virtual/kernel:do_deploy as a do_compile dependency to get the
dependency task in the expected order.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
beecrypt is no longer included in OE-core (since fb8ca4225f beecrypt:
remove) so remove our dependency on it.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
libgpg-error was updated in oe-core to 1.28, which already includes the
patch adding risc-v support.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
It is useful to be able to override kernel's provider or version from
local.conf.
For qemuriscv64 machine move PREFERRED_* variables before qemu.inc,
because it sets PREFERRED_PROVIDER to linux-yocto.
Signed-off-by: Taras Kondratiuk <takondra@cisco.com>
bbl has a machine specific payload (vmlinux), so it should be
machine-specific too. Otherwise riscv-pk build for different machines
will collide.
Signed-off-by: Taras Kondratiuk <takondra@cisco.com>
Machine-specific packages (like Linux kernel) should have
machine-specific PACKAGE_ARCH that is obtained from MACHINE_ARCH. This
allows to separate their build artifacts in TMPDIR.
Currently all RISC-V machines override MACHINE_ARCH and artifacts for
machine-specific recipes collide. For example kernels of both
qemuriscv64 and freedom-u540 machines will be deployed into the same
$D directory.
Remove MACHINE_ARCH override and set tune PACKAGE_ARCH via
PACKAGE_EXTRA_ARCHS.
Signed-off-by: Taras Kondratiuk <takondra@cisco.com>
This is a workaround for the naming of the console.
This doesn't work around the issue for systemd based builds.
Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
Modify freedom-u540 machine to boot off of sd card by default.
Note that there is a bug with the U540's SPI controller that
makes this painfully slow.
Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
The "default" boot mode at the moment is to bundle a ramdisk image in
the kernel and mount root in a ramfs.
This image is suitable to bundle with the kernel but it has minimal
features and basicly just boots.
Signed-off-by: Mirza Krak <mirza.krak@endian.se>
