ewrvvvvvvvvvvvvvvvvvvvvvvvvvvd has quit [Remote host closed the connection]
jeffmiw has quit [Ping timeout: 480 seconds]
jeffmiw has joined #asahi-dev
jeffmiw has quit [Ping timeout: 480 seconds]
deathdisco[m] has joined #asahi-dev
psykose has left #asahi-dev [#asahi-dev]
<jannau>
kettenis: is 'Device 'serial@39b200000' failed to configure default pinctrl: -19' expected? I'm already using a patched dtb with power-management/power-domains removed
<kettenis>
defenitely not expected
<kettenis>
oh, you enabled some debugging output
<kettenis>
should be harmless
<jannau>
yes, I enabled device model debugging output
<kettenis>
to fix the power domain issues you'd need to add some u-boot,dm-pre-reloc properties
<jannau>
is hat also needed when all power-domains are removed?
<kettenis>
no
<kettenis>
and it shouldn't be needed on the t6000 branch anyway since it doesn't have the pmgr driver yet
<kettenis>
you removed those to avoid too much debug spam?
<jannau>
yes
<kettenis>
then forget about what I just said for now ;)
<jannau>
well, I removed them because I remembered you said they cause the device not initiated without 'u-boot,dm-pre-reloc'. I wasn't aware that it's only a problem with the pmgr driver in u-boot
<jannau>
reducing the debug spam was a nice side effect
___nick___ has joined #asahi-dev
___nick___ has quit []
___nick___ has joined #asahi-dev
jeffmiw has joined #asahi-dev
aleasto has joined #asahi-dev
jeffmiw has quit [Ping timeout: 480 seconds]
kit_ty_kate has quit [Ping timeout: 480 seconds]
ewryyyyyyyyyyyyyyyyyyyyyyyyyyd has joined #asahi-dev
<marcan>
looks like they're basically feeding a bunch of metrics into PID controllers and using that to make scheduling and DVFS state decisions
jeffmiw has quit [Ping timeout: 480 seconds]
yuyichao has quit [Ping timeout: 480 seconds]
<kettenis>
and apparently an API for programs to influence those decisions
yuyichao has joined #asahi-dev
<jevinskie[m]>
kettenis: I should have asked before I ported apfs-fuse to baremetal for inclusion in your u-boot fork but: can your u-boot quiesce the HW enough such that it can chainload another m1n1/u-boot/xnu (my particular use case)? I’m trying to take my m1n1+concatenated xnu and rework it to m1n1+concatenated u-boot loading xnu from the Preboot apfs volume
<kettenis>
it probably doesn't at the moment, but the nvme driver now runs some code before handover to shut itself down as far as we can
<kettenis>
so other drivers can do the same thing if needed
<jevinskie[m]>
Gotcha, thanks. I’ll push forward and patch as needed. Thanks for the nvme support in u-boot!