#
#asahi-dev · 2025-12-22 06:20
chadmedtheir surface format for their cursor fb is also super fucked up lol
#asahi-dev · 2025-12-22 06:18
chadmedoverlay plane swaps never have ts1 or ts2 set, but ts3 continues ticking up
#asahi-dev · 2025-12-21 23:56
chadmedfinding an installer for 13.5 is becoming incredibly difficult
#asahi-dev · 2025-12-21 23:03
chadmedyeah we're just trying to understand these timestamps right now
#asahi-dev · 2025-12-21 23:02
leiooh, right, for the purpose of DCP understanding I suppose tracing over a DP one would work
#asahi-dev · 2025-12-21 23:02
chadmedi just dont use them because im booted into linux 99.999% of the time
#asahi-dev · 2025-12-21 23:01
chadmedyeah ive got dp adapters
#asahi-dev · 2025-12-21 23:01
leioM2 Pro and up, M3 Pro and up and all M4 supposedly do
#asahi-dev · 2025-12-21 23:01
leiofwiw, I'm reading that all M1, and M2/M3 base don't support VRR over HDMI in macOS
#asahi-dev · 2025-12-21 22:42
chadmedoh ill need a 13.5 install wont i
#asahi-dev · 2025-12-21 22:41
chadmedyeah, ill try get macos to play nice with my vrr monitors and see what happens to the timestamps
#asahi-dev · 2025-12-21 22:39
jannauI think there are multiple interpretations possible. there's probably not much difference in practice but it's still worth experimenting to see if we can learn more
#asahi-dev · 2025-12-21 22:33
jannauthe HV isn't stealing time anymore by default (by modifying various timers)
#asahi-dev · 2025-12-21 22:31
chadmedi just dont see what these three timestamps, which are so closely correlated, could possibly be other than what we have already inferred
#asahi-dev · 2025-12-21 22:31
chadmedthe traces are going to be hard to interpret as meaningfully related to realtime no matter what we do because m1n1 is stealing time while our timebase still ticks up
#asahi-dev · 2025-12-21 22:26
jannauoliver: with the relative timeing I tought that maybe dcp interprets one of the timestamps as current time. the other timestamps would then be relative to that one
#asahi-dev · 2025-12-21 20:07
oliverCould be
#asahi-dev · 2025-12-21 19:55
jannauI think we're speaking past each other
#asahi-dev · 2025-12-21 19:46
oliverbut they are not. all tsX are in the same ballpark. ts2-ts1 and ts3-ts1 are always about 12-14ms
#asahi-dev · 2025-12-21 19:45
jannauI mean relative to one of the ts fields. i.e. ts_X is the current time and the other fields are relative to it
#asahi-dev · 2025-12-21 19:44
oliveror 60hz, depending on what content is visible
#asahi-dev · 2025-12-21 19:43
oliverand with rrate i mean 120hz here, not the real swap rate
#asahi-dev · 2025-12-21 19:41
oliver * i get about ~5 swap submit commands per second with ts1 increasing by exactly 1/rrate on each command. if they were related to any realtime-like clock, again, the difference between two swap commands would not be exactly 1/rrate.
#asahi-dev · 2025-12-21 19:41
oliverbut that does not make sense:
#asahi-dev · 2025-12-21 19:41
oliver * if they were relative, ts1 wouldn't increment by exactly 1/rrate.
#asahi-dev · 2025-12-21 19:38
jannaubut I wouldn't rule out that the timestamps are all relative. that would explain why setting a static value works
#asahi-dev · 2025-12-21 19:37
jannauoliver: I wouldn't necessarily trust timestamps vs real time relations from traces
#asahi-dev · 2025-12-21 19:31
oliverthe dcp tracing values need more interpretation?
#asahi-dev · 2025-12-21 19:31
oliverjannau, chadmed: just reading the conversation here. "setting ts1 = now + (1 / refresh rate) * 1e9, ts2 = last time we got dcp_swapped and ts3 = now" it just doesn't match the data from dcp trace at all. i wrote this on github: ts1 does not depend on real time and only increments by 1 / desired refresh rate. ts2 is approx ts1+14ms and ts3 is approxy ts1+12ms. Both are slightly varying from frame to frame. or do i missing something and
#asahi-dev · 2025-12-21 19:30
jannaumacbook pro hdmi out fixed
#asahi-dev · 2025-12-21 17:58
nickchana small patch will make the existing code work
#asahi-dev · 2025-12-21 17:57
nickchanalright figured rtkit v10 (iOS 11-13); only critical difference is epmap is completed within 1 message so MGMT_MSG_EPMAP_REPLY_DONE and MGMT_MSG_EPMAP_REPLY_MORE doesn't exist
#asahi-dev · 2025-12-21 17:13
amarioguyCLUSTER_PRIO makes sense, that's easy enough to test, but i guess the symbol is what's unclear to me because mailing list seems to imply cpu groups can be prioritized, but the symbol implies it can only do a delay
#asahi-dev · 2025-12-21 17:11
amarioguysince the linux driver doesn't use it, trying to get any info i can before i have to resort to bit twiddling to find out specifics
#asahi-dev · 2025-12-21 17:11
amarioguybtw for AIC2, is AIC2_DELAY_GROUPS in the linux driver that "grouping" register mentioned in the mailing list discussion?
#asahi-dev · 2025-12-21 15:15
jannauI've tagged and pushed u-boot asahi-v2025.10-1
#asahi-dev · 2025-12-21 13:38
jannauI'll first look into u-boot and afterwards into the hdmi out
#asahi-dev · 2025-12-21 13:34
jannaunot yet tagged because the usb changes are expected to break usb in u-boot and the macbook pro HDMI output is very likely broken as well
#asahi-dev · 2025-12-21 13:32
jannauI've pushed a v6.18.2 based tree to asahi-wip (untagged). Most signifant changes: upstream(-ish) dwc3/atc USB support and asahi GPU driver updates in preparation for upstreaming
#asahi-dev · 2025-12-21 13:17
chadmed(enabling tearing in the surfaces seems to fix the laggy brightness changing and some other weird stuff btw)
#asahi-dev · 2025-12-21 13:16
jannaushould not make much of a difference in practice
#asahi-dev · 2025-12-21 13:16
chadmedwould the timeout always be exactly one frame in the future though even if we're disallowing tearing
#asahi-dev · 2025-12-21 13:15
jannauinstead of submit and present time I could imagine present time and timeout
#asahi-dev · 2025-12-21 13:13
jannauI suspect last_present_time might be render start time (i.e. just informative)
#asahi-dev · 2025-12-21 13:11
chadmedi dont really see how they could be anything else given the tight timing but sure
#asahi-dev · 2025-12-21 13:09
jannauoliver: I pulled the PR and modified it as suggested
#asahi-dev · 2025-12-21 13:08
jannauI think I want to have a better understanding what the timestamps mean before setting them for all displays
#asahi-dev · 2025-12-21 12:51
chadmedmacos doesnt like my vrr monitors though so i cant really test that with varying times between swaps for a given mode
#asahi-dev · 2025-12-21 12:50
chadmedts2 is the only one im not _too_ sure is real but it seems to line up
#asahi-dev · 2025-12-21 12:49
chadmedoliver, jannau: setting ts1 = now + (1 / refresh rate) * 1e9, ts2 = last time we got dcp_swapped and ts3 = now does not break anything on any of the hdmi displays ive tested

plus ›