#
#asahi · 2026-04-11 12:20
pitusthmm okay. i was just confused because the numbers were suspiciously close
#asahi · 2026-04-11 11:52
chaos_princessthe cpu clock rate does change ofc, every modern cpu does that
#asahi · 2026-04-11 11:52
linkmauveTomus[m], if you’re using btrfs, you can certainly install your other distribution in a different subvolume, and pass that subvolume to the kernel at boot to pick the distribution.
#asahi · 2026-04-11 11:44
pitusthmm, maybe it's not quite as close as i thought it was, although it's still very strange
#asahi · 2026-04-11 11:42
pitustdoes the m1 have anything like dynamic frequency scaling? i've been messing around with performance counters (i wrote a stupid lkm to make them readable from usermode) and with CNTVCT_EL0 (which self-reports to be a fixed 24 MHz clock) and it's very very close to a 3 GHz fixed rate which is very suspicious
#asahi · 2026-04-10 16:15
Tomus[m]Ok, thanks for help, i wanted to try it mostly out of curiosity so its not a big issue for me
#asahi · 2026-04-10 16:10
jannaureusing space from the fedora asahio remix install is harder. I'm not even sure btrfs can be shrunk
#asahi · 2026-04-10 16:10
Tomus[m]I want to shrink the current fedora Asahi partition by a bit, I almost fully shrunk macOS
#asahi · 2026-04-10 16:09
jannauwhich space do you want to use for the sencond install? more space from the macos apfs partition? that can be handled by the installer
#asahi · 2026-04-10 16:08
jannauTomus[m]: dual boot works by creating another install
#asahi · 2026-04-10 16:07
chaos_princessrun the installer twice
#asahi · 2026-04-10 16:01
Tomus[m]Is there a way to dualboot a second distro with fedora asahi remix? I have some free time and curiosity and wanted to try out other distros working on asahi but dont know how to configure the bootloader or is shrinking the partition safe
#asahi · 2026-04-09 15:18
svensame for PPL which uses the same ISA extensions, it's only loaded by XNU itself rather than iBoot
#asahi · 2026-04-09 15:18
sventhe GXF/SPRR/whatever lockout mechanism is entirely separate from SPTM, and you can't just disable SPTM once it's running because only SPTM itself could do that
#asahi · 2026-04-09 15:17
svenmaybe look at the actual implementation before speculating ;)
#asahi · 2026-04-09 12:31
pitustyeah, true...
#asahi · 2026-04-09 12:31
chaos_princessand sptm exists on m2/m3 too, but those have pre-sptm macos versions
#asahi · 2026-04-09 12:31
chaos_princessthey already had ppl before sptm that uses similar technology and does similar lockout
#asahi · 2026-04-09 12:25
pitust(although obviously i haven't looked at the actual impl, maybe (and probably) it isn't that simple)
#asahi · 2026-04-09 12:24
pitustwell, you want to lock access to the SPTM registers either way, right? because you don't want to allow disabling SPTM at runtime. so the code could literally be `if (should_use_sptm) { load_sptm(); } lock_sptm_regs();`...
#asahi · 2026-04-09 12:21
JamesCalligeros[m]in fact doing this just makes it harder to start sptm in raw boot mode, which we will need to do for M4 RE
#asahi · 2026-04-09 12:20
JamesCalligeros[m]which already (and still) has full access to everything
#asahi · 2026-04-09 12:20
JamesCalligeros[m]the locking down of access to registers and instructions from raw boot mode doesnt affect sptm. iboot only boots sptm in mach-o boot mode
#asahi · 2026-04-09 12:19
pitustidk, imo its more probable that it was removed because it made sptm easier to implement
#asahi · 2026-04-09 12:17
JamesCalligeros[m]they messed with that, it was available from raw boot objects, some people tried to make use of that, now it is locked down.
#asahi · 2026-04-09 12:16
pitustalso, you could make this sort of "fake xnu" work while a huge amount of the available hardware to a mostly-normal linux env, by running everything in a VM (which isn't ideal for asahi since it breaks KVM and requires using SPTM APIs, but is almost certainly viable)
#asahi · 2026-04-09 12:16
JamesCalligeros[m]apple are allowed to do what they want with the ISA, however our understanding is that this is on the proviso that it does not mess with architected/documented features
#asahi · 2026-04-09 12:12
pitustbut that's completely separate problem from a legal one, anyway; and my understanding of the arm license is that this kind of extension *is* allowed (although i could be completely wrong)
#asahi · 2026-04-09 12:11
pitustah.
#asahi · 2026-04-09 12:11
JamesCalligeros[m]they did not want a "make my memory bugs go away" prctl available, and especially not one that only worked on a subset of machines
#asahi · 2026-04-09 12:09
pitustinteresting, then
#asahi · 2026-04-09 12:09
pitustahh okay
#asahi · 2026-04-09 12:08
jannauthat was not the reason why it was rejected and the patches weren't just for one vendor. it has provisions for fujitsu's A64FX and nvidia's denver
#asahi · 2026-04-09 12:07
JamesCalligeros[m]Intended for one vendor in a non-architected way, and exposed in that particular way
#asahi · 2026-04-09 12:06
pitustwhich patch? the one that was rejected because linux didn't want to have features intended only for one CPU vendor?
#asahi · 2026-04-09 12:06
JamesCalligeros[m]For a good example on how resistant the arm folks are to even relatively minor things like apple’s bespoke TSO flag, see that ML patch. It was not received well.
#asahi · 2026-04-09 12:04
jannautake this with a grain of salt
#asahi · 2026-04-09 12:03
pitustand it doesnt make a huge amount of sense
#asahi · 2026-04-09 12:03
pitustthats pure speculation
#asahi · 2026-04-09 12:02
JamesCalligeros[m]Except your fake xnu now also has to run under sptm and probably doesnt do anything useful or interact with the broader arm ecosystem in any meaningful way
#asahi · 2026-04-09 11:59
pitustand it doesn't really make sense, either: you can still access a fair bit of the features by making a fake XNU
#asahi · 2026-04-09 11:58
pitusti can't find any sources on this being a legal thing
#asahi · 2026-04-09 11:53
JamesCalligeros[m]Theyre not supposed to make ISA extensions available to the broader non-apple ecosystem. On M1 to M3, some of their ISA extensions were able to be used in the boot mode we use for linux. M4 no longer allows this
#asahi · 2026-04-09 11:51
pitustapple has made changes to their chips for a very long time, including usermode-visible changes, and they have always been the only company allowed to do that afaiu
#asahi · 2026-04-09 11:50
pitustJamesCalligeros[m]: do you have a source on the legal dispute thing? or is it just speculation?
#asahi · 2026-04-09 10:45
fl0_idamadaluzia the most recent updates you will get by searching irc logs. usually nobody will update docs for sth incomplete
#asahi · 2026-04-09 02:18
JamesCalligeros[m]Part of the challenge with M4 is getting macOS to run under our hypervisor given significant changes Apple has had to make to the boot process, partially due to a legal dispute with Arm.
#asahi · 2026-04-09 00:39
wetdogive joined here only recently myself, and haven't seen much chatter, so i have no real idea, but yeah, i think there is a lot more work than there are devs
#asahi · 2026-04-09 00:36
amadaluziaGranted, work is still being done on M3, not enough resources for M4
#asahi · 2026-04-09 00:34
amadaluziaI've changed the URL a bit to look at M4 chips and from the sea of TBAs I assume no one has taken up the task yet?

plus ›