<f_>
and at the same time I also rebased the amlimage patch
<f_>
I want to send these patches ASAP, I'm wondering what to do wrt amlimage: I could either resend it as part of the patch series, or just have a note in the cover letter that it depends on that
<f_>
narmstrong / Kwiboo ^ thoughts?
<lvrp16>
I need to switch le potato to your tree eventually. Amlogic bl2 black box so annoying.
<lvrp16>
I can't add lzma
<f_>
even for us at postmarketOS it's soooooo annoying
<lvrp16>
Sooooooooo
<f_>
that was part of my motivation for working on this :)
<lvrp16>
The latest release from them does not even load from nor properly.
<lvrp16>
I am using a bl2 from 2018
<f_>
wut, they have actual releases now?
<lvrp16>
I am taking it from their bsp
<f_>
Hopefully you won't need to switch to my tree though..
<f_>
.. once this will all land upstream once and for all (for gx)
<lvrp16>
The 2018 version is the only one that works from nor...
<lvrp16>
After much trial and error with black boxes...
<f_>
yeah I also tend to pick rather old versions of BL2 for reversing
<lvrp16>
It is like the Mali blobs from 2017...
<lvrp16>
Before mesa
<f_>
typically the older ones have more debug printf's than the newer ones
<f_>
and other debug things and such
<lvrp16>
God what a waste of time black box binaries are
<f_>
Absolutely..
<f_>
in other news .. been a bit silent but I did work on aml_ddr.fw some more lately
<f_>
it seems this thing has been mostly written from scratch or something
<f_>
with a little bit of help from u-boot imx8m sources .. because it would seem that it's very similar to A311D ddr-wise
<f_>
but this thing is just a whole mess in its own :>
<f_>
Also there's this ddrs->fast_boot thing I have no idea what it is for
<f_>
Like, in timing.h it's:
<f_>
unsigned> char> fast_boot[4];// 0 fastboot enable 1 window test margin 2 auto offset after window test 3 auto window test