#
✕ nick:leio
#asahi-dev · 2026-06-27 07:31
leioby my reading firefox supported v4l2 for rpi in 116 and vk video in 153; maybe that's not request api or assumes ffmpeg patches though
#asahi-dev · 2026-06-27 07:28
leiowhat for? Should be possible to use v4l2 directly for firefox for example, might need to fix some support bugs and such though
#asahi-dev · 2026-05-29 08:05
leiodruz: No comment intended on your question, but could reverse engineering AVE be a valid thesis subject as well? :)
#asahi-dev · 2026-05-28 09:09
leio(I guess old codec meant like H.264 in that?)
#asahi-dev · 2026-05-28 09:08
leiothese were*; gave up*
#asahi-dev · 2026-05-28 09:07
leio on these chip concurrently to Apple giving up on them, don't think it was a coincidence, and since we know by now that the GPU is somewhat of a fork of Imagination design, its a possiblilty that the codecs are a fork of their design too; at least for the old codec, and how to compute auxiliary / scratch buffer sizes, that might be key
#asahi-dev · 2026-05-28 09:07
leiosofus: I've been told that if you look at eiln's stuff and compare against driver/media/platform/verisilicon or drivers/media/platform/rockchip decoder drivers, you'll find some strangely similar parameters and patterns, same kind of address and offsets, so you might find some inspiration from there. TI released some open source codec drivers for now abandonned Imagination CODEC; these where hybrid, you could do firmware access, or cpu access; Imagination gave on
#asahi-dev · 2026-05-15 12:08
leiothere's https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31867 with rust bindings and things to write a mesa vulkan video driver.
#asahi-dev · 2026-05-15 11:54
leiosofus: and you understand the details too?
#asahi-dev · 2026-05-15 11:39
leio(but vulkan video is extensively documented in the specs)
#asahi-dev · 2026-05-15 11:38
leiosofus: that's the wrong angle of attack as I found out. We should start understanding the command stream, making sure it's fully stateless, maybe document it more, go from there
#asahi-dev · 2026-05-15 11:25
leiosofus: it isn't necessarily a bad fit, but if vulkan video works for it, then it's just nicer to do all of that in userspace instead in rust than C in v4l2.
#asahi-dev · 2026-04-03 15:35
leio(read: the IRC bridge isn't converting their idea of emoji representation into a proper unicode emoji glyph)
#asahi-dev · 2026-04-03 15:34
leioVarious IRC clients support emoji fine. But you sent some stuff between colons, not an emoji.
#asahi-dev · 2026-03-15 18:37
leiooliver: the commit style CI failures might be good to fix, just in case; but I suspect we just need to wait a bit and then poke on matrix for thoughts
#asahi-dev · 2026-03-13 17:56
leiooliver: used the correct port, right? (it exposes it on a single port only for each machine)
#asahi-dev · 2026-03-12 12:16
leiodid we just snipe oliver into helping stabilize dp-alt? :)
#asahi-dev · 2026-03-12 12:13
leioI think M1 pro HDMI can't push through 120 Hz in 4K for the bandwidth
#asahi-dev · 2026-03-12 12:12
leio(also with considering DSC lowering bandwidth requirements)
#asahi-dev · 2026-03-12 12:11
leiothere are some issues in reaching 240 Hz on some monitors (though that might hit bandwidth limits on what M1 Pro supports) due to DCP firmware not handling some EDID bits with how some monitors expose it, but otherwise it should all be fine, as long as the bandwidth is there from HDMI spec + cable used
#asahi-dev · 2026-03-11 15:52
leiomaybe fedora disabled a cycle earlier
#asahi-dev · 2026-03-11 15:52
leiolike the whole code to support any of that was deleted
#asahi-dev · 2026-03-11 15:52
leiooliver: GNOME upstream does not support X11 sessions anymore, only X apps via xwayland on wayland sessions
#asahi-dev · 2026-03-10 23:08
leiobut now I'm just still confused how all of these things relate to eachother wrt dmabuf surfaces as supposedly used by modern GTK video players vs universal planes vs compositors vs DCP
#asahi-dev · 2026-03-10 23:06
leioIn an ideal world I still like the aspect of compositors being able to use more overlay planes for other things than the cursor, being able to opt to render cursor via SW (or maybe it's disabled overall due to being on top of a video)
#asahi-dev · 2026-03-10 22:58
leioon hindsight should have realized that and tackled it that way for myself 2 years ago
#asahi-dev · 2026-03-10 22:57
leiogreat, I thought we might need to do all of that in the input KMS thread each frame it gets near the edge
#asahi-dev · 2026-03-10 22:55
leioeven better, so you aren't even really affecting the performance critical input thread KMS commit bits that might have a problem if taking too long?
#asahi-dev · 2026-03-10 22:54
leiomaybe that's a problem if the cursor is the size of the whole primary plane? :D
#asahi-dev · 2026-03-10 22:54
leiobut you seem to get away with just always padding and shifting
#asahi-dev · 2026-03-10 22:53
leioto me shift was for a logic of only padding when the size is less than 32x32 and then shifting accordingly to compensate
#asahi-dev · 2026-03-10 22:53
leiooh, yeah, to account for the padding
#asahi-dev · 2026-03-10 22:52
leioI thought that would have been necessary, but apparently not then
#asahi-dev · 2026-03-10 22:52
leioyou didn't do the shift part, it looks like :)
#asahi-dev · 2026-03-10 22:47
leioI don't think that's anything more than "it's hard to do, please help"
#asahi-dev · 2026-03-10 22:47
leiofor mouse cursor you want to know where your click will go to if you click it, not where you were for the rest of the rendering for the use cases where this kind of input latency matters
#asahi-dev · 2026-03-10 22:45
leiohttps://blogs.gnome.org/shell-dev/2021/01/21/threaded-input-adventures/ describes some of that; the problem for asahi comes from the first "what it does not bring yet" point being implemented by now
#asahi-dev · 2026-03-10 22:43
leiothus at the point of time it needs to decide to fallback to SW cursor for the next frame, it doesn't yet have the final position of the mouse cursor if HW were used, thus a atomic commit test to figure out if cursor plane will work can't be reliably done as that might change for the position it's at that time and when it's actually going to be KMS commited
#asahi-dev · 2026-03-10 22:38
leiowhere I'm confused as per above is how is GTK GraphicsOffload stuff as per https://blogs.gnome.org/gtk/2023/11/15/introducing-graphics-offload/ giving zero-copy path when that isn't dealing with overlay planes in the compositor side
#asahi-dev · 2026-03-10 22:34
leiomutter does cursor rendering in what they believe is better, so they can't fallback like that; making use of overlay planes is another big work, it seems like
#asahi-dev · 2026-03-10 22:33
leioI'm now utterly confused about the (GTK) graphics offload work vs overlay planes now from looking into your patch and mutter code
#asahi-dev · 2026-03-10 22:30
leioyes
#asahi-dev · 2026-03-10 21:53
leiothough if something can be done to hide all of this from userspace now, that might be best
#asahi-dev · 2026-03-10 21:53
leiooliver: fwiw, gnome-shell chat is on matrix, but jadahl (who we talked about this before iirc) is one of the few mutter devs still on libera #gnome-shell on IRC side too
#asahi-dev · 2026-03-10 21:46
leio(I think)
#asahi-dev · 2026-03-10 21:45
leiothat's what olive_r's patch does
#asahi-dev · 2026-03-10 21:44
leio(because if it needs to go SW, it needs to be drawn different to include in the scene graph or whatever together with the rest? while with hardware it's placed at the most up to date pointer position instead, closer to the scanout time than the rest of the non-cursor screen damage)
#asahi-dev · 2026-03-10 21:42
leiothe problem is that it needs to decide whether to use HW or SW cursor before that due to that, but if you make HW work, then that's not an issue
#asahi-dev · 2026-03-10 21:42
leioI think the patch is doing the extending and shifting trick inside that low-latency thread?
#asahi-dev · 2026-03-10 21:39
leiooh, nvm, maybe not; GTK is going via dmabuf itself instead

plus ›