persmule has quit [Remote host closed the connection]
ikarso has joined #u-boot
sng has joined #u-boot
sng has quit [Remote host closed the connection]
stipa has quit [Quit: WeeChat 3.0]
ex--parrot is now known as ex-parrot
Clamor has joined #u-boot
Leopold has joined #u-boot
Leopold_ has quit [Ping timeout: 246 seconds]
alpernebbi has quit [Ping timeout: 245 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
pivi has joined #u-boot
alpernebbi has joined #u-boot
Clamor has quit [Ping timeout: 248 seconds]
Clamor has joined #u-boot
<lvrp16>
sjg1: another thought about bootstd, it prioritizes efi over script. if my memory serves me correctly, distro_bootcmd is the other way around?
<lvrp16>
i'm not saying this for my own applications, we have no images that use boot.scr since we use grub for everything. but it may affect others.
mmu_man has joined #u-boot
<Kwiboo>
I understand that it is a change in order, but fail to see it as a breaking change, if your distro have both efi and scripts I expect it should be able to boot with both options, so the order should not really matter
valdemaras has joined #u-boot
sng has quit [Remote host closed the connection]
stipa has joined #u-boot
valdemaras has quit [Quit: valdemaras]
ikarso has joined #u-boot
<Tartarus>
lvrp16: It's hard to say what's right in that if you're using EFI, you're "supposed" to be using the distro method for changing boot args
<Tartarus>
Which iirc means grub/etc, as only armbian was doing distro but not EFI, last I checked
mmu_man has quit [Ping timeout: 245 seconds]
<lvrp16>
Tartarus: i'm not saying what's right but rather predefined behavior. It doesn't matter to me which way this goes. I was just pointing it out in case people didn't know about it.
<lvrp16>
I was looking at setting bootargs via boot.scr for our buildroot release earlier today and realized I was doing it the wrong way.
mmu_man has joined #u-boot
<lvrp16>
for anyone migrating distro_bootcmd to bootstd, it's a behavior change that ought to be mentioned
sng has joined #u-boot
persmule has joined #u-boot
sng has quit [Ping timeout: 256 seconds]
<Kwiboo>
lvrp16: ahh, so you mean that the boot script did not actually boot anything, only set up env or something, and because nothing was booted the distro_bootcmd moved on and falled back on efi boot?
sng has joined #u-boot
<lvrp16>
Kwiboo: yeah that was my intented use but discovered the order issue. I did something else in the end for my application that was more agnostic.
sng has quit [Ping timeout: 246 seconds]
<Kwiboo>
guessing a preboot script or similar would make more sense in such scenario with bootstd. the script bootmeth should probably try and boot something and not be used to prepare env for some other bootmeth
<marex>
is it just me who considers the name 'bootmeth' uh ... unfortunate ?
Clamor has quit [Read error: Connection reset by peer]
Clamor has joined #u-boot
sng has joined #u-boot
sng has quit [Ping timeout: 256 seconds]
mmu_man has quit [Ping timeout: 240 seconds]
mmu_man has joined #u-boot
sng has joined #u-boot
goliath has joined #u-boot
sng has quit [Ping timeout: 256 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
<Forty-Bot>
marex: yes
<Forty-Bot>
event "spy" instead of event listener is a little strange too
sng has joined #u-boot
sng has quit [Ping timeout: 245 seconds]
<Tartarus>
OK, good, we can increase the timeout on Azure to larger than 60min, and stop having to play the whack-a-mole time games