From: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
To: Jean-Michel Hautbois <jean-michel.hautbois@veo-labs.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] cx18: Fix VIDIOC_TRY_FMT to fill in sizeimage and bytesperline
Date: Wed, 25 Nov 2015 09:53:45 +0000 [thread overview]
Message-ID: <4726783.suCipCVCmC@f19simon> (raw)
In-Reply-To: <CAH-u=81v76v0dYb64RAF-q0fuF2TCor=SKm3h3POpxOO5Fb4YA@mail.gmail.com>
On Tuesday 24 November 2015 21:27:33 Jean-Michel Hautbois wrote:
> Hi,
> Le 24 nov. 2015 19:46, "Simon Farnsworth" <simon.farnsworth@onelan.co.uk> a écrit :
> >
> > I was having trouble capturing raw video from GStreamer; turns out that I
> > now need VIDIOC_TRY_FMT to fill in sizeimage and bytesperline to make it work.
>
> You could have used v4l2-compliance tool it would give you at least (I don't have the HW to test) this error. Would save your time :-)
It only took me 2 minutes to find - I'd have spent longer getting
v4l2-compliance running :)
As I'm not going to have access to the hardware after Friday, I'll leave
getting a full v4l2-compliance pass to someone else.
> > Signed-off-by: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
> > ---
> >
> > I'm leaving ONELAN on Friday, so this is a drive-by patch being sent for the
> > benefit of anyone else trying to use raw capture from a cx18 card. If it's
> > not suitable for applying as-is, please feel free to just leave it in the
> > archives so that someone else hitting the same problem can find my fix.
> >
<snip>
--
Simon Farnsworth
Software Engineer
ONELAN Ltd
http://www.onelan.com
next prev parent reply other threads:[~2015-11-25 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 18:09 [PATCH] cx18: Fix VIDIOC_TRY_FMT to fill in sizeimage and bytesperline Simon Farnsworth
[not found] ` <CAH-u=81v76v0dYb64RAF-q0fuF2TCor=SKm3h3POpxOO5Fb4YA@mail.gmail.com>
2015-11-25 9:53 ` Simon Farnsworth [this message]
2015-11-27 13:37 ` 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=4726783.suCipCVCmC@f19simon \
--to=simon.farnsworth@onelan.co.uk \
--cc=jean-michel.hautbois@veo-labs.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox