#
✕ nick:jannau
#asahi-dev · 2026-01-04 20:54
jannauthe latter mostly because I started in the wrong direction and at the same time wanted to change too much
#asahi-dev · 2026-01-04 20:53
jannauI have (trivial) patches which add aux-bridge and aux-hpd-bridge to atc-phy and tipd but are stuck on the dcp side
#asahi-dev · 2026-01-04 20:51
jannauseems it wasn't (just) devicetree objections
#asahi-dev · 2026-01-04 20:50
jannaurelevant mails: https://lore.kernel.org/dri-devel/20230903214150.2877023-1-dmitry.baryshkov@linaro.org/ https://lore.kernel.org/dri-devel/20231025223027.943563-1-dmitry.baryshkov@linaro.org/
#asahi-dev · 2026-01-04 20:27
jannauwith the current setup you can't have more than one connector per dcpext. you wouldn't know for which port the hotplug event is. you would have to model 2 things in the device tree which are directly connected two each type-c port and use those as references in the "displayport" property
#asahi-dev · 2026-01-04 20:20
jannaurosalyntg_: hej, I was afk. the issue with the current setup with the oob_hotplug event is that the devicetree maintainers don't like it. they afaik nak-ed for qcom x1 elite systems
#asahi-dev · 2026-01-03 23:37
jannauwe probably want m1n1 to switch to cpu0 in kboot.c
#asahi-dev · 2026-01-03 17:22
jannaunot that there is yet much to upstream without gem-shmem and gpuvm
#asahi-dev · 2026-01-03 17:21
jannauI guess I'll have to start upstreaming the driver now
#asahi-dev · 2026-01-03 17:19
jannaum1n1 #466 (gpu initdata creation) merged, thanks chaos_princess
#asahi-dev · 2026-01-03 13:26
jannaum3 max has 4 efficiency cores? M3* dev start on the first performance core which would be cpu4 (from m1n1's pov). linux defines the boot cpu as cpu0 independent on device tree entries
#asahi-dev · 2026-01-03 13:18
jannauyes, it's likely that it'll work. There were some changes necessary to get it working on M1 Pro and Max but not much between M1* and M2* (ignoring dptx for the hdmi port on desktop devices)
#asahi-dev · 2026-01-03 10:36
jannauno, I left a comment in PR and you've already picked up my changes
#asahi-dev · 2026-01-03 10:32
jannauI have at least https://github.com/jannau/m1n1/commits/bootloader-cal-blobs/ on top but unfortunately don't remember if I had anything additional
#asahi-dev · 2026-01-03 10:25
jannauchaos_princess: do you have any changes for agx initdata in m1n1 beyond the pull request? I'd like to get that merged soon-ish
#asahi-dev · 2026-01-03 10:23
jannauI'm expecting atc-phy changes for tbt5 / dp2.1 which would be preferably figured out by tracing
#asahi-dev · 2026-01-03 09:28
jannaueven thunderbolt5 / dp 2.1 might be doable with a m3 ultra (if that hasn't the same issue as m4 systems)
#asahi-dev · 2026-01-03 09:26
jannauI suspect everything except agx might be doable with supporting the same fw version on m1 - m3 a mixture of cursing, guessing and luck
#asahi-dev · 2026-01-03 08:16
jannausounds like it's caused by https://github.com/AsahiLinux/linux/pull/433 then cc: chaos_princess
#asahi-dev · 2026-01-03 08:12
jannauchadmed: where? any details? passed a smoke test here
#asahi-dev · 2026-01-03 00:19
jannaugood night. I hope it's not too much trouble to rebase onto the new branch
#asahi-dev · 2026-01-03 00:14
jannauI think surface 0 posed some limitations on pixel formats / color spaces. possibly even on other surfaces
#asahi-dev · 2026-01-03 00:12
jannauthose timed out vblank events should not happen. that handling is only there as safety since some userspace (maybe X11) locked up without
#asahi-dev · 2026-01-03 00:10
jannauthere is a vrr related message in dcp's sys/rtkit log
#asahi-dev · 2026-01-03 00:04
jannauI skipped the swap_id as sequence number (probably fine), the vblank workqueue removal (might introduce deadlocks, taking locks from DCP callbacks is dangerous) and I'm not using surface 0 due to its limitations
#asahi-dev · 2026-01-03 00:01
jannaupushed. I've not taken some of the dcp_surface setting changes (mostly because I didn't spend time on it) That might explain the broken alpha for AR30
#asahi-dev · 2026-01-02 23:56
jannauI've taken some of your changes applied them in cleaner commit order and extended them. full range nv12, nv16 and nv24 support and p010 and p210 support (10-bit nv12/nv16)
#asahi-dev · 2026-01-02 23:53
jannaunot 100% sure if I'm testing correctly but alpha for ARGB2101010 might be broken with my kernel branch (I'll push to asahi-wip in a moment)
#asahi-dev · 2026-01-02 23:51
jannauchadmed: probably relevant to your interest: https://gitlab.freedesktop.org/jannau/kms-overlay-test
#asahi-dev · 2026-01-02 12:25
jannauyes, that's the reason why we don't use it
#asahi-dev · 2026-01-02 12:18
jannauit get's random order for those then. might just be an easily fixable oversight for overlay plane as cursor plane
#asahi-dev · 2026-01-02 12:16
jannauis currently writing kms-overlay-test based on drm-rs/tiny-dfr
#asahi-dev · 2026-01-02 12:11
jannauwhat was necessary to get kwin to use overlays?
#asahi-dev · 2026-01-02 11:48
jannauhow? blending restriction is stricter when wide gamut pixel formats are used?
#asahi-dev · 2026-01-01 09:19
jannauoliver: can you test whether the mapping works on a tty (I think you'll only see swaps when switching ttys)
#asahi-dev · 2026-01-01 09:18
jannaubut the gem objects the kms driver uses (grm_gem_dma) are already mapped so that should not fail. except maybe when using imported objects from the GPU
#asahi-dev · 2026-01-01 09:16
jannaumap into the kernel virtual address space, nothing to do with iova
#asahi-dev · 2025-12-31 14:32
jannauI think this is in the context of m3 bringup. usually the 1st stage m1n1 doesn't need to be updated but it's possible that the installed version does something broken. then you have to either undo it in the chainloaded m1n1 or reinstall a fixed version
#asahi-dev · 2025-12-30 21:03
jannaualways missing
#asahi-dev · 2025-12-30 21:03
jannauAPPLE_MAILBOX=m should have always been broken with APPLE_SEP=m|y but the dependency is not expressed in Kconfig. not sure if I lost that or if it was alwyas
#asahi-dev · 2025-12-30 14:52
jannaumaybe. I certainly used it with 13.5 but I probably have a few minor changes to make it work git-stashed away
#asahi-dev · 2025-12-30 09:48
jannausven's talk isn't going to last 8+ hours
#asahi-dev · 2025-12-30 09:47
jannauI think #asahi would be fine
#asahi-dev · 2025-12-29 15:24
jannauI'm already looking at https://github.com/mripard/redid for edid generation. it doesn't have everything we need but adding the missing bits shouldn't be too hard
#asahi-dev · 2025-12-29 15:20
jannauthe second thing was always the plan
#asahi-dev · 2025-12-29 15:18
jannauwe need the fake EDID for the internal display for user space
#asahi-dev · 2025-12-29 15:18
jannauI think there is a method to override the edid from the display, iirc in the dpavserv endpoint
#asahi-dev · 2025-12-29 15:17
jannauI think we just need to ignore that for the internal display
#asahi-dev · 2025-12-29 15:15
jannauthe fake edid is for the internal macbook pro displays
#asahi-dev · 2025-12-29 15:07
jannauhttps://invent.kde.org/plasma/kwin/-/wikis/Environment-Variables#kwin_use_overlays

plus ›