#asahi-dev · 2025-12-16 12:09
chaos_princessi think so#asahi-dev · 2025-12-16 12:05
chaos_princessyes#asahi-dev · 2025-12-16 12:04
chaos_princessor do the test i proposed :P#asahi-dev · 2025-12-16 12:03
chaos_princessso, you are running at 120hz, but with 60hz worth of latency#asahi-dev · 2025-12-16 12:03
chaos_princesssomething tells me ts1 is the "desired presentation time"#asahi-dev · 2025-12-16 12:01
chaos_princess(something tells me the offsets will change)#asahi-dev · 2025-12-16 12:01
chaos_princesstry making sure you have 120hz content on the screen#asahi-dev · 2025-12-16 12:01
chaos_princesssince macos only runs at 120hz when something wants it#asahi-dev · 2025-12-16 12:00
chaos_princessits probably running at 60hz at that point#asahi-dev · 2025-12-16 12:00
chaos_princessi mean in macos#asahi-dev · 2025-12-16 11:59
chaos_princessoliver_: what was on screen when you got those values?#asahi-dev · 2025-12-16 11:58
chaos_princessso, that is probably fine?#asahi-dev · 2025-12-16 11:58
chaos_princess1s/16ms is 60-ish#asahi-dev · 2025-12-16 11:56
chaos_princessi assume ts1 is present time and ts2 is render completion time?#asahi-dev · 2025-12-16 11:56
chaos_princessalso, where did 16660000 and 40000000 come from#asahi-dev · 2025-12-16 11:55
chaos_princesstimesync? no, but it is just yet another mmio on the dcp, look for the smallest one, iirc it was that one#asahi-dev · 2025-12-16 11:54
chaos_princessin theory you want proper vrr, the display can go as low as 10 hz#asahi-dev · 2025-12-16 11:54
chaos_princess^#asahi-dev · 2025-12-16 11:54
chaos_princessit will#asahi-dev · 2025-12-16 11:53
chaos_princessoliver_: 24mhz is the "standard apple clock rate". and yes, macos reads timesync before every frame submit#asahi-dev · 2025-12-16 11:47
chaos_princessthat would be constant#asahi-dev · 2025-12-16 11:46
chaos_princessand, i would be interested in how the constants were derived#asahi-dev · 2025-12-16 11:45
chaos_princessoliver_: the only other issue i see is that you might want to look into something called "timesync", there is a separate mmio region on some coprocessors that contains the 24mhz clock from the coprocessor's perspective#asahi-dev · 2025-12-16 11:43
chaos_princesshell yes#asahi-dev · 2025-12-15 09:03
chaos_princessbut 12 is not helpful for m4?#asahi-dev · 2025-12-15 08:59
chaos_princessinteresting. i sorta want to try it on one of my machines now and see how it goes#asahi-dev · 2025-12-15 08:50
chaos_princesswouldn't kmutil complain when trying to build that?#asahi-dev · 2025-12-15 08:50
chaos_princessits more that, well, how is this supposed to work#asahi-dev · 2025-12-15 08:38
chaos_princessnickchan: so, mind elaborating on that? since i've heard you propose that before and i am a bit confused as to how that is supposed to work#asahi-dev · 2025-12-13 11:09
chaos_princessand which machine?#asahi-dev · 2025-12-13 11:09
chaos_princesswhich versions were you using?#asahi-dev · 2025-12-13 10:44
chaos_princessthe sfr error is due to it losing the internet connection and failing to download something#asahi-dev · 2025-12-13 10:19
chaos_princessand no, dfu is a full wipe of everything#asahi-dev · 2025-12-13 10:18
chaos_princessconnect to the internet#asahi-dev · 2025-12-13 08:33
chaos_princess*m2 pro/max#asahi-dev · 2025-12-13 08:33
chaos_princessYou can install on pro/max without dfu restore by installing 13.latest, then running 13.5 installassistant from that#asahi-dev · 2025-12-12 22:33
chaos_princessarchive.org is your friend#asahi-dev · 2025-12-12 18:08
chaos_princessthe dcp firmware is packaged together with the macos install, with iboot loading the correct one for the selected os, and as such apple does not need to have any compatibility between different versions#asahi-dev · 2025-12-12 18:07
chaos_princessyes#asahi-dev · 2025-12-12 18:05
chaos_princessand no, it is not backwards compatible#asahi-dev · 2025-12-12 18:04
chaos_princessthere is current version somewhere in device tree that is filled in by m1n1#asahi-dev · 2025-12-12 17:58
chaos_princessdcp changes between versions, and tracer does 12.3(?) or 13.5 specifically#asahi-dev · 2025-12-12 17:58
chaos_princessyes#asahi-dev · 2025-12-11 12:30
chaos_princessunlikely the main install is 13.5#asahi-dev · 2025-12-11 12:12
chaos_princessright now it is trying to load macos rootfs from the asahi volume, going "where is everything?" and panicking#asahi-dev · 2025-12-11 12:08
chaos_princessif you want to use m1n1 as a hypervisor, you need to install a full separate copy of macos, and then replace it's kernel with m1n1#asahi-dev · 2025-12-11 12:08
chaos_princessactually, > "and m1n1 came with that" - you are doing it wrong.#asahi-dev · 2025-12-11 12:07
chaos_princesswhen you did kmutil configure-boot, what did you specify as the -v parameter#asahi-dev · 2025-12-07 10:35
chaos_princessbut a simple check should also work#asahi-dev · 2025-12-07 10:35
chaos_princessif you want to be extra fancy, you can match to real addresses via adt