It's because of the Raspberry Pi foundation we have this perception that embedded Arm chips are like general purpose desktop computers that run Linux desktops. The original Pi SoC was designed for TV set top boxes, STB's hence the loopy booting from GPU which was likely part of some obfuscated secure boot chain to thwart STB hackers. The Pi was a throw away hobby toy based on a chip Broadcom was going to scrap so they got a dumpster deal. It took a lot of effort for the community to fully reverse the Broadcom SoC and bring all the Pi hardware to mainline.
Desktop computer was a reach. Even for BeagleBone.
I am surprised RK3566 and RK3568 still don't have good UEFI-EDK2 support.
RK3588 has great UEFI-EDK2 support. I wish somebody would backport RK356x and RK3399 boards....
The pace of development is too fast. We don't need more aarch64 CPU but better support. RISC-V adds to the mayhem.
Like we need that...
The Open Source Hardware Dream.
Software exists from the vendor, but it’s not open source and/or not part of Linux mainline.
Hence the effort to develop an open source (and mainlined) alternative.
Whether this is a good use of effort and/or whether you believe the vendor should be doing the Linux development or not, and/or whether they should open-source their proprietary drivers, will depend on your personal views.