07:11 <digetx> kwizart: I may try to add t124 v4l support to kernel driver and gstreamer, but then you'll need to build whole gstreamer to test it; it's not difficult to build it, but nevertheless it will take some extra time and effort, will you be able to build and test it?

07:13 <digetx> btw, turned out v4l memory management isn't that bad, though it's still not ideal, it's the yuv format mess that is the problem, apparently neither kernel nor userspace devs are getting it right

09:00 <kwizart> digetx, sure I can test with gstreamer patches. But I wonder why ? v4l2-m2m is working with mpv/ffmpeg. Do you mean you need to improve the v4l2-m2m API ?

09:01 <digetx> AFAIK, ffmpeg doesn't support h264 v4l-m2m

09:03 <kwizart> well, ffmpeg -decoders |grep m2m

09:03 <kwizart> V..... h264_v4l2m2m V4L2 mem2mem H.264 decoder wrapper (codec h264)

09:04 <kwizart> that's the why it's supported with downstream raspberry-pi kernel (instead of the deprecated MMAL API)

09:04 <kwizart> way

09:08 <digetx> that should be a something different, we need V4L2_PIX_FMT_H264_SLICE format, not V4L2_PIX_FMT_H264

09:08 <digetx> also nothing supports t124 tiling framebuffer format, it needs to be supported separately