Hello @salas!
Thanks for the questions and your interest in testing! Let me clarify those points for you, as my initial explanation could have been clearer.
The driver for the Ethernet adapter needs to be compiled from source. You can find the repository here:
https://github.com/dante1613/Motorcomm-YT6801/
You're right, my board also has only one user-accessible M.2 NVMe slot. My "NVMe x2" note was a bit confusing. According to the board schematics, the RK3588S SoC provides two NVMe interfaces. On this board, one is routed to the M.2 slot, and the other is internally wired to the chip that drives the RJ45 Ethernet port. So, only one is available for storage.
You are correct that the USB-C port is used for power delivery. However, based on the schematics, the USB-C controller's pins are also multiplexed. Some are routed for DisplayPort Alt Mode (which then goes to the HDMI port), while the remaining data lines are intended for USB 3.0. I am still investigating this part, so I'm not 100% certain yet, but that's what the hardware layout suggests.
Thank you so much for offering to test with an eMMC card! That would be extremely helpful to confirm that it's working correctly.
To make it easier for you, I've just uploaded a pre-compiled image to the "Releases" section of my Armbian build repository. You can also build it yourself from the source, of course.
And yes, to confirm, all my work is for the Orange Pi 5 Pro variant.
Regarding your question about the kernel patch: it's currently based on the Armbian edge kernel tree (v6.16), which includes its own set of patches. It might not apply cleanly to a vanilla mainline kernel (like one from kernel.org) without some adjustments. However, the core DTS changes should be a great starting point for upstreaming the work once it's more mature. That's definitely the end goal!
Thanks again for your feedback!