libffi 3.3-rc0 has much better RISC-V suppor then our single patch. Use
the RC release instead of a single patch.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
The mainline master GDB is very good now and even includes support for
debugging RISC-V Linux applications. Use the master branch until the
next GDB release is cut with all of this new support.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Update to the latest version of the RISC-V Proxy Kernel. This means we
are running an updated bbl.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
In a multi-BSP env u-boot may be provided by other BSP layers as well so
we need to be explicit about u-boot we need
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Now that QEMU RISC-V virt machine support is in master u-boot use the
mainline u-boot instead of a fork.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
And add SUMMAARY, DESCRIPTION field to provide imformation of
kernel bbfile.
Signed-off-by: pino-kim <sungwon.pino@gmail.com>
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
We are sort of hijacking OE-Core recipe here, so lets be careful and
make it such that it only happens for risv64, which makes a multi-BSP
scenario work again.
This repo seems to be rebasing :( so add rebaseable=1 so bitbake knows
about it
update to latest rev as of today
Signed-off-by: Khem Raj <raj.khem@gmail.com>
These policies enabled essential features like package management
and ssh server in images, additionally remove static libs and use
uninative
Signed-off-by: Khem Raj <raj.khem@gmail.com>
clang is not yet supported and when meta-clang is in
layermix things start to fail.
This patch patches by assuming the dependencies
and later adding them to bad recommendations so
they are dropped from runtime deps too
might not work with with dpkg backend
Signed-off-by: Khem Raj <raj.khem@gmail.com>
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>
