<chadmed>
argh TIL that the dt bindings that make doing energy aware scheduling easier are a downstream android-only feature... and arm's documentation on energy aware scheduling only covers using the android specific bindings
<chadmed>
the "correct" way to do it upstream is still to build the energy model manually in the cpufreq driver or let the em subsystem build its own with a dodgy little formula that tries to guess how much power each core uses based on its operating points, which seems so dirty and gross
mrkajetanp has joined #asahi-dev
mrkajetanp_ has quit [Ping timeout: 480 seconds]
nuh^ has joined #asahi-dev
nuh^ has quit [Ping timeout: 480 seconds]
yuyichao_ has joined #asahi-dev
yuyichao has quit [Read error: Connection reset by peer]
yuyichao_ has quit [Quit: Konversation terminated!]
the_lanetly_052___ has joined #asahi-dev
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi-dev
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
tsujp has quit [Read error: Connection reset by peer]
tsujp has joined #asahi-dev
chadmed has quit [Read error: Connection reset by peer]
chadmed has joined #asahi-dev
bisko has joined #asahi-dev
bisko has quit [Read error: Connection reset by peer]
bisko has joined #asahi-dev
bisko has quit []
chadmed has quit [Remote host closed the connection]
chadmed has joined #asahi-dev
nuh^ has quit [Ping timeout: 480 seconds]
nuh^ has joined #asahi-dev
nuh^ has quit [Ping timeout: 480 seconds]
nuh^ has joined #asahi-dev
nuh^ has quit [Ping timeout: 480 seconds]
nuh^ has joined #asahi-dev
kov has joined #asahi-dev
nuh^ has quit [Ping timeout: 480 seconds]
c10l has quit [Quit: Bye o/]
c10l has joined #asahi-dev
nuh^ has joined #asahi-dev
nuh^ has quit [Ping timeout: 480 seconds]
nuh^ has joined #asahi-dev
nuh^ has quit [Remote host closed the connection]
ayedaemon[m] has joined #asahi-dev
<SocioProphet[m]>
Wanted to follow up on this. Thanks for everythign you've contributed btw--you are doing cool stuff and its good for the community. Ive been digging into this project a bit across and booted on my m1 macbook, but as I look into the docs and dig through things it seems like as long as one was willing to recompile the m1n1 for x86 build the firmware would support the same deployment. Admittedly there may be some porting to do of
<SocioProphet[m]>
assembly code; but wanted to understand if I'm missing the point. My read was that the firmware was the same and as long as one was willing to do some of the necessary leg work (https://kernelshaman.blogspot.com/2021/02/building-xnu-for-macos-112-intel-apple.html) it would be possible to deploy on older mac-intel machines as well. Is this wrong?
the_lanetly_052___ has quit [Ping timeout: 480 seconds]
<ChaosPrincess>
completely
<j`ey>
SocioProphet[m]: there's 0 point of trying to make m1n1 work on x86
<ChaosPrincess>
m1n1 boots from iboot's custom boot protocol, while intel macs use efi
<_jannau_>
SocioProphet[m]: yes, m1n1 is a very low level tool written for apple silicon machines. most of the code makes no sense on a x86 mac
<_jannau_>
the system firmware is certainly not the same. firmware for same devices as the wifi might be the same or similar
<j`ey>
SocioProphet[m]: you cant just "recompile" it, you have to rewrite aboute 99% of it
<SocioProphet[m]>
got it
<SocioProphet[m]>
appreciate your schooling a noob.
<SocioProphet[m]>
I was thinking I'd maybe try to re-align your installer to install a T2Linux linux example for x86, but wanted to consider if it could make sense to rebuild m1n1 in the process--I have that answer now so thank you. My initial efforts to recompile it / build for x86 failed so wanted to ask the experts before I decided to bang my head against the wall too hard lol
<j`ey>
the installer doesnt make sense either
<SocioProphet[m]>
there are pieces that do for sure
<SocioProphet[m]>
the disk resizing is worth not rebuilding
<SocioProphet[m]>
you have a good process
the_lanetly_052___ has joined #asahi-dev
chadmed has quit [Ping timeout: 480 seconds]
chadmed has joined #asahi-dev
<marcan>
yes, the disk resizing and general OS recognition stuff could be used on x86 Macs. not all of it though, the boot/nvram/recovery related stuff is quite specific to M1.
AdryzzOLEDEdition[m] is now known as AdryzzOLEDEdition[m]1
bps has joined #asahi-dev
Telvana has quit []
Telvana has joined #asahi-dev
Telvana has quit []
bisko has joined #asahi-dev
bps has quit [Ping timeout: 480 seconds]
bisko has quit [Read error: Connection reset by peer]
<SocioProphet[m]>
Thanks. I will report back and share any code that I've been able to repurpose / reuse for this goal. Definitely appfeciate the guidance
Gaspare has joined #asahi-dev
fetsorn has joined #asahi-dev
fetsorn has quit [Quit: :q]
fetsorn has joined #asahi-dev
fetsorn has quit []
fetsorn has joined #asahi-dev
nuh^ has joined #asahi-dev
Gaspare has quit [Quit: Gaspare]
fetsorn has quit [Read error: Connection reset by peer]
MajorBiscuit has joined #asahi-dev
MajorBiscuit has quit [Quit: WeeChat 3.5]
Gaspare has joined #asahi-dev
Gaspare has quit [Quit: Gaspare]
nicolas17 has joined #asahi-dev
fetsorn has joined #asahi-dev
fetsorn has quit []
fetsorn has joined #asahi-dev
fetsorn has quit [Remote host closed the connection]