From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Discussion of the development of and with GStreamer
<gstreamer-devel@lists.freedesktop.org>,
Stanimir Varbanov <stanimir.varbanov@linaro.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Rob Clark <robdclark@gmail.com>
Subject: Re: gstreamer: v4l2videodec plugin
Date: Mon, 11 Apr 2016 12:25:08 -0400 [thread overview]
Message-ID: <1460391908.30296.12.camel@collabora.com> (raw)
In-Reply-To: <570B9454.6020307@linaro.org>
Le lundi 11 avril 2016 à 15:11 +0300, Stanimir Varbanov a écrit :
> adding gstreamer-devel
>
> On 04/11/2016 03:03 PM, Stanimir Varbanov wrote:
> >
> > Hi,
> >
> > I'm working on QCOM v4l2 video decoder/encoder driver and in order
> > to
> > test its functionalities I'm using gstreamer v4l2videodec plugin. I
> > am
> > able to use the v4l2videodec plugin with MMAP, now I want to try
> > the
> > dmabuf export from v4l2 and import dmabuf buffers to glimagesink. I
> > upgraded gst to 1.7.91 so that I have the dmabuf support in
> > glimagesink.
> > Mesa version is 11.1.2.
I'm very happy to see this report. So far, we only had report that this
element works on Freescale IMX.6 (CODA) and Exynos 4/5.
> >
> > I'm using the following pipeline:
> >
> > GST_GL_PLATFORM=egl GST_GL_API=gles2 gst-launch-1.0 $GSTDEBUG
> > $GSTFILESRC ! qtdemux name=m m.video_0 ! h264parse ! v4l2video32dec
> > capture-io-mode=dmabuf ! glimagesink
> >
> > I stalled on this error:
> >
> > eglimagememory
> > gsteglimagememory.c:473:gst_egl_image_memory_from_dmabuf:<eglimagea
> > llocator0>
> > eglCreateImage failed: EGL_BAD_MATCH
> >
> > which in Mesa is:
> >
> > libEGL debug: EGL user error 0x3009 (EGL_BAD_MATCH) in
> > dri2_create_image_khr_texture
> >
> > Do someone know how the dmabuf import is tested when the support
> > has
> > been added to glimagesink? Or some pointers how to continue with
> > debugging?
So far the DMABuf support in glimagesink has been tested on Intel/Mesa
and libMALI. There is work in progress in Gallium/Mesa, but until
recently there was no support for offset in imported buffer, which
would result in BAD_MATCH error. I cannot guaranty this is the exact
reason here, BAD_MATCH is used for a very wide variety of reason in
those extensions. The right place to dig into this issue would be
through the Mesa list and/or Mesa code. Find out what is missing for
you driver in Mesa and then I may help you further.
For the reference, the importation strategy we use in GStreamer has
been inspired of Kodi (xmbc). It consist of importing each YUV plane
seperatly using R8 and RG88 textures and doing the color conversion
using shaders. Though, if the frame is allocated as a single DMABuf,
this requires using offset to access the frame data, and that support
had only been recently added in Gallium base code and in Radeon driver
recently. I don't know if Freedreno, VC4 have that, and I know nouveau
don't.
cheers,
Nicolas
next prev parent reply other threads:[~2016-04-11 16:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 12:03 gstreamer: v4l2videodec plugin Stanimir Varbanov
2016-04-11 12:11 ` Stanimir Varbanov
2016-04-11 12:55 ` Víctor M. Jáquez L.
2016-04-12 8:23 ` Stanimir Varbanov
2016-04-11 16:25 ` Nicolas Dufresne [this message]
2016-04-12 8:57 ` Stanimir Varbanov
2016-04-12 12:00 ` Stanimir Varbanov
2016-04-12 15:57 ` Nicolas Dufresne
2016-05-13 8:45 ` Stanimir Varbanov
2016-05-14 10:59 ` Nicolas Dufresne
2016-05-14 12:07 ` Stanimir Varbanov
2016-05-19 13:25 ` Philipp Zabel
2016-05-19 14:37 ` Nicolas Dufresne
2016-05-15 7:41 ` Nicolas Dufresne
2016-05-15 15:02 ` ayaka
2016-04-15 15:58 ` Rob Clark
2016-04-15 16:09 ` Nicolas Dufresne
2016-04-18 14:22 ` Rob Clark
2016-04-28 11:33 ` Stanimir Varbanov
2016-04-29 9:32 ` Stanimir Varbanov
2016-04-29 11:44 ` Rob Clark
2016-05-01 21:48 ` Nicolas Dufresne
2016-05-09 8:13 ` Stanimir Varbanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1460391908.30296.12.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=gstreamer-devel@lists.freedesktop.org \
--cc=linux-media@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=stanimir.varbanov@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox