From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Lonsn <lonsn2005@gmail.com>
Cc: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
linux-samsung-soc@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: SMDKV210 support issue in kernel 3.8 (dma-pl330 and HDMI failed)
Date: Thu, 28 Feb 2013 16:54:53 +0100 [thread overview]
Message-ID: <512F7DCD.3040301@samsung.com> (raw)
In-Reply-To: <512F732B.4070804@gmail.com>
On 02/28/2013 04:09 PM, Lonsn wrote:
> HDMI output is OK now, it's a variable init question in 'struct v4l2_buffer
> buf' when call ioctl(fd, VIDIOC_DQBUF, &buf) in the hdmi example application.
> Add m.planes in buf then OK.
> Thanks all!
> I will continue to test the mfc decoder for s5pv210.
Well done! I was going to suggest exactly that to you. It's due to some
change in v4l2-core in recent versions of the kernel. I'll try to update
the example application when I find some time.
Regards,
Sylwester
next prev parent reply other threads:[~2013-02-28 15:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 12:00 SMDKV210 support issue in kernel 3.8 (dma-pl330 and HDMI failed) Lonsn
2013-02-26 12:59 ` Lonsn
2013-02-26 12:59 ` Lonsn
2013-02-26 20:07 ` Sylwester Nawrocki
2013-02-26 20:32 ` Sylwester Nawrocki
2013-02-27 15:13 ` Lonsn
2013-02-27 15:48 ` Lonsn
2013-02-27 15:48 ` Lonsn
2013-02-27 21:41 ` Sylwester Nawrocki
2013-02-28 12:28 ` Lonsn
2013-02-28 15:09 ` Lonsn
2013-02-28 15:09 ` Lonsn
2013-02-28 15:54 ` Sylwester Nawrocki [this message]
2013-02-26 21:22 ` Sylwester Nawrocki
2013-02-26 21:22 ` Sylwester Nawrocki
2013-02-27 10:51 ` Inderpal Singh
2013-02-27 10:51 ` Inderpal Singh
2013-02-27 11:22 ` Sylwester Nawrocki
2013-02-27 11:22 ` Sylwester Nawrocki
2013-02-27 15:32 ` Inderpal Singh
2013-02-27 15:32 ` Inderpal Singh
2013-02-27 15:22 ` Lonsn
2013-02-27 15:22 ` Lonsn
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=512F7DCD.3040301@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lonsn2005@gmail.com \
--cc=sylvester.nawrocki@gmail.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.