warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #u-boot
warpme has quit [Client Quit]
mmu_man has joined #u-boot
warpme has joined #u-boot
<xypron>
tlwoerner: Something wrong with the Anubis script.
<xypron>
I hate all those sites wasting my time with Anubis.
<Tartarus>
It's a shame there's not a real alternative
<Tartarus>
The various IP blocking and so forth the admins tried didn't really stop the bots enough
persmule has joined #u-boot
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dsimic has quit [Ping timeout: 240 seconds]
dsimic has joined #u-boot
BtbN has joined #u-boot
<BtbN>
Hi! Is there some way I can detect if the current boot is a cold-boot or a reboot? I'd like to launch a different kernel in each case, to have a fallback in case rebooting into an updated kernel fails.
<BtbN>
The device logs the type of boot to the serial console each bootup, so the information has to be somewhere
<quinq>
grep for the message in the source
la_mettrie has left #u-boot [#u-boot]
<BtbN>
I'm afraid it's not u-boot logging it, but the device itself
<BtbN>
before it launches u-boot
<K900>
The way you'd normally do this is with boot counting
<K900>
As in, you store a number of boot attempts in some external storage, and then you have the OS determine whether it booted "successfully", however you define that, and set a flag in the same storage
<K900>
And on the next boot you check the value of the flag, then reset it
<K900>
And if you get to the bootloader a few times without the success flag being set, you switch to booting the backup
<BtbN>
hm, can u-boot reliably write to ext4?
<BtbN>
Cause that's all there is :D
<BtbN>
Though the information of the boot type exists somewhere, probably need to poke a magic memory address
<BtbN>
don't think saveenv works on this device
<BtbN>
Another idea I'd have would be two separate boot-scripts
<BtbN>
and have the second one delete itself first thing
<BtbN>
so if it fails to boot, next boot only the old one is still there