Thanks for commenting. Maybe this is useful
RISC-V Star64 JH7110: Power Up the Display Controller with U-Boot Bootloader: https://lupyuen.codeberg.page/articles/display3.html Am 2. Sept. 2023, 23:24, um 23:24, Mark Kettenis <mark.kette...@xs4all.nl> schrieb: >> From: Robert Palm <develo...@robert-palm.de> >> Date: Sat, 02 Sep 2023 18:34:14 +0200 >> >> Hi Mark, >> >> as you presumably already know, it seems there exists a first >> version for hdmi support: >> >https://patchwork.kernel.org/project/linux-riscv/cover/20230801101030.2040-1-keith.z...@starfivetech.com/ >> >> Does this mean a new driver for the vf2 like rkdwhdmi would be >> "needed" to support hdmi in OpenBSD? > >In principle support in u-boot would be enough to give OpenBSD a >framebuffer console. > >> Am 3. Aug. 2023, 15:41, um 15:41, Mark Kettenis ><mark.kette...@xs4all.nl> schrieb: >> >> Date: Tue, 01 Aug 2023 23:11:43 +0200 >> >> From: Robert Palm <develo...@robert-palm.de> >> >> >> >> I own a VF 2 version 1.2a and can successfully install / boot the >> >machine. >> >> >> >> The inner network port (dwqe1) works at 100 full duplex and >receives >> > >> >> ipv4 via DHCP. >> >> >> >> The outer port currently doesn't seem to get an ip, but gets >active >> >> and in full-duplex 100. >> > >> >There is a reason why the VisonFive 2 isn't listed as supported on >> > >> > https://www.openbsd.org/riscv64.html >> > >> >There are stll bugs and... >> > >> >> It seems a lot depends on proper .dtb files (which kind users >shared >> >> with me). >> > >> >Yes, and it is a total mess. The device trees are being changed as >> >support for the board is upstreamed in the Linux kernel. But their >> >firmware still provides their hacked up device trees that they use >> >with their hacked up vendor kernel. >> > >> >> How did you create the .dtb files ? >> > >> >They're build from: >> > >> >>https://github.com/starfive-tech/linux/tree/JH7110_VisionFive2_upstream >> > >> >But that branch keeps getting rebased, and they changed things >again, >> >so PCIe stopped working. So I've decided to stick with what I have >> >for development and wait until the device tree bindings have been >> >accepted by the Linux maintainers. Meanwhile, if you're running >> >-current on one of these, expect your setup to break at some point >in >> >the future. >> > >> >> Do you plan to update them ? >> > >> >The plan is to provide usable device tree in ports as soon as there >is >> >an upstream Linux version that only needs minor patching. >> > >> >> They seem to be quite different to the "official" starfive >releases >> >> (which don't work for me with OpenBSD). >> > >> >As I said, that's just the typical unmaintainable vendor crap. >> > >> >> Do you plan more work on the VF2 ? >> > >> >I probably consider it done as soon as I finc the remaining dwqe(4) >> >bugs have been found and fixed. >> > >> >Cheers, >> > >> >Mark >> >>
