From: Hans Verkuil <hverkuil@xs4all.nl>
To: Florian Echtler <floe@butterbrot.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: laurent.pinchart@ideasonboard.com, linux-input@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH v3][RFC] add raw video stream support for Samsung SUR40
Date: Mon, 16 Feb 2015 12:40:12 +0100 [thread overview]
Message-ID: <54E1D71C.2000003@xs4all.nl> (raw)
In-Reply-To: <54DB4295.1080307@butterbrot.org>
On 02/11/2015 12:52 PM, Florian Echtler wrote:
> Hello again,
>
> does anyone have any suggestions why USERPTR still fails with dma-sg?
>
> Could I just disable the corresponding capability for the moment so that
> the patch could perhaps be merged, and investigate this separately?
I prefer to dig into this a little bit more, as I don't really understand
it. Set the videobuf2-core debug level to 1 and see what the warnings are.
Since 'buf.qbuf' fails in v4l2-compliance, it's something in the VIDIOC_QBUF
sequence that returns an error, so you need to pinpoint that.
If push comes to shove I can also merge the patch without USERPTR support,
but I really prefer not to do that.
Regards,
Hans
next prev parent reply other threads:[~2015-02-16 11:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 15:30 [PATCH v3][RFC] add raw video stream support for Samsung SUR40 Florian Echtler
2015-02-11 11:52 ` Florian Echtler
2015-02-16 11:40 ` Hans Verkuil [this message]
2015-02-20 21:46 ` Florian Echtler
2015-02-21 10:22 ` Hans Verkuil
2015-03-06 11:24 ` Florian Echtler
2015-03-06 11:47 ` Hans Verkuil
2015-03-07 19:52 ` Florian Echtler
2015-03-07 20:57 ` Hans Verkuil
2015-03-09 9:49 ` Florian Echtler
2015-03-09 10:09 ` Hans Verkuil
2015-03-09 13:45 ` Florian Echtler
2015-03-09 14:02 ` Hans Verkuil
2015-03-12 19:37 ` Florian Echtler
2015-03-15 16:26 ` Hans Verkuil
2015-03-16 8:36 ` Florian Echtler
2015-03-16 8:53 ` Hans Verkuil
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=54E1D71C.2000003@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=floe@butterbrot.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@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;
as well as URLs for NNTP newsgroup(s).