#asahi-dev · 2026-09-24 12:52
ndufresneLarstiQ yep, regular temperature, I was also reproducing in Montreal trying to daily that phone (it never worked well though)#asahi-dev · 2026-09-24 12:29
ndufresneFun fact, I remember working on the display controller of the OpenMoko Freerunner, and one bug requires to place the phone in the freezer for 30min or so and resume from suspend at low temprature to reproduce#asahi-dev · 2026-09-24 12:28
ndufresneIf there is anything in Weston that is incompatible with asahi gpu driver, file an issue, I'm sure we can fix it, but I'm not saying its good for desktop, use kde/mutter/wlroot based stuff, but its been better for testing overlay/underlay at low level then kmssink#asahi-dev · 2026-09-24 12:27
ndufresnechadmed ok, Canadian loves talking about weather, but you lost me about breeze and mercury here !#asahi-dev · 2026-09-24 11:49
ndufresneIt would be nice to keep kms bit in shape, but it needs work, and needs HW specific allocation support#asahi-dev · 2026-09-24 11:48
ndufresneRight, for testing on Wayland I aim for Weston, which has less magic, more config, but I won't hide that I work with bunch of Weston devs to help me#asahi-dev · 2026-09-24 11:30
ndufresneRight, kmssink is on its decay, I don't use it anymore myself, I always go for Wayland (Weston for niche use case, mutter/KDE for desktop work)#asahi-dev · 2026-09-24 11:18
ndufresneLet's say, we got away for now with AFBC since it's a single plane, we need to do more work, rmader was on that recently #asahi-dev · 2026-09-24 11:16
ndufresneBut we can code HW specific offset calculations in gst v4l plugin, it's much more productive then wait for v4l3#asahi-dev · 2026-09-24 11:14
ndufresnesofus: I'm missing some context, but it seems unlikely, specially for when opaque DRM formats are negotiated. But perhaps you mean we don't interpolate offset and second stride, I know there is still few gaps to fill there when drivers uses single allocation (which in v4l is forces to use the single plane interface, the API is really bad)#asahi-dev · 2026-09-20 17:38
ndufresneBtw, nice work on getting the decoder driver to the mailing list, since it all RE, and this HW is meant to be firmware accessed (and you don't have the firmware) its all very impressive!#asahi-dev · 2026-07-21 18:19
ndufresneJust different endian ?#asahi-dev · 2026-07-20 13:49
ndufresnestill think VV is a long term direction to take#asahi-dev · 2026-07-20 13:49
ndufresneThis does not help the dilema of VV vs V4L2 ... though VV is frame based in its flow#asahi-dev · 2026-07-20 13:48
ndufresneBut its not really a thing today, I talks to about it to the Linux Media group already, have lined up a talk at Linux Plumber in Prague this year, and we have a encoder (kernel side in Rust as a bonus) in the development for the RK3588 chips#asahi-dev · 2026-07-20 13:47
ndufresneWe are working on introduce VV specific (HW specific) drivers in the long term to slim down the software, and more some bits to userspace in the long run#asahi-dev · 2026-07-20 13:46
ndufresneOn HEVC we have a third mode, frame based with slices, this allow for batching in slice based HEVC decoder, or for less capable frame based decoders#asahi-dev · 2026-07-20 13:45
ndufresnehi sofus, at linux kernel level, the V4L2 stateless API supports both slice and frame based decoders, this is because Allwinner CPU access codecs are slice based, but most other are frame based#asahi-dev · 2026-07-20 13:43
ndufresneo/