#
✕ nick:oliver
#asahi-dev · 2025-12-28 20:03
oliverlm: i have no idea, but i would assume it to work
#asahi-dev · 2025-12-28 19:57
oliver(without SUBDIRS)
#asahi-dev · 2025-12-28 19:57
olivercheckout git repo, edit EXTRAVERSION is Makefile, copy current config from /boot/ to .config, unset CONFIG_EFI_SBAT_FILE in .config, ensure you have rustc on your path, then run `make -j10 SUBDIRS=drivers/gpu/drm/apple && sudo make -j10 SUBDIRS=drivers/gpu/drm/apple INSTALL_DTBS_PATH='/usr/lib/modules/$(KERNELRELEASE)/dtb/' dtbs_install modules_install install`
#asahi-dev · 2025-12-28 19:48
oliverI have not tested any other, but it should work with all of them, as long as they behave similar to mutter & kwin. have you a specific one in mind?
#asahi-dev · 2025-12-28 19:12
oliveryou can try this one: https://github.com/AsahiLinux/linux/pull/431
#asahi-dev · 2025-12-28 19:09
oliverchadmed: i see no difference between r03w and r01l in sdr rendering. using r01l in hdr rendering allows for one or two other colorspaces to be used, but all of them look totally broken.
#asahi-dev · 2025-12-28 07:49
oliverfor sdr
#asahi-dev · 2025-12-28 07:49
oliverjust double checked, it is XRGB2101010.
#asahi-dev · 2025-12-28 07:23
oliverchadmed: mutter uses rbg2101010 for both sdr/hdr iirc.
#asahi-dev · 2025-12-27 22:02
oliverMy patch does though. I have to check tomorrow what kwin does if I disable that again.
#asahi-dev · 2025-12-27 22:01
oliverNo, it doesn't right now. I think I've read somewhere that this might be open for discussion.
#asahi-dev · 2025-12-27 21:58
oliverCurrently in mutter that wouldnt be helpful, as you can not change the real brightness in hdr mode due to mutter only using the virtual backlight control.
#asahi-dev · 2025-12-27 21:56
oliverThat is set as soon as you switch into hdr mode, even if only sdr content is on the screen. Ah, but you mean that would be fine, but still unlock the full brightness range.
#asahi-dev · 2025-12-27 21:50
oliverThat would need at least support by the compositor, in kernel space you don't know if you have pixels above sdr range
#asahi-dev · 2025-12-27 21:46
oliverNot sure I understand. Did you mean: clip the brightness in hdr mode when no hdr content is visible?
#asahi-dev · 2025-12-27 21:39
oliverI think mutter is currently ignoring that. But sure what kwin does with that. It looks like the whole space on Linux isn't quite there yet
#asahi-dev · 2025-12-27 20:25
oliverThanks
#asahi-dev · 2025-12-27 20:16
oliverSounds reasonable. Do you know if I get it from macos or do I need to build one up from the ground?
#asahi-dev · 2025-12-27 19:34
oliver* and totally fine with kde too
#asahi-dev · 2025-12-27 19:17
oliverI put something out today. It works pretty fine with vanilla gnome 49 and okayish with kde for now. would be nice if someone could try this out. I have the feeling, that the whole hdr space on linux is still not really there yet... but at least it works: https://github.com/AsahiLinux/linux/pull/431
#asahi-dev · 2025-12-27 12:29
oliverthank you!
#asahi-dev · 2025-12-27 11:57
oliverthank you. how would i find something like this out by myself, is that written down somewhere?
#asahi-dev · 2025-12-27 11:29
oliveri am trying to read out the surface to be submitted. the way i understand it, the call.surfAddr contains the dma address of where the actual data is. how can I read the data behind this address? i need to somehow map this to a physical or virtual address? i thought i could just do `dart_dcp_tracer.dart.ioread` but thats not correct.
#asahi-dev · 2025-12-26 14:55
oliverLet's see how fast we are if need to transfer 30mb of frame buffer over serial each swap ;p
#asahi-dev · 2025-12-26 14:18
oliverThanks. Ive disabled most printing actually, I am using the parse script later. But I want to record the screen and some timestamp in the future so can match an event to what's actually happening.
#asahi-dev · 2025-12-26 14:10
oliverBut that's just experimenting, I need to check what gnome is actually doing, I guess
#asahi-dev · 2025-12-26 14:09
oliverI set xfer to hdr and keep colorspace in native. That at least gives me a good looking result.
#asahi-dev · 2025-12-26 14:08
oliverThanks
#asahi-dev · 2025-12-26 14:07
oliverOkay, then I'll try to verify that by just looking at the data that Is scanned out. I should be able to read the pixel data from m1n1 right?
#asahi-dev · 2025-12-26 14:05
oliverIf I force gnome into hdr rendering and tell dcp to scan out with xfer hdr, it actually looks quite good already. If I then force the brightness as high as mac does, it looks pretty good already.
#asahi-dev · 2025-12-26 14:05
oliveryes exactly. And the primary surface format changes to 16bit float
#asahi-dev · 2025-12-26 14:03
oliverUnless the media controls are overlaying the video
#asahi-dev · 2025-12-26 14:02
oliver I am going for non fullscreen hdr content right now. You're right with full screen content, that's probably going onto its own surface.
#asahi-dev · 2025-12-26 13:52
oliverYou're sure? I saw macos switching from a 10bit rgb format to 16bit half floats, but it is just scanning out that one surface while the hdr media is playing (well, as along as something is overlaying something on top of the hdr content at least). And interestingly it is also scanning that one out as sdr with the same colorspace.
#asahi-dev · 2025-12-26 13:04
oliverLooking for educated guesses: when you display some hdr content on a Macbook, it takes half a second for the hdr content to reach full brightness. During tracing I see, that the display brightness is slowly increased above the normal sdr maximum during this time. Question is now: how does the sdr content stay at the same brightness during that time? Is macos just rendering it darker in software or might it just adjust some gamma curve or
#asahi-dev · 2025-12-26 13:04
oliveranything?
#asahi-dev · 2025-12-22 21:11
oliverMaybe. I saw in a trace that the brightness was set to value larger then the max in the dcp driver.
#asahi-dev · 2025-12-22 20:49
oliverDid anyone look into hdr on the internal display in the past? Is there something written down? I see that gnome already uses the rbg2101010 format for the primary plane. I also see some bits in the dcp driver regarding color space and transfer function.
#asahi-dev · 2025-12-21 20:07
oliverCould be
#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: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: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-12 18:06
oliverand the dcp then just talks the "device-tree.current-version" version of the protocol?
#asahi-dev · 2025-12-12 18:03
oliverand how does the linux kernel handle this then? it just talks 13.5 and the dcp is reverse compatible?
#asahi-dev · 2025-12-12 18:02
oliveri see

plus ›