#asahi-dev · 2026-03-10 21:36
leioand I'm pretty sure mutter uses overlay planes extensively#asahi-dev · 2026-03-10 21:35
leiothere was https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4745 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4916 and some other churn in there for 50#asahi-dev · 2026-03-10 21:34
leioI think cursors just need to be able to be drawn on overlay planes proper in mutter#asahi-dev · 2026-03-10 21:34
leiojadahl wasn't really opposed to something like this, but looking deeper, I'm not sure how that approach is going to work#asahi-dev · 2026-03-10 21:27
leiooliver: if you can enable it via some quirk system (I see something exists for cogl, though can't spot anything for outside it) and make sure it works with any cursor size, it might be upstreamable; maybe a good starting point for discussion in a draft MR as-is too#asahi-dev · 2026-03-06 18:55
leiochadmed: oliver: there was no refusal from gnome, instead there were technical aspects that need work to make it fit in with what they are doing and no-one who has done such work#asahi-dev · 2026-03-01 19:17
leioIlosariph: the latest release is 0.3.5, which is a tag without the github "release" dance.#asahi-dev · 2026-03-01 16:40
leiosorry, I can't dig into it in any capacity until next weekend#asahi-dev · 2026-03-01 14:57
leioafter a few weeks#asahi-dev · 2026-03-01 14:57
leioI can poke some people if things we need have good MRs and no reactions#asahi-dev · 2026-03-01 14:56
leioit's not really a module that needs a lot of action, just with pipewire entering the scene, it needed some but no-one was there to provide it#asahi-dev · 2026-03-01 14:55
leiofl0_id: if you meant as a reply to me with the 3b78fc commit, then I meant in general, gvc was rather dormant for a while but now someone seems to be actively working on it as of late.#asahi-dev · 2026-03-01 12:39
leiothere's recent upstream activity again in there too#asahi-dev · 2026-02-21 07:53
leionicolas17: I used to have one of those U3224KB, wonder what they needed to quirk there, looked OK for that one, unlike my current G80SD#asahi-dev · 2026-01-31 18:08
leioprobably would just take installing libxkbcommon distro dev package and reconfiguring whatever you're actually building.#asahi-dev · 2026-01-31 18:08
leioPersonally I would investigate why it's building libxkbcommon as a subproject in the first place; if it found the system libxkbcommon development pkg-config file and headers, it probably wouldn't, used your actual system-wide libxkbcommon install for this and not exhibit any of these problems by sidestepping all of that.#asahi-dev · 2026-01-31 18:07
leioso this is strictly a problem with your configuration and local build#asahi-dev · 2026-01-31 18:07
leioit configures it as such in its meson.build and all; this is why you see these #define's#asahi-dev · 2026-01-31 18:07
leiolibxkbcommon will look for its files from where they are supposed to be in its knowledge. If you don't pass a -Dprefix (probably inherited from whatever you are actually building that grabs libxkbcommon as a subrpoject), then that will default to /usr/local, so of course it's going to be trying to load its files at runtime from the place it assumes you are going to be installing it - under /usr/local#asahi-dev · 2026-01-31 18:04
leioI don't know what you are building that has the problem (something using wlroots?), also I doubt this is the correct venue to discuss this#asahi-dev · 2026-01-31 17:55
leioThey do not, it's probably because you built it without specifying a prefix for the install, then it defaults to /usr/local instead of /usr, and the default lookup paths are coded to be in the same prefix as the install of it, but then you also run it locally perhaps. If you don't install it anyways to system (do you?), maybe just configuring with /usr as install prefix is sufficient.#asahi-dev · 2026-01-31 17:00
leiobigmac: /usr/local is not something we'd have unless we make it ourselves. Stuff in the /usr/share variant comes from xkeyboard-config typically. Not sure what env vars you are referencing, but various XDG_* ones are supposed to be treated as a default value existing to a certain specified one by any consumers when the env var is not set#asahi-dev · 2026-01-23 20:23
leioprobably would end up in bits/010-soc in some form#asahi-dev · 2026-01-21 17:55
leioUnable to decrypt message#asahi-dev · 2026-01-21 17:30
leioand of course "better alternatives" is highly debatable :)#asahi-dev · 2026-01-16 22:27
leionevertheless I think that this is something to get very excited about ;)#asahi-dev · 2026-01-14 17:01
leiosounds like no point in investigating unsynn then :)#asahi-dev · 2026-01-10 13:39
leiowouldn't a fork in github have most of the objects already there and not need to push it all?#asahi-dev · 2026-01-09 21:23
leiocan we nerdsnipe jann_au into that vfio thing for AVD next? *g#asahi-dev · 2026-01-08 17:43
leioespecially with the only asahi-capable one being my main workstation too#asahi-dev · 2026-01-08 17:42
leioreally uncomfortable for me to use multiple machines#asahi-dev · 2026-01-08 17:42
leioit would be very motivating for me to poke at it too if I were able to just use this same machine for the dev by not needing it sitting in m1n1#asahi-dev · 2026-01-08 17:15
leiocompared to the status quo#asahi-dev · 2026-01-08 17:15
leioyeah, the biggest win would of course be simply not doing software decoding overall :)#asahi-dev · 2026-01-08 17:12
leiothe latter probably is not relevant for us#asahi-dev · 2026-01-08 17:12
leiothose are the likely reasons apple uses it#asahi-dev · 2026-01-08 17:12
leiothe cm3 probably uses a lot less power, and it can probably be configured to read protected (decrypted) memory (DRM support)#asahi-dev · 2026-01-08 16:58
leioit would probably be useful if the command stream and co stuff would end up as some sort of a documentation beyond a few early blog posts#asahi-dev · 2026-01-08 16:57
leioI also find some talks about the stateless stuff with eiln at https://oftc.catirclogs.org/asahi-dev/2023-09-16# but that was early on, things might have changed with new discoveries or something#asahi-dev · 2026-01-08 16:57
leiosome past discussion was in https://oftc.catirclogs.org/asahi-dev/2025-10-07##asahi-dev · 2026-01-08 16:48
leiothe command stream and such things are of interest in there#asahi-dev · 2026-01-08 16:48
leioto take care of and we won't need to worry about that much, but still#asahi-dev · 2026-01-08 16:48
leiovup: I would also be careful about looking at some of the code - I would stay away from looking at the code borrowed from ffmpeg and elsewhere that is with an unsuitable license (mostly LGPL, things about SPS/PPS parsing in there, etc), as if we end up with a vulkan driver, we want it MIT licensed. Most of that code is probably unnecessary too if we can do vulkan video, as that side in my reading and understanding appears to be the job of the vulkan application #asahi-dev · 2026-01-08 16:46
leiovup: I would suggest to start with trying to replicate the m1n1 based experiments and get it decoding in m1n1; this will need two machines, the M1 or M2 to sit in m1n1 and do the hardware decode and another that then shows what it decoded. I think the experiment only works on either M1 or M2 (what eiln had) and may need some address tweaks for the other.#asahi-dev · 2026-01-08 16:44
leiovup: I made the mistake of starting from that end, but really should start with the AVD side of it, so you'd even be able to tell if vulkan video would work (just from the basis of stateless or not, to start with). But if it's interesting read, why not :)#asahi-dev · 2026-01-08 16:32
leiovup: did we scare you off completely? ;p#asahi-dev · 2026-01-07 21:28
leiootherwise the only option might be stateful v4l; or VA-API if you are into "fun" like trying to make frame-based stuff work with slice-based API that VA-API is.#asahi-dev · 2026-01-07 21:26
leioI believe userspace will pick things up with vulkan video, we shouldn't worry about that for now; main question is - can we do it stateless to even have vulkan video be viable option technically.#asahi-dev · 2026-01-07 21:25
leioseparate vulkan driver can be a bit messy, but Vulkan Core (which clarify having Vulkan driver that have no compute) is coming (or already there, this is months old stuff I'm pulling out)#asahi-dev · 2026-01-07 21:24
leiochats with*