naoki has quit [Read error: Connection reset by peer]
naoki1 has joined #u-boot
naoki1 is now known as naoki
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #u-boot
mckoan|away is now known as mckoan
BoergeSt has joined #u-boot
sszy has joined #u-boot
naoki has quit [Quit: naoki]
naoki has joined #u-boot
naoki has quit [Quit: naoki]
naoki has joined #u-boot
naoki has quit [Client Quit]
naoki has joined #u-boot
naoki has quit [Client Quit]
naoki1 has joined #u-boot
naoki1 is now known as naoki
mmu_man has joined #u-boot
prabhakalad has quit [Ping timeout: 252 seconds]
MyNetAz has quit [Remote host closed the connection]
prabhakalad has joined #u-boot
enok has quit [Ping timeout: 244 seconds]
naoki has quit [Ping timeout: 252 seconds]
MyNetAz has joined #u-boot
mmu_man has quit [Ping timeout: 272 seconds]
mmu_man has joined #u-boot
sbach has quit [Ping timeout: 265 seconds]
sbach has joined #u-boot
<sng>
qschulz i was able to reproduce this issue on the qemu arm64. I had not noticed that my u-boot build had enabled lwip, which is why I was not able to reproduce this
<sng>
qschulz the lmb_fix_over_lap_regions() function is not handling one of the overlap conditions
<sng>
qschulz https://paste.ack.tf/94a515 - scenario A is being handled, but not scenario B. which is why the print shows up
<sng>
qschulz I will send the fix which handles the second scenario as well
MyNetAz has quit [Remote host closed the connection]
BoergeSt has quit [Quit: WeeChat 4.1.1]
BoergeSt has joined #u-boot
BoergeSt has quit [Client Quit]
BoergeSt has joined #u-boot
<sng>
qschulz also, I think the values of pxefile_addr_r and kernel_addr_r in the px30 config file needs to be swapped
enok has joined #u-boot
enok71 has joined #u-boot
enok has quit [Read error: Connection reset by peer]
enok71 is now known as enok
enok71 has joined #u-boot
enok has quit [Client Quit]
enok71 is now known as enok
MyNetAz has joined #u-boot
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #u-boot
ungeskriptet has quit [Remote host closed the connection]
persmule has quit [Remote host closed the connection]
<Tartarus>
Yes, v2025.01 doesn't have TPL init'ing SDRAM on rk3399 so it doesn't boot there
<Tartarus>
v2025.04-rc1 should
persmule has joined #u-boot
<sjg1>
I suppose I'm a bit confused. Yes v2025.04-rc1 starts, but does not print a banner
<sjg1>
If labgrid can't see the banner, it should just fail. I suppose that is what is happening, so then it restarts U-Boot and starts running the next test
<Tartarus>
So what does the actual boot log look like then?
<sjg1>
But there is definitely some sort of lab bug here somewhere, because if it can't see the banner, it should just complain
<Kwiboo>
a revert of af518a1dfe637cb4dc486d7a832585e4a48bc970 will probably get kevin/bob back to working
<Tartarus>
Kwiboo: Would that impact console not existing until much later on in boot?
Stat_headcrabbed has joined #u-boot
<Kwiboo>
ahh, sorry I tought it did not boot at all because of that commit, should read all before typing, board_early_init_f() in gru.c mention something about a delay and we get garbage serial output otherwise
<Kwiboo>
so with current "# CONFIG_BOARD_EARLY_INIT_F is not set" for bob/kevin such delay does not happen and the result may be missing banner on console?
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
Stat_headcrabbed has joined #u-boot
Stat_headcrabbed has quit [Client Quit]
<eballetbo>
I don't think this is a u-boot problem, but I'm having a problem booting an aboot image, the thing is that using an old u-boot I'm able to boot the system but using a newer u-boot I'm getting ( [ 0.449812] Initramfs unpacking failed: invalid magic at start of compressed archive ) This looks a kernel problem to me but I don't really know what magic does the old u-boot that makes it to work. The only thing that I change is
<eballetbo>
u-boot.
<eballetbo>
any idea what could be the problem?
<sng>
qschulz I believe that earlier, with the local scope of the lmb memory maps, this was not showing up
<sng>
qschulz I am not sure about this scenario of the download working after having interrupted it once. I haven't tried it on my end tbh
<eballetbo>
actually reverting these two commits fixed the issue for me
<eballetbo>
1b1ffda42071 ("boot: android: Fix ramdisk loading for v2 header")
<eballetbo>
da3447d09fa0 ("android: Fix ramdisk loading for bootimage v3+")
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
dsimic has quit [Ping timeout: 244 seconds]
dsimic has joined #u-boot
enok has joined #u-boot
<mkorpershoek>
eballetbo: do you reproduce this on master as well ?
<eballetbo>
I did with 2025.01, will try master tomorrow
<eballetbo>
(need to drop)
<mkorpershoek>
Also, do you know what version is your bootimage?
<eballetbo>
v2
<mkorpershoek>
ok, we can continue tomorrow.
<mkorpershoek>
feel free to ping me so that I can help, I'm probably the one that got those patches merged so if there is an issue we should sort it out