On Fri, 2019-09-27 at 10:12 +1000, Jonathan Gray wrote: > On Thu, Sep 26, 2019 at 12:28:56PM -0400, Kurt Miller wrote: > > > > I've been trying to get the rock64 to work with u-boot 2019.10rc4 > > with the help of solene@ and a motivated user with this board. > > (I don't have one to test with). The Rock64 is close to fully > > working with 2019.10rc4 u-boot but is experiencing a similar issue > > to what NetBSD has reported on the u-boot list. > > > > https://marc.info/?t=156888926600002&r=1&w=2 > > > > When booting miniroot66.fs with the u-boot TPL the install > > eventually fails with a kernel panic as seen below on > > solene@'s board. Using rkbin TPL the install completes > > and the resulting system appears stable in light testing. > > > > I have attached the diffs I'm using to the ports > > sysutils/arm-trusted-firmware and sysutils/u-boot. > > I modified the u-boot port to build idbloader with both > > u-boot TPL and rkbin TPL. > > It isn't clear what the license on rkbin is. It is binary only but does > it allow distribution?
Yea, there's no license at all and no matter how much digging I do, I can't find one. Mostly I was trying to point out that the rock64 board is having the same issues that NetBSD is having with the TPL layer in the forthcoming 2019.10 release and providing a way for people with the Rock64 board to verify it. I'm not sure if there's much I can do to get the TPL layer fixed but it would be great if the 2019.10 release could replace the 2017.09-rockchip-ayufan firmware that most people are using and doesn't work all that well on OpenBSD. Although I think the sysutils/arm-trusted-firmware change could go in now, since the BL31 layer for rk3328 has been confirmed to work by two people and it removes one more binary blob for that board. -Kurt
