From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Rob Clark <robdclark@gmail.com>,
Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: Discussion of the development of and with GStreamer
<gstreamer-devel@lists.freedesktop.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: gstreamer: v4l2videodec plugin
Date: Fri, 15 Apr 2016 12:09:55 -0400 [thread overview]
Message-ID: <1460736595.973.5.camel@ndufresne.ca> (raw)
In-Reply-To: <CAF6AEGvjin7Ya4wAXF=5vAa=ky=yvUHnYSo8Of_cyd8TCc04UQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Le vendredi 15 avril 2016 à 11:58 -0400, Rob Clark a écrit :
> The issue is probably the YUV format, which we cannot really deal
> with
> properly in gallium.. it's a similar issue to multi-planer even if
> it
> is in a single buffer.
>
> The best way to handle this would be to import the same dmabuf fd
> twice, with appropriate offsets, to create one GL_RED eglimage for Y
> and one GL_RG eglimage for UV, and then combine them in shader in a
> similar way to how you'd handle separate Y and UV planes..
That's the strategy we use in GStreamer, as very few GL stack support
implicit color conversions. For that to work you need to implement the
"offset" field in winsys_handle, that was added recently, and make sure
you have R8 and RG88 support (usually this is just mapping).
cheers,
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-04-15 16:10 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
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 [this message]
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=1460736595.973.5.camel@ndufresne.ca \
--to=nicolas@ndufresne.ca \
--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