ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #u-boot
vardhan has joined #u-boot
vardhan_ has joined #u-boot
clamor has joined #u-boot
mtoy has quit [Ping timeout: 240 seconds]
mtoy has joined #u-boot
xroumegue has quit [Ping timeout: 245 seconds]
clamor has quit [Ping timeout: 248 seconds]
clamor has joined #u-boot
xroumegue has joined #u-boot
vardhan_ has quit [Read error: Connection reset by peer]
vardhan_ has joined #u-boot
vardhan has quit [Ping timeout: 248 seconds]
vardhan_ has quit [Ping timeout: 260 seconds]
vardhan has joined #u-boot
shadowless has quit [Ping timeout: 245 seconds]
gsz has joined #u-boot
gsz has quit [Ping timeout: 244 seconds]
vardhan has quit [Ping timeout: 260 seconds]
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot
rvalue has quit [Ping timeout: 245 seconds]
rvalue has joined #u-boot
bjoto has joined #u-boot
Poltawer has joined #u-boot
mmu_man has joined #u-boot
Algotech has joined #u-boot
gsz has joined #u-boot
apritzel_ has joined #u-boot
apritzel_ has quit [Ping timeout: 268 seconds]
Jones42 has joined #u-boot
<pitillo>
hi marex, good day. I hope I don't bother you again. I think I've taken a little step forward, I'm understanding some things and I'm a little closer than yesterday, but it's still a huge "world"
<pitillo>
I have managed to adjust the CFLAGS and get to a point where the size is too big. I'm still testing and trying to adjust, but I'm not sure if I'll be able:
<pitillo>
ld.bfd: u-boot-spl section `.rodata' will not fit in region `.sram'
<pitillo>
ld.bfd: region `.sram' overflowed by 1508 bytes
<pitillo>
but there's still some work ahead, because CFLAGS aren't set right and the product is still EABI5
goliath has joined #u-boot
gsz has quit [Ping timeout: 245 seconds]
gsz has joined #u-boot
vfazio has quit [Remote host closed the connection]
vfazio has joined #u-boot
zkrx has quit []
zkrx has joined #u-boot
jclsn has quit [Quit: WeeChat 4.5.1]
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
Stalevar has quit [Read error: Connection reset by peer]
monstr has joined #u-boot
tlwoerner has joined #u-boot
Stalevar has joined #u-boot
dhruvag2000 has joined #u-boot
vardhan_ has joined #u-boot
gsz has quit [Ping timeout: 248 seconds]
monstr has quit [Remote host closed the connection]
goliath has quit [Quit: SIGSEGV]
lehmanju has quit [Ping timeout: 276 seconds]
goliath has joined #u-boot
vfazio has quit [Remote host closed the connection]
vfazio has joined #u-boot
<xypron>
Tartarus: There seems to be something misconfigured in Gitlab: I see a lot of failures with '/usr/bin/sh: exec format error'. Why do we now use arm64 runners on jobs like sandbox64 test.py? Wouldn't this requires a separate Docker image built specifically for arm64?
<xypron>
sjg1: In bootdev_find_by_label() we check for CONFIG_IS_ENABLED(BLK). Let's assume that there are not block devices. How would we find the a bootdev by label 'dhcp'?
<Tartarus>
xypron: Yes, the instructions are for building for both amd64 and arm64
<Tartarus>
As we have a number of arm64 runners now
<xypron>
Tartarus: does that mean by chance we build on amd64 or arm64?
<Tartarus>
xypron: Generally yes, a few specific jobs, no.
<Tartarus>
(We have a few jobs that limit to amd64, and a few jobs we do both)
<xypron>
Tartarus: When running TARGETPLATFORM=linux/arm64 docker buildx build on an an ARM system it says some packages are missing. How did you build the arm64 image?
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #u-boot
gsz has joined #u-boot
<Tartarus>
sjg1: Yes, I rejected your broken changes, you're still free to do them in non-broken ways. I believe that one is you should be 'select BLK' instead, until you separate out the parts of BOOTSTD which do require BLK (and so should be 'select BLK' instead) from those which don't.
enok has joined #u-boot
enok has quit [Remote host closed the connection]
enok has joined #u-boot
enok has quit [Remote host closed the connection]
goliath has joined #u-boot
<Tartarus>
But also, I don't know if I need to spell out every time I compromise and take something of yours which I have some level of problem with but am unsure if you just forgot my feedback, disagreed with my feedback, or don't care about my feedback.
mmu_man has quit [Ping timeout: 260 seconds]
enok has joined #u-boot
enok has quit [Remote host closed the connection]
mmu_man has joined #u-boot
<sjg1>
Tartarus: No, I don't want bootstd to depend on BLK, or select BLK. It should not need BLK
gsz has quit [Ping timeout: 272 seconds]
<sjg1>
Tartarus: But yes, please do point out when you compromise on things. Also, I like feedback. But there has been too much 'no'
apritzel_ has joined #u-boot
<Tartarus>
sjg1: Do your gitlab runners run priviledged or no?
Poltawer has quit [Quit: WeeChat 4.6.1]
<Tartarus>
sjg1: And, I have been pointing it out much more of late, but also I don't see the value in 2/2 (adding the symlink in ellesmere directory) of the qemu_arm64_spl conf files, but I did it awayways
fionera has joined #u-boot
<sjg1>
Tartarus: There's no value for you. But for me it means I don't have to maintain my own branch
<sjg1>
Tartarus: The gitlab-runner process is running as root. Is that what you mean?
<sjg1>
Tartarus: I have a conflict for the meeting tomorrow, BTW
<sjg1>
Tartarus: I sent you an email with three things you could compromise on and you rejected all three. So I suggested you pick something you might be willing to compromise on
<Tartarus>
sjg1: Yes, you should be able to maintain your own branch, trivially
<Tartarus>
And no, I mean is it running with the priviledged flag
<Tartarus>
sjg1: And yes, I think what you picked as things that I should have just accepted are telling on your lack of compromise
<Tartarus>
(own branch of u-boot-test-hooks, that is)
<Tartarus>
sjg1: Re meeting conflict, can you please reply to the email where Karen said she'd be there to offer an opinion, and I guess can you make the normal meeting next week? She probably can as well
jmasson has quit [Ping timeout: 260 seconds]
<sjg1>
Tartarus: No, I have ' privileged = false' in the .toml file. I can change it though
<sjg1>
Tartarus: Do you mean ANSI, sunxi bootstd and PXE without lwip?
<Tartarus>
re gitlab yes that although hah, maybe I've just uncovered another bug elsewhere, digging more first
<Tartarus>
And things I should have compromised on and just said yes to, yes, those examples. Doubly so after the last community call where I thought we had made progress on understanding why the sunxi series is in fact not ready, not even for sunxi
<sjg1>
All I see in the notes is that Heinrich was hoping to work on his work-around