<tpw_rules>
is apple m2 a different defconfig on u-boot?
<zzywysm>
i don't think it is, but it probably should be
<milek7>
why?
<chadmed>
jannau: was this on the studio or a laptop that was plugged in? the smc reports 50W at all times when charging on my 14" so that may have spoiled your testing
<chadmed>
on battery i can rev it up to about 30W watching 1080p60 video
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
doggkruse has joined #asahi-dev
PhilippvK has joined #asahi-dev
phiologe has quit [Ping timeout: 480 seconds]
impurity0174[m] has joined #asahi-dev
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
doggkruse has joined #asahi-dev
the_lanetly_052__ has joined #asahi-dev
pyropeter1 has joined #asahi-dev
PyroPeter_ has quit [Ping timeout: 480 seconds]
kov has quit [Quit: Coyote finally caught me]
<jannau>
chadmed: macbook pro 14" m1 max on battery
<jannau>
tpw_rules: same defconfig, the differences are minimal and we want a single u-boot binary to handle all devices
<jannau>
30W for 1080p60 decoding and rendering are more than I would have expected but it can easily depend on codec/bitrate
<tpw_rules>
"single u-boot binary to handle all devices" yes, that's what i wanted too. good to know that's the case
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nicolas17 has quit [Ping timeout: 480 seconds]
X-Scale` has joined #asahi-dev
X-Scale has quit [Ping timeout: 480 seconds]
X-Scale` is now known as X-Scale
Catyre has joined #asahi-dev
MajorBiscuit has joined #asahi-dev
Catyre has quit [Ping timeout: 480 seconds]
Catyre has joined #asahi-dev
Catyre has quit [Ping timeout: 480 seconds]
<kettenis>
when I named the u-boot defconfig file, I anticipated the need for a separate config at some point for a future SoC generation
<kettenis>
but so far we've managed to avoid that
<kettenis>
meanwhile I did confirm that the crash is indeed caused by an SError during the SetVirtualAddressMap() EFI runtime call that happens early on in the OpenBSD kernel
<kettenis>
frustratingly the bug comes and goes if I add some code to the kernel or u-boot (hence my Heisenbug complaint last night)
<kettenis>
probably need some help from marcan to make some sense out of that SError
<_jannau_>
heisenbug due to address space randomization or alignment?
<kettenis>
probably
<kettenis>
I suspect the early memory mapping code in our kernel isn't 100% correct
<kettenis>
a hint of what the hardware doesn't like about it would probably help me find that issue
nela has quit [Quit: leaving.]
nela has joined #asahi-dev
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi-dev
the_lanetly_052__ has quit [Remote host closed the connection]
doggkruse has joined #asahi-dev
kov has joined #asahi-dev
doggkruse has quit [Ping timeout: 480 seconds]
<kettenis>
hmm, using 1G WB cached mappings that overlap with the memory we're not supposed to touch is probably not a good idea
<kettenis>
so that probably is the issue
<kettenis>
bit odd that I didn't run into this before though