VioletGiraffe

@Long-Johnny
Rather than to say 'never solved', we (as a community) need to learn about *uboot*
https://docs.u-boot.org/en/latest/
https://linux-sunxi.org/U-Boot
this is practically the *BIOS* for these little boards that we use and that u-boot boots Linux - it is the boot loader.
Once you / we find a way to pass that memory size to *uboot*, then it is a matter of learning to configure a file e.g. edit a DTS overlay to encode the memory size.
And there you have it, a fully supported board.
But that that step/procedure may have to be manually done by hand.
In that sense, once one figures this out, one can manually configure these boards for any arbitrary memory size.
 

There are actual two ways. You can use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh KERNEL_CONFIGURE=yes which will continue to assemble an image with the modified config file which is more user friendly.
On the other hand there is code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh kernel-config which will export the modified kernel config into code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } output/ folder and stops there which is more developer friendly.
If you chose latter route you need to move the exported config to userpatches or overwrite the one in code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } config/kernel/. Once you done that simply execute code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh and the modified config will be used.

Hi,
 
=y means the driver/functionality is directly compiled into the kernel
=m means it will be built and made available as kernel module
 

@VioletGiraffeI don't remember the changes I made, but if its status is marked as disabled in dts, then probably yes. For the module, if you are ok to do your own build, you can use "./compile.sh BOARD=orangepizero3 BRANCH=current kernel-config" to modify kernel configuration and then proceed with building the image. Current branch will give you 6.6 kernel, you can use edge if you want to use 6.7 kernel as well. Once you get it to work, feel free to raise a PR

TV out might work, its not tested though. The DTS changes for the same was part of HDMI changes that were merged. But there is no audio support added yet so you will not have any audio.

Welcome @VioletGiraffe, thanks for joining the forum and letting us know you can test

Must be quite a journey reading the whole thread for the history now, well done 

In terms of video out, I don't think there has been any specific focus on it and as @Stephen Graf may not be currently supported, but keep an eye out for updates here.
 
I think mainline is good to build off currently, there are no big PRs pending except the Overlay work which may not interest you as it's GPIO related. The options vary based on what OS you're using, but I generally use Edge Kernel, Debian OS and XFCE Desktop options for testing. I can be more specific if you need

Unfortunately I don't think there has been any work on the TV out.  Not even Zunlong supports TV out.  From the Zunlong zero3 manual:
 
 Analog audio and video
output interface
Supported, it can be used to connect headphones to
play music, or connect to TV through AV cable to
output analog audio and video signals (Android
system only).
 
Using the main build for Armbian would thus be as good as any place to start.