#
✕ nick:jannau
#asahi-dev · 2025-12-29 15:07
jannauand it's disabled by default, needs KWIN_USE_OVERLAYS=1
#asahi-dev · 2025-12-29 14:45
jannauresume is also broken with hdmi connected but https://github.com/AsahiLinux/linux/commit/4b0726eb707c6728f65f9da996e2ff44c49c6ca7 hopefully works around that
#asahi-dev · 2025-12-29 14:44
jannaupossibly timing or sequencing issues between dptx and iomfb. it's unfortunately annoying to trace as tracing slows it down too much so that it breaks because macos runs into timeouts
#asahi-dev · 2025-12-29 14:41
jannauoliver: what do you mean by rebooted? Did you have to reboot before the TV was detected on the HDMI port?
#asahi-dev · 2025-12-29 14:39
jannauI think chadmed got it working as well for external displays
#asahi-dev · 2025-12-29 12:11
jannauthe the summary at the bottom of https://github.com/AsahiLinux/linux/pull/432/checks?check_run_id=59082317321
#asahi-dev · 2025-12-29 12:11
jannauyour committer / author name do not match the signed-of-by
#asahi-dev · 2025-12-29 09:20
jannauyes
#asahi-dev · 2025-12-29 09:15
jannauintegralpilot: probably related to the critical battery charge reporting. macos 26 changed that. also occurs on m1/m2 macbooks which updated macos to 26 since the smc firmware is not per OS
#asahi-dev · 2025-12-29 08:51
jannauvintage trace, matured for over than 3 years
#asahi-dev · 2025-12-29 08:49
jannaumacos 12.3 trace of a M1 Max
#asahi-dev · 2025-12-29 08:48
jannausven: https://paste.centos.org/view/e4231498
#asahi-dev · 2025-12-28 20:57
jannauhttps://android.googlesource.com/kernel/exynos-modules/devicetree/+/refs/tags/android-wear-15.0.0_r0.11/r11_bcm430132_bluetooth.dtsi looks similar though
#asahi-dev · 2025-12-28 20:50
jannaubut maybe not since your device tree misses the uart-port property
#asahi-dev · 2025-12-28 20:49
jannauellyqw: bluetooth seems to be connected over uart: see odm/btbcm with compatible "goog,nitrous" which points to https://android.googlesource.com/kernel/msm/+/49bc9ea8c034c18527bf550c881ffc13c8465ebb/Documentation/devicetree/bindings/bluetooth/nitrous.txt
#asahi-dev · 2025-12-28 19:11
jannauthere is at least one wide gammut color space. It look "interesting" with standard gammut sRGB data
#asahi-dev · 2025-12-28 10:50
jannaugetting the SPMI usb-pd/type-c controllers up looks like a higher priority task then
#asahi-dev · 2025-12-28 10:48
jannauthe M3 devices do not charge over magsafe while using them as target? That seems inconvenient
#asahi-dev · 2025-12-28 10:47
jannauI tested only briefly on the base M3. Mostly based on ADT and the aic3 code in m1n1. I wouldn't be surprised if there are issues
#asahi-dev · 2025-12-27 23:12
jannauthat's afaik already loaded by iboot. but the driver can provide temperature measurements for temp compensation
#asahi-dev · 2025-12-27 23:06
jannauColor and Timing Elements seem to derived from te EDID in the dcp firmware and since the internal displays don't have one we get bogus information there
#asahi-dev · 2025-12-27 21:59
jannaudoes mutter at least initially sets the backlight to 100%?
#asahi-dev · 2025-12-27 21:59
jannauyes, maybe based on the values in the metadata
#asahi-dev · 2025-12-27 21:55
jannaubased on HDR_OUTPUT_METADATA set by the compositor
#asahi-dev · 2025-12-27 21:49
jannauexpose the full 1500 (or 1000) nits range as backlight values. Values over the max SDR brightness are clipped to the current max if only SDR content is shown
#asahi-dev · 2025-12-27 21:46
jannauyou seem to be right that mutter doesn't modulate the backlight for HDR: https://blog.sebastianwick.net/posts/gnome-49-backlight-changes/
#asahi-dev · 2025-12-27 21:41
jannaualso not quite sure how to integrate dcp's brightness control. Most practical solution might be to extend the range and clip the brightness if no HDR content is shown
#asahi-dev · 2025-12-27 21:33
jannauDisplayID standard is available free of charge after registration from https://vesa.org/vesa-standards/
#asahi-dev · 2025-12-27 21:33
jannauoliver: DisplayID Display Parameters Data block contains "Native Maximum Luminance (Full Coverage)", "Native Maximum Luminance (10% Rectangular Coverage)" and "Native Minimum Luminance" fields. So that would be solved by providing an EDID as well
#asahi-dev · 2025-12-27 20:48
jannauhopefully the new drm/kms backlight api arrives soon: https://zamundaaa.github.io/wayland/2025/07/22/display-next-hackfest-2025.html#new-backlight-api
#asahi-dev · 2025-12-27 20:47
jannauI suppose that would be normally signalled through edid
#asahi-dev · 2025-12-27 20:46
jannauoliver: my understanding for backlight control is that kwin still wants to control the backlight for HDR. For that to work you have to set maxBrightnessOverride, maxAverageBrightnessOverride and minBrightnessOverride via kscreen-doctor: https://paste.debian.net/hidden/99798351
#asahi-dev · 2025-12-27 20:22
jannauI haven't seen anything (but I haven't searched extensively) and I suspect they just hard-code their screen properties directly without EDID so building it from know properties and guesses is the only solution. I have a photo meter so we can at least to some degreee test how good our guesses are
#asahi-dev · 2025-12-27 20:13
jannauoliver: plan for internal display edid is/was to let m1n1 it embed in the device tree (or provide it as firmware)
#asahi-dev · 2025-12-27 16:34
jannauI haven't tested extensively but I've encoutered the broken raw custom boot objects only on m4*. I don't remember if I tested m3
#asahi-dev · 2025-12-27 12:34
jannauI kinda hope that we don't add another FW version to the C dcp driver
#asahi-dev · 2025-12-27 12:33
jannauI think it's useful for bringup to use major macOS versions as stages as long as nobody sinks time into analysing complex FW interfaces like dcp or agx
#asahi-dev · 2025-12-27 12:28
jannauoliver: easiest option to spot this would be experiments/dcp.py I don't think we explictily documented this outside of code. consider m1n1's python implementations and experiments as documentation
#asahi-dev · 2025-12-27 12:22
jannaulatest 14.x would be the easiest option for M3 devices. nvme there might jsut work
#asahi-dev · 2025-12-27 11:42
jannauoliver: the surface is in the disp0 dart
#asahi-dev · 2025-12-26 10:48
jannaum1n1 intends to initializes the t602x e-cores to the same 2GHz as all other e-cores. I haven't noticed a difference in m1n1 pre-kboot on t6020 or t6022 either
#asahi-dev · 2025-12-26 09:20
jannauthe documentation patch isn't merged but I think it should work now. never tried it myself though
#asahi-dev · 2025-12-26 09:19
jannauhave you seen https://lore.kernel.org/linux-kbuild/20240906-macos-build-support-v2-8-06beff418848@samsung.com/
#asahi-dev · 2025-12-26 09:18
jannauintegralpilot: yes, assume that cpu offsets are predictable
#asahi-dev · 2025-12-26 00:04
jannauI think subclassing drm_plane was wrong. dcp_surface belongs state. should have been obvious since it is derived from the common new state
#asahi-dev · 2025-12-25 14:30
jannauit was completely broken because I duplicated the padding
#asahi-dev · 2025-12-25 14:30
jannauchadmed: updated the branch to something working. survices boot, login to plasma and reboot
#asahi-dev · 2025-12-24 13:20
jannaujust to make sure, you're setting the env variable to enable overlays
#asahi-dev · 2025-12-24 13:19
jannaunot sure how much or if at all it helps but at least it's closer to the intended design
#asahi-dev · 2025-12-24 13:07
jannaumerry christmas

plus ›