<sjg1>
Tartarus: Sorry, was busy...so you think I should redo it to add BOOT_DEVICE_VBE and BOOT_DEVICE_ELF, or something like that?
behanw has quit [Quit: Connection closed for inactivity]
<Tartarus>
Yes, something like that I think
<sjg1>
Tartarus: OK I'll rework that, should be fine. Did you see the stuff about adding a phase to FIT? I think I've figured out how to do this with a single config but have not implemented it yet
<Tartarus>
I saw but didn't really read yet, I figured I'd put v2 through a size-test and see what stuck out
<sjg1>
Tartarus: OK, well I think I might rework it based on my new idea before sending v2
<Forty-Bot>
sjg1: I'm going to send a patch to make it depend on PHYS_64BIT, unless you think there's a better config
GNUtoo has quit [Ping timeout: 258 seconds]
GNUtoo has joined #u-boot
<LeSpocky>
sjg1: I also got that, actually I did not investigate further but disable CONFIG_CLK_K210 O:-)
<LeSpocky>
there are lots of warnings when building on i386 while there are none on amd64 :-/
<LeSpocky>
I'm not sure how much effort should be put into this, nobody uses i386 in production anymore, I just happened to have that old laptop lying around
GNUtoo has quit [Ping timeout: 258 seconds]
GNUtoo has joined #u-boot
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
hanetzer has quit [Ping timeout: 265 seconds]
hanetzer has joined #u-boot
mmu_man has joined #u-boot
alpernebbi has quit [Ping timeout: 246 seconds]
alpernebbi has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
prabhakarlad has quit [Ping timeout: 252 seconds]
WoC has quit [Remote host closed the connection]
mmu_man has quit [Ping timeout: 268 seconds]
WoC has joined #u-boot
GNUtoo has quit [Remote host closed the connection]
lucascastro has joined #u-boot
GNUtoo has joined #u-boot
lucascastro has quit [Ping timeout: 244 seconds]
<Forty-Bot>
LeSpocky: well, sandbox_defconfig can't be used on x86_64 either
<Forty-Bot>
so if we plan on supporting it, testing on 32-bit archs is good
<sjg1>
LeSpocky: yes we should add an i386 build and qemu test
<sjg1>
Forty-Bot: It can't be used on x86_64?
<Forty-Bot>
not from my testing
<sjg1>
Forty-Bot: What happens?
<Forty-Bot>
it usually hangs somewhere in the unit tests
<Forty-Bot>
I ran into this last when doing the malloc stuff
<Forty-Bot>
and I ended up just testing on sandbox64
<Forty-Bot>
no clue why this works in CI but not my machine
<sjg1>
Forty-Bot: I think that was fixed... but the reason CI is different is that it runs each test separately
<Forty-Bot>
huh, looks like it survived
<Forty-Bot>
some of the tests fail, but no crash
minimal has joined #u-boot
jclsn has quit [Read error: Connection reset by peer]
vagrantc has joined #u-boot
mmu_man has joined #u-boot
Guest4494 has joined #u-boot
<LeSpocky>
Forty-Bot: I used sandbox_defconfig on x86_64, had no problems with that
GNUtoo has quit [Remote host closed the connection]