#
✕ nick:kitlith
#asahi-dev · 2026-10-11 03:47
kitlithprobably not going to try that right *now*, or even in the next month or two, since everything seems to be happening all at once right now. but this does help a usecase I'm interested in.
#asahi-dev · 2026-10-11 03:38
kitlithI've been occasionally poking at monado and wivrn on my M1 Pro, having an environment to run games that does not require muvm would make running most VR games with monado in particular actually possible. (Writing a monado bridge for muvm is (i think?) more or less blocked on the same thing that explicit sync is)
#asahi-dev · 2026-10-11 03:36
kitlithGot it. I thought I remembered something along those lines, but it's been awhile so I wanted to double check.
#asahi-dev · 2026-10-11 03:30
kitlithQ regarding p3s: I take it there are issues occurring with wine arm64ec+FEX on 16k page size that do not occur with p3s?
#asahi-dev · 2026-03-07 20:45
kitlithunderstandable!
#asahi-dev · 2026-03-07 20:37
kitlithnods that would be the piece that i'm missing.
#asahi-dev · 2026-03-07 20:35
kitlithchadmed: from my perspective the problem is currently in m1n1, and I'd like to move it out of m1n1. specifically, the fact that m1n1 needs a copy of the device tree that it adds a bunch of details to, and then passes on to uboot, kernel, etc. nothing else can make those changes, so once we're in our boot menu and trying to select between different kernels, we can't select a different devicetree.
#asahi-dev · 2026-03-06 06:53
kitlithare the dynamic bits pulled based on information in the dtb?
#asahi-dev · 2026-03-06 05:10
kitlithI see.
#asahi-dev · 2026-03-06 00:26
kitlithsome idle musing about boot flow: could m1n1 theoretically provide the dynamic bits of the device tree as a device tree overlay, to be merged with <kernel specific devicetree>? granted, the eventual goal is for incompatbilities to not happen in the first place...
#asahi-dev · 2026-02-10 06:53
kitlith(to be clear, when I'm saying consistently above, I mean "continues happening across unplug and replug")
#asahi-dev · 2026-02-10 06:48
kitlithnot very *actionable* right now since i didn't actually gather information
#asahi-dev · 2026-02-10 06:47
kitlithi've previously seen edid consistently not being fully read(?) (modes are present, but name & non-desktop property is absent), as well as the display consistently disconnecting as soon as i attempt to display something on it. both fixed by a reboot.
#asahi-dev · 2026-02-10 06:39
kitlithIs there any state/logs aside from dmesg I should make sure to save/dump on the fairydust branch if I notice that interactions with the external display have started behaving weirdly, before i reboot and it stops happening? (not for right now, but for next time I run into something.)
#asahi-dev · 2026-01-20 09:29
kitlithjannau: https://gitlab.freedesktop.org/kitlith/mesa/-/commit/279e9caf1090017001c235ed3ef9a5dc0a2d6f19 -- i'm not entirely sure that filtering out virtio at this stage is strictly necessary. It does show up as platform bus, I'm pretty sure it'll fail anyway when trying to find the connector, as drm_info fails to get any useful information when running under muvm. But I guess there's also little reason not to filter it out at this stage, aside f
#asahi-dev · 2026-01-15 20:38
kitlithit's not made it to the copr yet, at the very least
#asahi-dev · 2026-01-15 08:04
kitlithThank you, jannau.
#asahi-dev · 2026-01-15 08:03
kitlithi'm out of time to work on this at the moment (I'll be at an event for the next few days), but will try to finish up next week.
#asahi-dev · 2026-01-15 07:52
kitliththanks, chaos_princess
#asahi-dev · 2026-01-15 07:47
kitlithrn i'm trying to track down if there's a known issue that would prevent muvm (0.4.1-3) from working on the fairydust branch.
#asahi-dev · 2026-01-15 07:46
kitlithjannau: i think there were 3 instances? 2 of them inside imagination iirc. (all as in all examples, not large number)
#asahi-dev · 2026-01-15 07:06
kitlithhm. is it just me or are all of these implementations that are checking DRM_BUS_PLATFORM forgetting to drmFreeDevice?
#asahi-dev · 2026-01-15 06:58
kitlithjannau: i'll take the route of panvk_can_present_on_device, since I think I've exhausted the fds I can compare against from this function.
#asahi-dev · 2026-01-15 06:52
kitlithlooks like the renderonly pointer isn't initialized when this is called, anyway.
#asahi-dev · 2026-01-15 06:46
kitlithDoing that alone fixes the issue, yes, but I tend to lean more conservative when I'm not familiar with <other constraints>
#asahi-dev · 2026-01-15 06:33
kitlithbut if it's not supposed to work, given supports_scanout = false...
#asahi-dev · 2026-01-15 06:32
kitlithI've already forced can_present to return true w/ gdb and observed it seemingly working correctly (monado + valve index on the fairydust kernel), but was looking for a route that was upstreamable.
#asahi-dev · 2026-01-15 06:30
kitlithjannau: can_present is the difference between being able to use vkGetDrmDisplayEXT and vkAcquireDrmDisplayEXT or not. I did not observe any checks of supports_scanout in that path.
#asahi-dev · 2026-01-15 06:26
kitlithah. the platform fullname is different. the application i'm testing with passes in a drm fd with platform fullname /soc/display-subsystem, whereas the fd I was comparing against (hk_physical_device.dev.fd) has platform /soc/gpu@<addr>, so they don't compare as equal.
#asahi-dev · 2026-01-15 05:21
kitliththink i'm personally leaning towards wsi_common_drm_devices_equal, but am not fussed either way.
#asahi-dev · 2026-01-15 05:05
kitlithAre there any preferences for which approach should be taken?
#asahi-dev · 2026-01-15 05:04
kitlithI noticed that wsi_device->can_present_on_device in mesa is not overridden by honeykrisp, but it should be since it's a DRM_BUS_PLATFORM device instead of a DRM_BUS_PCI device. There seems to be two approaches taken by the drivers that override this in mesa so far: (1) we're the only DRM_BUS_PLATFORM device on the system, return true if it's a DRM_BUS_PLATFORM device. (2) compare drm device equality using wsi_common_drm_devices_equal.