From: "Maik Steuer" <Maik.Steuer@gmx.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: video4linux-list@redhat.com, kernel@pengutronix.de
Subject: Re: testing soc_camera with mt9m001 on pxa270
Date: Mon, 01 Dec 2008 11:35:05 +0100 [thread overview]
Message-ID: <20081201103505.79550@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0811281755510.4430@axis700.grange>
-------- Original-Nachricht --------
> Datum: Fri, 28 Nov 2008 18:00:47 +0100 (CET)
> Von: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> An: Maik Steuer <Maik.Steuer@gmx.de>
> CC: kernel@pengutronix.de, video4linux-list@redhat.com
> Betreff: Re: testing soc_camera with mt9m001 on pxa270
> On Fri, 28 Nov 2008, Maik Steuer wrote:
>
> > > I would suggest you tell us what camera you are going to use, maybe
> > > someone is already working on a driver for it. If not - you write a
> driver
> > > yourself and start working with a real hardware.
> >
> > At the moment the camera is only a FPGA which sends 8 Bit dummy data
> > with hsync, vsync and pixclock. So I can change all necessary parameters
> > for pxa requirements.
> >
> > I throught that the ioctl (fd, VIDIOC_REQBUFS, &req) starts
> > soc_camera_reqbufs() but it isn't so.
>
> Yes, this is indeed what should happen: see __video_do_ioctl() and around
> it. You're saying, that VIDIOC_REQBUFS is the first failing ioctl? Then
Yes, VIDIOC_REQBUFS is the first failling. The right case construction wasn't called. I printed out the commited ioctl cmd and the unsigned integer value for VIDIOC_REQBUFS:
<7>pxa27x-camera: VIDIOC_REQBUFS
<7>switch(c0105608) VIDIOC_REQBUFS = c0145608
They are different! That's the problem. The capture.c example use #include <linux/videodev2.h> but the v4l2-ioctl.c use declarations in #include <media/v4l2-ioctl.h> for the VIDIOC_REQBUF define macro.
Is there a known version conflict?
> just check what error code it returns, activate the
>
> dev_dbg(&icd->dev, "%s: %d\n", __func__, p->memory);
>
> in soc_camera.c::soc_camera_reqbufs(), etc.
>
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
greets
Maik
--
Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL
für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-12-01 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 14:58 testing soc_camera with mt9m001 on pxa270 Maik Steuer
2008-11-28 15:16 ` Guennadi Liakhovetski
2008-11-28 16:26 ` Maik Steuer
2008-11-28 17:00 ` Guennadi Liakhovetski
2008-12-01 10:35 ` Maik Steuer [this message]
2008-12-01 10:43 ` Guennadi Liakhovetski
2008-12-01 14:37 ` Mauro Carvalho Chehab
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=20081201103505.79550@gmx.net \
--to=maik.steuer@gmx.de \
--cc=g.liakhovetski@gmx.de \
--cc=kernel@pengutronix.de \
--cc=video4linux-list@redhat.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