On Thursday, 31 August 2023 14:14:38 CEST Christopher Obbard wrote: > This is the case for some other devices (e.g. rk3588) currently where there > is support in U-Boot mainline but there is no arm-trusted-firmware support > _or_ DDR bringup in U-Boot as yet.
I do follow the linux-rockchip ML and it looks like kernel 6.6 is getting rather interesting for rk3588 support. I'm less 'in the loop' wrt rk3588 on u-boot and TF-A although I did post this: https://forum.pine64.org/showthread.php?tid=14432&pid=117094#pid117094 I do expect for TF-A support to land upstream for rk3588 (eventually), but do you know (or suspect) that DRAM init will be open sourced too? Note that I don't _fully_ understand these things, so if what I'm saying doesn't make any sense, feel free to point that out :-) > It'd be great to get Debian running on some of this more recent Rockchip > hardware I'm currently working on that. Although it's initially for Quartz64 Model A+B and PineTab2 (all rk3566) devices, I don't see why it wouldn't be usable for rk3588 devices too as (long as) they're all arm64. AFAICT (now), I can just make 1 image as the only differentiator would be the specific u-boot binary that needs to be put in place and I can just make an instruction to `dd` the right u-boot binary onto sector 64 of the image file. Thus https://github.com/Kwiboo/u-boot-build/#flashing with `/dev/mmcblk0` replaced by my image file. https://salsa.debian.org/diederik/linux/-/tree/pine64/master-next is the kernel I (currently) use, which is based (and periodically rebased up) on the Debian kernel (with the intend to 'upstream' it to Debian's kernel when that's appropriate). Cheers, Diederik
signature.asc
Description: This is a digitally signed message part.
