We still use 1.13 for risv64, so cheat a little so we can re-use recipes
from oe-core to pretend to be 1.14
Signed-off-by: Khem Raj <raj.khem@gmail.com>
currently meta-riscv does not parse unless meta-oe is present.
It does not appear that anything explictly depends on openocd
in the layer.
Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
OE-Core disables it on riscv64 since go support is now in this layer it
makes sense to enable it in meta-riscv
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Alter the SRC_URIs to fetch 1.13 from the right fork.
Rename refreshed 0002-cmd-go-make-content-based-hash-generation-less-pedan.patch
so it does not conflict with oe-core go recipes
Fixes#114
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Latest glibc wants kernel 5.4+ ABI and linux-yocto is still at 5.2, so
until that switches to 5.4 lets pin to dev kernel which is 5.5+
Fixes#199
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Now that we are using U-Boot 2019.10 let's remove the uneeded patches
that have been merged into mainline u-boot.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Fix the ethernet compatible sting name with the 5.3 kernel device tree.
This restores u-boots networking access when using the 5.3 kernel.
This patch is taken from the mainline master u-boot but rebased onto our
current 2019.07 + 21 patches u-boot. Once 2019.10 is released we can
drop all of these patches.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Let's now use the defconfig for the HiFive Unleashed. We can still apply
any extra configs ontop with a config patch.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
No one is testing the 4.19 kernel and it probably doesn't work with the
latest OpenSBI work so let's just remove it from meta-riscv.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Now that we are using the newer glibc port and 5.2 kernel headers remove
the qemuricv32 compatible machine from the 5.0 kernel and add it to the
5.2 kernel.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
OE-Core has upgraded to the 5.2 kernel headers. This means that all RV32
software now requires a 64-bit time_t. Update the glibc fork to an
implementation that works in a 64-bit time_t. At the same time we can
revert the linux kernel patch.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
When building in a non CI env this all is not
needed as the user might accidentally end up losing all the build
artifacts that are not intendeed to. On CI systems its better to delete
it via extra step outside setup
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Now that we are using QEMU 4.1 we can use QEMU's -bios option and
-kernel option and remove the device loader.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Add the uEnx.txt file to meta-riscv to allow users to build OSTree
setups for the HiFive Unleashed. This is based on the original version
from Ricardo Salveti (@ricardosalveti).
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Let's swap to using a fitImage by default. At the same time let's update
the u-boot boot commands to handle all the image types and support
loading a uEnv.txt file.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Append causes IMAGE_FSTYPES to contaminate initramfs-based images, as
even when forcing it to be empty at the recipe level, it always shows up
after parsing.
Using += allows the recipe to set another value without being influenced
by the machine configuration.
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Wic file to be used with sota/ostree (meta-updater), as the source for
root needs to be provided by the otaimage plugin.
It can be maintained outside this layer, but having it maintained at the
official meta-riscv layer makes it a lot easier for users experimenting
with meta-updater.
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Based on the default u-boot machine configuration, useful for fitImage
support (known address for loading the device-tree).
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
The changes done by this bbappend are all specific to freedom-u540, so
change every override to be machine specific.
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
meta-multimedia depends on meta-python. I'm not sure why it's
necessary to add all the dependent layers in order, but if I don't do
this I get a bunch of exceptions during setup.sh that result in no
meta-python in my bblayers.conf and thus a non-functional bitbake.
setup.sh was already explicitly adding meta-python, so this patch just
adds it before meta-multimedia. That fixes the errors on my side.
Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
