* initial ptv config
* Latest Updates:
* Move Charger Driver over to TI BQ25890 driver from mainline (and backport from 6.5 release)
* Fix up BQ25890 to work with the SC89890H which is in the PtV
* Drop vendor es8316 patches and backport es8316 patches from 6.5
* Update DT file for
- New Charger Driver, with battery and charger profiles derived from PT2
- Fix rfkill for BT/Wifi (was using incorrect GPIO and radio-type
- change hall sensors to emit SW_LID event
- add simple-battery profile from PT2 (needs a audit of used params tho)
- Fix Camera Flash Entry
- Fix backlight off by setting PullDown Mode on Backlight GPIO
- Start work on es8316 dt entry.
- add speaker_amp entry to turn on/off speakers when not used
- add audio routing and widgets based on PineBook Pro
* Update PtV kernel and new image layout specifically for PtV
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>
Currently meta-riscv does not parse unless meta-python is present.
Moreover, it does not appear that anything explicitly depends on
python3-pyruvate in the layer.
Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com>
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>
Latest version is causing QA errors e.g.
ERROR: lttng-tools-2.13.0-r0 do_package_qa: QA Issue: lttng-tools: ELF binary /usr/lib/lttng/libexec/lttng-consumerd has relocations in .text
lttng-tools: ELF binary /usr/bin/lttng has relocations in .text
lttng-tools: ELF binary /usr/bin/lttng-crash has relocations in .text
lttng-tools: ELF binary /usr/bin/lttng-relayd has relocations in .text
lttng-tools: ELF binary /usr/bin/lttng-sessiond has relocations in .text [textrel]
Signed-off-by: Khem Raj <raj.khem@gmail.com>
