On Tue, Aug 09, 2022 at 02:45:08PM +0200, Michael Grzeschik wrote:
On Thu, Apr 28, 2022 at 12:44:37AM +0200, Nicolas Frattaroli wrote:The RK3566 and RK3568 SoCs come with a small Hantro instance which is solely dedicated to encoding JPEG. This patch adds the necessary structs to the Hantro driver to allow it to function. Tested with the following GStreamer command: gst-launch-1.0 videotestsrc ! v4l2jpegenc ! matroskamux ! \ filesink location=foo.mkvI just tried this pipeline on v5.19. The filesize generated is increasing and data is generated. However the content seems to be unusable. When playing foo.mkv with e.g. vlc the following errors, that no JPEG data was found in the images, is generated: [mjpeg @ 0x7f2f08c1f780] No JPEG data found in image [mjpeg @ 0x7f2f08c1f780] No JPEG data found in image [mjpeg @ 0x7f2f08c1f780] No JPEG data found in image ... The same with gstreamer: gst-launch-1.0 filesrc location=foo.mkv ! decodebin ! glimagesink ../ext/jpeg/gstjpegdec.c(1418): gst_jpeg_dec_handle_frame (): /GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstJpegDec:jpegdec0: Decode error #53: Not a JPEG file: starts with 0x00 0x00 .. Do you have an idea why that is? Did you test the pipeline with an earlier kernelversion and validated the generated content of foo.mkv?
After further debugging, I found out that my latest port of the bootlin patches to support h264 encoding broke the hantro driver somehow. https://git.pengutronix.de/cgit/mgr/linux/log/?h=v5.19/topic/rk3568-vepu-h264-stateless-bootlin The good news about that is; it is possible that the same issue was the cause that I thought the h264 encoding is not supported on the VEPU121. So the support is still unknown I will come back to that. Regards, Michael -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Attachment:
signature.asc
Description: PGP signature
