public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Stanimir Varbanov <svarbanov@mm-sol.com>,
	Stanimir Varbanov <stanimir.varbanov@linaro.org>,
	Discussion of the development of and with GStreamer
	<gstreamer-devel@lists.freedesktop.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Rob Clark <robdclark@gmail.com>
Cc: ayaka <ayaka@soulik.info>,
	"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>
Subject: Re: gstreamer: v4l2videodec plugin
Date: Sat, 14 May 2016 13:59:13 +0300	[thread overview]
Message-ID: <1463223553.4185.3.camel@collabora.com> (raw)
In-Reply-To: <5735941E.6020703@mm-sol.com>

[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]

Le vendredi 13 mai 2016 à 11:45 +0300, Stanimir Varbanov a écrit :
> yes, of course :)
> 
> Just FYI, I applied the WIP patches on my side and I'm very happy to
> report that they just works. So If you need some testing on qcom
> video
> accelerator just ping me.
> 
> One thing which bothers me is how the extra-controls property
> working,
> i.e. I failed to change the h264 profile for example with below
> construct:
> 
> extra-controls="controls,h264_profile=4;"

While I got you. I would be very interested to know who QCOM driver
interpreted the width and height expose on capture side of the decoder.
I'm adding Philippe Zabel in CC here (he's maintaining the
CODA/Freescale decoder). In Samsung MFC driver, the width and height
expose by the driver is the display size. Though, recently, Philippe is
reporting that his driver is exposing the coded size. Fixing one in
GStreamer will break the other, so I was wondering what other drivers
are doing.

cheers,
Nicolas

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-05-14 10:59 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 [this message]
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=1463223553.4185.3.camel@collabora.com \
    --to=nicolas.dufresne@collabora.com \
    --cc=ayaka@soulik.info \
    --cc=gstreamer-devel@lists.freedesktop.org \
    --cc=linux-media@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robdclark@gmail.com \
    --cc=stanimir.varbanov@linaro.org \
    --cc=svarbanov@mm-sol.com \
    /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