From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Chuanbo Weng <strgnm@gmail.com>
Cc: Tomasz Stanislawski <t.stanislaws@samsung.com>,
linux-media@vger.kernel.org
Subject: Re: DMABUF doesn't work when frame size not equal to the size of GPU bo
Date: Tue, 31 Dec 2013 16:19:53 +0100 [thread overview]
Message-ID: <3150357.rYSWurtcIU@avalon> (raw)
In-Reply-To: <CAFu4+mV7D_Ys-tobgtoi92pvuS41mqE71PQf_e0qS_6rOnvV3g@mail.gmail.com>
Hi Chuanbo,
On Tuesday 31 December 2013 19:21:09 Chuanbo Weng wrote:
> 2013/12/31 Tomasz Stanislawski <t.stanislaws@samsung.com>:
> > Hi Chuanbo Weng,
> >
> > I suspect that the problem might be caused by difference
> > between size of DMABUF object and buffer size in V4L2.
>
> Thanks for your reply! I agree with you because my experiment prove it
> (Even when the bo is bigget than frame size, not smaller!!!).
>
> > What is the content of v4l2_format returned by VIDIOC_G_FMT?
>
> The content is V4L2_PIX_FMT_YUYV. (And if the content V4L2_PIX_FMT_MJPEG,
> this issue doesn't happen.)
Could you please give us the content of all the other fields ?
> > What is the content of V4l2_buffer structure passed by VIDIOC_QBUF?
Same here.
> The fd in v4l2_buffer structure is fd of gem object created by
> DRM_IOCTL_MODE_CREATE_DUMB.
>
> I've upload the program that can reproduce this issue on intel platform. You
> just need to clone it from
> https://github.com/strgnm/v4l2-dmabuf-test.git
> Then build and run as said in README.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-12-31 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-25 2:15 DMABUF doesn't work when frame size not equal to the size of GPU bo Chuanbo Weng
2013-12-27 1:55 ` Chuanbo Weng
2013-12-29 15:27 ` Laurent Pinchart
2013-12-31 2:42 ` Chuanbo Weng
2013-12-31 7:43 ` Tomasz Stanislawski
2013-12-31 11:21 ` Chuanbo Weng
2013-12-31 15:19 ` Laurent Pinchart [this message]
2014-01-02 2:22 ` Chuanbo Weng
2014-01-07 8:10 ` Seung-Woo Kim
2014-01-07 10:50 ` Chuanbo Weng
2014-01-21 16:12 ` Laurent Pinchart
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=3150357.rYSWurtcIU@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=strgnm@gmail.com \
--cc=t.stanislaws@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