Hi Laurent and Tomasz,
As I said in my previous email, you can download the code from
the github address.
I think you can easily reproduce this issue by running my program
(Especially Laurent) and
get more information from this program.
Could you please tell me whether you have reproduced this issue?
Thanks,
Chuanbo Weng
2013/12/31 Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>:
> Hi Chuanbo,
>
> On Tuesday 31 December 2013 19:21:09 Chuanbo Weng wrote:
>> 2013/12/31 Tomasz Stanislawski <t.stanislaws@xxxxxxxxxxx>:
>> > 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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
