05:15 <anarsoul> linkmauve: it means that likely vertex shader is too complex

09:34 <linkmauve> Hmm, what are the limits?

17:09 <kwizart> hello here, I'm experiencing a crash for lima on 5.8.18-300.fc33.aarch64 (fedora 33 userspace) with AML-S805X-AC

17:10 <kwizart> https://paste.centos.org/view/636faf1c

17:12 <kwizart> My current workaround is to use rd.driver.blacklist=lima (when initramfs is created with dracut). That prevent lima from been loaded during the initramfs (and specially after the full meson stack is loaded as meson_dw_hdmi is within the initramfs)

17:13 <kwizart> Questions: 1/ Is there a bug tracker to properly report this issue ? 2/ any idea for a fix ?

18:04 <anarsoul> kwizart: https://gitlab.freedesktop.org/lima/linux/-/issues

18:05 <kwizart> thx, reporting...

18:07 <kwizart> slowly advancing, is it expected to use libva_v4l2_request with meson_vdec ? Seems like I'm missing a /dev/media0 to work with it...

18:09 <linkmauve> Oh, TIL about /dev/media0, so this is the rumoured new v4l2 request API?

18:10 <linkmauve> On 5.8.9 (but on an Allwinner SoC) I have this device.

18:12 <jernej> kwizart: meson_vdec implements stateful v4l2 codec, not request api

18:12 <jernej> so no, it won't work with that lib

18:12 <jernej> besides, that's not lima related :)

18:22 <kwizart> report: https://gitlab.freedesktop.org/lima/linux/-/issues/36

18:23 <kwizart> thx for the tips about stateful/stateless I will fail to remember each cases

18:23 <kwizart> I wonder which player would support the stateful v4l2 codec yet ?

18:24 <kwizart> but indeed, not a #lima issue (wonder where meson would live)

18:24 <linkmauve> kwizart, any using ffmpeg’s *_v4l2m2m codecs.

18:34 <xdarklight> kwizart: there's #linux-amlogic for Amlogic things