On Wednesday, 30 August 2023 20:32:02 CEST Vagrant Cascadian wrote: > On 2023-08-30, Diederik de Haas wrote: > > On Wednesday, 30 August 2023 16:35:46 CEST Vagrant Cascadian wrote: > >> > I also recall seeing references to a `rk3568_ddr_1056MHz_v1.18.bin` > >> > file from https://github.com/rockchip-linux/rkbin/tree/master/bin/rk35. > >> > AFAIK that's only available as a BLOB? Is that file needed? And is it a > >> > problem if that's only available as a BLOB? > >> > >> If upstream u-boot requires that to work it is... more complicated. > >> > >> Looks like it does probably require it, based on the trustedfirmware > >> thread you linked to above. > > > > As mentioned above, AFAIK it's no different from rk3328/rk3399, but I'll > > ask. > If the rk3568*.bin is not actually required to build an upstream > arm-trusted-firmware, then it is not different! > > If the rk3568*.bin is required to build an upstream > arm-trusted-firmware, then it is different! > > The current arm-trusted-firmware and u-boot packages for rk3328 and > rk3399 do not require those or other blobs.
I asked and it *is* different ... and thus (a lot) more complicated. I thought it would be the same as rk3328/rk3399 as that also uses a DRAM init/ training. While that itself is true, "rk3328 and rk3399 can use U-Boot's open source dram init", while rk356x's dram init is not open source, but provided under the non-free (AFAICT, but IANAL) license provided here: https://github.com/rockchip-linux/rkbin/blob/master/LICENSE So it looks like you were right and `rkbin` needs to be packaged separately and then combined with the rest, which I think is all Free Software. I guess `rkbin` can be put in non-free-firmware, but I don't know in which archive area an u-boot package which uses/needs that should be placed. > live well, > vagrant You too :-)
signature.asc
Description: This is a digitally signed message part.
