narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
leah has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
djrscally has quit [Ping timeout: 244 seconds]
leah has quit [Ping timeout: 260 seconds]
leah has joined #linux-amlogic
hexdump0815 has quit [Ping timeout: 268 seconds]
chewitt has joined #linux-amlogic
djrscally has joined #linux-amlogic
_whitelogger has quit [Ping timeout: 260 seconds]
_whitelogger_ has joined #linux-amlogic
jacobk has quit [Ping timeout: 276 seconds]
jacobk has joined #linux-amlogic
naoki has quit [Quit: naoki]
naoki1 has joined #linux-amlogic
naoki1 has quit [Client Quit]
<f_> Soo another thing :p
naoki has joined #linux-amlogic
<f_> This is what gets printed in aquaman UART logs:
<f_> > Load bl33 from eMMC, src: 0x00094200, des: 0x01700000, size: 0x00085200, part: 0
<f_> aml log : R1024 check pass!
<f_> And this is what gets printed in lepotato logs:
<f_> > Load bl33 from eMMC, src: 0x00050200, des: 0x01000000, size: 0x000eca00
<f_> Do you notice something odd?
<f_> "0x01700000 != 0x01000000"
<f_> I didn't really take a look at bl2_load_images much in bl2, I merely just thought "must be it" and moved on before.
<f_> But there *is* a check for secureboot. Specifically, if secureboot is enabled, storage_load always loads images to 0x01700000. Else, the usual load address is honoured
<f_> storage_load is the one that takes care of printing what it loads, too..
<f_> I bet they probably overlooked that one
<f_> or something else
<f_> And like.. they only do this for the BL* images
<f_> The FIP header is loaded at the usual address but they then memcpy to 0x1700000 :p
<f_> storage_load(0xc000,0x1400000,0x4000,s_fip_header_d900981e);
<f_> memcpy(0x1700000,0x1400000,0x4000)
<f_> BTW, has anyone tried using gxl FIP format on gxbb?
<f_> I seem to remember that gxbb BL2 seemed to have some handling of gxl's FIP format
<f_> well, at least what I remember is under some circumstances it would print "New fip structure!" over UART, just like what gxl usually does.
<f_> > if (something_fip == L'\x87654321') {serial_puts("New fip structure!\n");} < is present in both gxbb and gxl bl2
naoki has quit [Quit: naoki]
paulk has quit [Ping timeout: 268 seconds]
paulk has joined #linux-amlogic
jacobk has quit [Ping timeout: 260 seconds]
jacobk has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
ldevulder has quit [Quit: Leaving]
ldevulder has joined #linux-amlogic
ldevulder has quit [Quit: Leaving]
jacobk has quit [Ping timeout: 276 seconds]
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 260 seconds]
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 260 seconds]
konsgn has quit [Ping timeout: 252 seconds]
naoki has joined #linux-amlogic
djrscally has quit [Ping timeout: 272 seconds]