Now, I did find an HDMI driver for the RK3568, but unfortunately the HDMI IP is quite different between the two SoCs.
Before I start adding RK3588 support to that driver, I would like to make sure I’m not duplicating effort with Rockchip’s or Radxa’s engineers. Unfortunately while Radxa’s GitHub has most parts of the BSP uploaded, EDK2 / UEFI is not there (probably because work on customizing it for the Rock 5B hasn’t started yet), and the other 2 repositories are either not up to date, or they don’t have commit history.
I would therefore like to ask to have the EDK2 BSP sources uploaded to Radxa’s GitHub (assuming Radxa has received such code, and is allowed to publish it), just like u-boot sources currently are. I could then submit my changes on top of that as pull requests.
https://gitlab.com/rk3588_linux/ is uploaded by me since the rockchip sdk uses manifest whose folder structure cannot be reproduced on GitHub. The version I uploaded there is also a bit outdated. I’ll update uefi-monorepo to the latest release for you.
I just got some new info from Rockchip. They are working on HDMI right now, and will add serial number support in SMBIOS. They will also release a new version this month (unknown if above features will be included or not).
I was able to get FreeBSD running on Rock 5B using the uefi bootloader.
I used the master branch and I had to completely block the pci code otherwise the system hung on the pci initialization.
This code is for Rockchip development board and needs to be modified for Rock 5B
I used console.
As mentioned earlier, the HDMI initialization code is not in uefi yet.
I tested booting efi loader from efi partition and running FreeBSD OSes. It works. Only blue USB ports work and for some reason in USB 2.0 mode. All this requires study, the uefi code is very raw this is the Alfa version.
Could you please point to a HOWTO about building EDK2?
I got an errors during build attempt.
Thanks.
UPD: successfully built it under Debian… but had a errors under Gentoo.
UPD2: not such successfully as i thought
cd u-boot and re-packet uboot.img: ./scripts/fit-repack.sh -f uboot.img -d unpack/
./make.sh: line 35: cd: ../u-boot: No such file or directory
cp: cannot stat 'uboot.img': No such file or directory
cp: cannot create regular file 'unpack/uboot': No such file or directory
mv: cannot stat 'uboot_uefi.img': No such file or directory
****Build NOR FLASH IMAGE****
The u-boot directory is missing and i’m not sure where to find it, any clues? thx.
UPD3: Successfully built it after downloading u-boot and build-tools.
I am currently checking the work of EDK2 to run Armbian. And I found some interesting nuances.
The settings indicate a waiting time of 3 seconds, but in reality 10 seconds are used. a cursory analysis showed a line in which 10 seconds are indicated and if it is changed, the time changes. It is possible that the processing of variables from the general settings file is triggered before the reconfiguration is performed.
The RAM size is limited to 8 GB. Even if you change the settings in the general settings file, it doesn’t change anything.
@balbes-150
Yes, indeed the maximum memory size is 8Gbyte.
And a change in the configuration files does not affect this, it is not clear how to fix it.
I looked at the EDK2 code for rk356x, the RAM size is automatically determined there (I’m studying the commit that does it there), maybe there’s a chance to try using these algorithms for rk3588 as well?
I figured out the USB, found the reason.
p.s. By the way, I took your screensaver designs for Station and used them in my builds, I hope you don’t mind?