From: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
To: Kamil Debski <k.debski@samsung.com>
Cc: "'Kyungmin Park'" <kyungmin.park@samsung.com>,
"'Arun Kumar K'" <arun.kk@samsung.com>,
"'Mauro Carvalho Chehab'" <m.chehab@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
"'Daniel Drake'" <drake@endlessm.com>
Subject: Re: [PATCH] [media] s5p-mfc: Use decode status instead of display status on MFCv5
Date: Tue, 23 Sep 2014 16:10:34 +0200 [thread overview]
Message-ID: <1411481434.4050.16.camel@collabora.co.uk> (raw)
In-Reply-To: <085901cfd736$6ae349c0$40a9dd40$%debski@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Hey Kamil,
On Tue, 2014-09-23 at 15:58 +0200, Kamil Debski wrote:
> > Commit 90c0ae50097 changed how the frame_type of a decoded frame
> > gets determined, by switching from the get_dec_frame_type to
> > get_disp_frame_type operation. Unfortunately it seems that on MFC v5
> > the
> > result of get_disp_frame_type is always 0 (no display) when decoding
> > (tested with H264), resulting in no frame ever being output from the
> > decoder.
>
> Could you tell me which firmware version do you use (date)?
I'm using the firmware version as included in
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/
Unfortunately there is no specific version information included about
the firmware. The commit that added it is fb5cda9c70277f6 dated Nov 28
17:43:06 2012 +0530, so that at least gives some information about the
time-frame.
--
Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Collabora Ltd.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6170 bytes --]
prev parent reply other threads:[~2014-09-23 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 12:52 Sjoerd Simons
2014-09-23 13:58 ` Kamil Debski
2014-09-23 14:10 ` Sjoerd Simons [this message]
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=1411481434.4050.16.camel@collabora.co.uk \
--to=sjoerd.simons@collabora.co.uk \
--cc=arun.kk@samsung.com \
--cc=drake@endlessm.com \
--cc=k.debski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.chehab@samsung.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
all inboxes | Powered by JetHome®