qschulz has quit [Remote host closed the connection]
qschulz has joined #u-boot
samekh_ has joined #u-boot
samekh has quit [Ping timeout: 256 seconds]
Xavier7 has joined #u-boot
sdfgsdfg has joined #u-boot
mripard has quit [Read error: Connection reset by peer]
mripard has joined #u-boot
crb has joined #u-boot
apritzel has quit [Ping timeout: 250 seconds]
sdfgsdfg has quit [Quit: ZzzZ]
Xavier7 has quit [Quit: IRcap 8.72 ]
thopiekar has quit [Ping timeout: 240 seconds]
thopiekar has joined #u-boot
vagrantc has quit [Quit: leaving]
persmule has joined #u-boot
persmule has quit [Remote host closed the connection]
sbach has quit [Read error: Connection reset by peer]
sbach has joined #u-boot
mmu_man has quit [Ping timeout: 240 seconds]
sdfgsdfg has joined #u-boot
apritzel has joined #u-boot
apritzel has quit [Ping timeout: 240 seconds]
apritzel has joined #u-boot
pgreco has quit [Ping timeout: 240 seconds]
senzilla has quit [Ping timeout: 256 seconds]
senzilla has joined #u-boot
pgreco has joined #u-boot
pgreco has quit [Ping timeout: 256 seconds]
sdfgsdfg has quit [Quit: ZzzZ]
mmu_man has joined #u-boot
Xogium has joined #u-boot
<Xogium>
heya folks… Hopefully quick question… My brain is melting from the totally confusing thing this has turned into
<Xogium>
in the u-boot I work with, the environment is simultaneously, in a mmc device, in an ubi volume, in a spi flash and in a nand flash… That's already pretty confusing me, but then, the env is also… nowhere
<Xogium>
can someone explain to me how this is even meant to work ?
<apritzel>
Xogium: this is because you might want to determine the location of the environment at *runtime*, not at compile time
<apritzel>
Xogium: there is the weak env_get_location() function, which your platform or board can overwrite to figure out which is the best location
redbrain has joined #u-boot
pgreco has joined #u-boot
pgreco has quit [Ping timeout: 250 seconds]
pgreco has joined #u-boot
adeepv has quit [Read error: Connection reset by peer]
redbrain has quit [Ping timeout: 240 seconds]
<kettenis>
with the patch series I just sent to the mailing list, all Apple Silicon Macs with the original M1 SoC should be able to boot a standard arm64 OS that supports UEFI
<kettenis>
(provided said OS includes M1 support)
apritzel has quit [Ping timeout: 250 seconds]
<Xogium>
kettenis: nice one :)
<kettenis>
(I mean provided the patch series I sent earlier are applied as well)
<Xogium>
so… can someone explain to me how it is that environment can be in multiple devices at once, all apparently sharing the same offset and sector size… and also be nowhere ?
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #u-boot
<Forty-Bot>
Xogium: it's a priority list
<Forty-Bot>
U-Boot searches them in the order specified by env_get_location
<Xogium>
Forty-Bot: hmm… Okay
<Xogium>
Forty-Bot: how do you know which one has priority over the others ? Like, the order
<Forty-Bot>
> in the order specified by env_get_location
<Xogium>
Forty-Bot: thanks
<Xogium>
frankly when you see this the first time, it's mega confusing
<mps>
I confirm what kettenis told above, it works stable for some time on my (and not only my) machine
redbrain has joined #u-boot
gaude has joined #u-boot
<mps>
I've got dockerfile from u-boot developer to test something, lets hope I will manage to do this
<mps>
'docker build -t .' gives me 'invalid argument "." for "-t, --tag" flag: invalid reference format'
<mps>
sorry, wrong channel
Xogium has left #u-boot [leaving channel]
djsands has joined #u-boot
Thorn has quit [Remote host closed the connection]