Several issues with the current visionfive 2 support:
* JH7110 Support is only in OpenSBI Master branch, (upcoming 1.3 release). So pin OpenSBI Revision to the commit that adds JH7110 Support otherwise reset etc does not work
* There are two variants of VisionFive2 and Star64 - 4Gb and 8Gb. StarFive's u-boot reads the eeprom on board to determine what variant you have, and modifies the loaded FDT it passes to the kernel with the correct Memory. Current U-boot scripts in meta-riscv do not do this, and thus all boards end up with the default 4Gb configuration. I've updated this for Star64, but needs testing on VF2
* Some of the addresses used in uboot for kernel/initramfs or fdt were different from upstream. Aligned the addresses with upstream StarFive.
As both Star64 and VisionFive2 are based on the same SOC, i've changed the machine configuration so we have a JH7110 SOC and VisionFive2 and Star64 inherit from this. Where appropriate in the recipies, I've changed to jh7110 instead of visionfive2
Finally, as the Star64 has different kernel/u-boot configs/dts files, i've pointed those at my repos for now, and will be upstreaming (assuming Starfive accept star64 related PRs). Once upstreamed, I'll submit a new PR here.
This also lays the groundwork for the new PineTab-V from pine64 which is due to be shipped in May.
Signed-Off-By: Justin Hammond <justin@dynam.ac>
At this point DTSes differ between d1/wip branch of the kernel
and corresponding branch of u-boot. Mangopi-MQ-Pro dts is missed in
u-boot part which leads to missing devices nodes (bluetooth in
particular). Sync dts and pin patch to mangopi only to not affect Nezha.
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
Use SOC name (Allwinner D1) instead of board name for
generic recipes.
Move board specific configuration to corresponding machine conf
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
Based on Nezha D1 machine config with addjusterd DTB configuration
and added wifi module driver.
Tested with core-image-(base|weston) on MangoPi MQ Pro rev 1.3:
- HDMI output/weston and wifi are working. USB-C ethernet detected but not
tested due to lack of HW.
Signed-off-by: Pavel Zhukov <pavel@zhukoff.net>
We don't need to specify OpenSBI in EXTRA_IMAGEDEPENDS to ensure it's
built and if we specify it we get circular dependencies with the u-boot
RSA signing code, so let's drop it.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
This is largely based on the beaglev code nbut tweaked to work with current
starfive kernel repositories and tweak to the board.
The kernel and rootfs boot with working network and graphics. The u-boot
binary builds but is as yet untested.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add baremetal-riscv32nf config for RISC-V32 machines without
floating point instructions (e.g. Hi3861)
Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com>
As we are in rapid dev phase, lets all use dev kernel
since older branches while work do not have all the latest
porting work
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This makes the main recipe PN same as the one in core, but gives it
starfive flavor in PV, this then becomes nice to include it via
PREFERRED_VERSION mechanism.
Additionally, this also means that it gets picked up in world builds for
beaglev and OE-Core recipe is not preferred, as of now, it tries to
build both, since they are seen as different packages by bitbake due to
different PN
Signed-off-by: Khem Raj <raj.khem@gmail.com>
do_deploy need to execute from sstate-cache when the build directory is
empty and system determines that there is no change to u-boot and it
can be reused from sstate, in this scenario deploydir needs to populate
properly, so we can not use WORKDIR in logic
Activate u-boot and opensbi only for beaglev-starlight-jh7100
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Fixes
NOTE: Multiple providers are available for virtual/bootloader (u-boot, u-boot-juno, u-boot-orangepi-i96, u-boot-poplar, u-boot-socfpga)
Consider defining a PREFERRED_PROVIDER entry to match virtual/bootloader
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>
