From: Hans Verkuil <hverkuil@xs4all.nl>
To: Florian Echtler <floe@butterbrot.org>
Cc: linux-input <linux-input@vger.kernel.org>, linux-media@vger.kernel.org
Subject: Re: [RFC] [Patch] implement video driver for sur40
Date: Tue, 06 Jan 2015 14:01:42 +0100 [thread overview]
Message-ID: <54ABDCB6.7070807@xs4all.nl> (raw)
In-Reply-To: <54ABD08C.7010107@butterbrot.org>
On 01/06/2015 01:09 PM, Florian Echtler wrote:
> On 06.01.2015 11:23, Hans Verkuil wrote:
>> On 01/06/2015 11:17 AM, Florian Echtler wrote:
>>>> You're not filling in the 'field' field of struct v4l2_buffer when returning a
>>>> frame. It should most likely be FIELD_NONE in your case.
>>>>> fail: v4l2-test-buffers.cpp(611): buf.check(q, last_seq)
>>>>> fail: v4l2-test-buffers.cpp(884): captureBufs(node, q, m2m_q, frame_count, false)
>>> OK, easy to fix. This will also influence the other two warnings, I assume?
>> Most likely, yes.
> Done. I would say that it's nearly ready for submission now (all tests
> from v4l2-compliance -s pass), I still have to sort out all the warnings
> from scripts/checkpatch.pl.
>
>>>>> On a different note, I'm getting occasional warnings in syslog when I run
>>>>> a regular video streaming application (e.g. cheese):
>>> Is there another possible explanation?
>> No :-)
>> You are still missing a buffer somewhere. I'd have to see your latest source code
>> to see what's wrong.
> Weirdly enough, the syslog warning/error doesn't seem to occur anymore
> since I've fixed the v4l2_buffer field. Perhaps some oddity within cheese?
>
> I'm attaching the current source again for you to maybe have another
> look; I will submit a proper patch in the next days.
Just a few quick remarks:
- run scripts/checkpatch.pl over your source, I'm fairly certain it will complain
about several constructs.
- use videobuf2-vmalloc instead of dma-contig. There is no DMA involved, so there
is no reason to use dma-contig.
- Don't set V4L2_CAP_EXT_PIX_FORMAT in querycap: it will be set automatically by
the v4l2 core.
Regards,
Hans
prev parent reply other threads:[~2015-01-06 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 13:34 [RFC] [Patch] implement video driver for sur40 Florian Echtler
2014-12-18 14:11 ` Hans Verkuil
2014-12-19 14:30 ` Florian Echtler
2014-12-19 14:36 ` Hans Verkuil
2014-12-19 14:57 ` Florian Echtler
2014-12-19 15:27 ` Hans Verkuil
2015-01-06 9:29 ` Florian Echtler
2015-01-06 9:36 ` Hans Verkuil
2015-01-06 10:17 ` Florian Echtler
2015-01-06 10:23 ` Hans Verkuil
2015-01-06 12:09 ` Florian Echtler
2015-01-06 13:01 ` Hans Verkuil [this message]
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=54ABDCB6.7070807@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=floe@butterbrot.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
/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.