> > in your v1 patch series you mentioned you do not have access to EMMC > to test. I am happy to test EMMC, but I had problems with the v2 and > v3 patches. > v2 dts did not compile and I was getting errors for the hdmi0 entries > like "Label or path hdmi0 not found". I assume I am missing patches. > After removing it compiles but the board does not boot. > > v3 patches don't work against 6.12-rc6/rc7 snapshot. The patch that > modifies the 5 plus dts fails. I again assume I am missing other > patches. > > If you have some info with which kernel or other modifications I can > use your patches, then I am happy to do some testing. If your primary focus is to only test eMMC support for the Orange Pi 5 Max, then apply the patches on top linux-rockchip for-next. https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/log/?h=for-next That generated DTB should be able to run against an older kernel since the Orange Pi 5 Plus already works. It's complicated since the HDMI Bridge support is in the pipeline for 6.13-rc1 but it goes through different trees.. The driver itself is merged into drm-misc next Where as the DTS updates are in linux-rockchip branch Also, regarding v3, I rebased on top of linux-rockchip for-next to include the updates for HDMI and GPU on the Orange Pi 5 Plus. For my development testing, I used Collabora's rk3588-test development branch, so all the needed patches were already in one place (since they test on a Radxa Rock 5B with the RK3588). https://gitlab.collabora.com/hardware-enablement/rockchip-3588/linux/-/commits/rk3588-test/?ref_type=heads So for v3, I had to first cherry-pick the Orange Pi 5 Plus changes from linux-rockchip for-next. Note: for v3 I held off on adding the USB 3 support for the Max, I was going to let the Orange Pi 5 Plus finish their USB 3 submission before trying to refactor the common DTS nodes. https://lore.kernel.org/linux-rockchip/20241025175415.887368-1-wens@xxxxxxxxxx/ > > Cheers, > Marco
