From: Arun Kumar K <arunkk.samsung@gmail.com>
To: Kamil Debski <k.debski@samsung.com>,
'Arun Kumar K' <arun.kk@samsung.com>,
linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
posciak@chromium.org, avnd.kiran@samsung.com
Subject: Re: [PATCH v2] [media] s5p-mfc: add init buffer cmd to MFCV6
Date: Fri, 09 May 2014 10:06:18 +0530 [thread overview]
Message-ID: <536C5B42.2060208@gmail.com> (raw)
In-Reply-To: <004c01cf6ad9$bcc0e780$3642b680$%debski@samsung.com>
Hi Kamil,
On 05/08/14 21:52, Kamil Debski wrote:
> Hi,
>
>> From: Arun Kumar K [mailto:arunkk.samsung@gmail.com] On Behalf Of Arun
>> Kumar K
>> Sent: Tuesday, March 11, 2014 10:16 AM
>>
>> From: avnd kiran <avnd.kiran@samsung.com>
>>
>> Latest MFC v6 firmware requires tile mode and loop filter setting to be
>> done as part of Init buffer command, in sync with v7. Since there are
>> two versions of v6 firmware with different interfaces, it is
>> differenciated using the version number read back from firmware which
>> is a hexadecimal value based on the firmware date.
>
> MFC version has two parts major and minor. Are you sure that date is
> the only way to check if the interface has changed? Maybe the major number
> should stay the same (6) in this case, and the minor should be updates?
> Do you have contact with persons writing the firmware?
>
Yes I contacted with the firmware team and there is no difference in the
minor number too. Both the versions will read as MFC v6.5. Only
difference is the firmware date.
> Also, I don't see a patch with the newer firmware posted to linux-firmware.
> When it is going to be sent?
>
I will send it along with the v7 firmware.
Regards
Arun
> Best wishes,
>
next prev parent reply other threads:[~2014-05-09 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 9:15 [PATCH v2] [media] s5p-mfc: add init buffer cmd to MFCV6 Arun Kumar K
2014-05-08 16:22 ` Kamil Debski
2014-05-09 4:36 ` Arun Kumar K [this message]
2014-05-13 9:19 ` Kamil Debski
2014-05-13 9:57 ` Arun Kumar K
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=536C5B42.2060208@gmail.com \
--to=arunkk.samsung@gmail.com \
--cc=arun.kk@samsung.com \
--cc=avnd.kiran@samsung.com \
--cc=k.debski@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=posciak@chromium.org \
--cc=s.nawrocki@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.