Somehow I am getting "Bad Linux ARM64 Image magic!" when loading the dtb file with the 5.6 kernel I compiled. However, the dtb file seems to work with my old 5.5 unstable kernel. With this, Indeed I get the 5 GT/s in lspci as well as a reasonable hdparm speed (860-880 MB/s with my Samsung 970 Evo) which is a clear improvement.
In the end, the end-user will just need to use a different dtb to get this change, right? So it's rather a question of deployment or making multiple DTBs available.
I assume that uboot has no way to determine the correct PCB version of the rockpro64 right? A similar problem exists with the pinephone that also needs different dtbs depending on the hardware revision and is being discussed here:
https://gitlab.com/postmarketOS/pmaports/-/issues/549
Edit: I got the 5.6 kernel working (the issue was that I had a zImage but u-boot needed an uncompressed image). I also got to test USB-C and USB 3.0 using a USB 3.1 to NVMe adapter but it does not work (USB-C does not recognize the drive, USB 3 renders "bad/missing sense data and get me just about 30 MB/s".
In the end, the end-user will just need to use a different dtb to get this change, right? So it's rather a question of deployment or making multiple DTBs available.
I assume that uboot has no way to determine the correct PCB version of the rockpro64 right? A similar problem exists with the pinephone that also needs different dtbs depending on the hardware revision and is being discussed here:
https://gitlab.com/postmarketOS/pmaports/-/issues/549
Edit: I got the 5.6 kernel working (the issue was that I had a zImage but u-boot needed an uncompressed image). I also got to test USB-C and USB 3.0 using a USB 3.1 to NVMe adapter but it does not work (USB-C does not recognize the drive, USB 3 renders "bad/missing sense data and get me just about 30 MB/s".