All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Nagel <andreasnagel@gmx.net>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-media@vger.kernel.org
Subject: Re: OMAP3 ISP: VIDIOC_STREAMON and VIDIOC_QBUF calls fail
Date: Sat, 10 Nov 2012 14:49:12 +0100	[thread overview]
Message-ID: <509E5B58.1020108@gmx.net> (raw)
In-Reply-To: <20121108092905.GF25623@valkosipuli.retiisi.org.uk>

Sakari Ailus schrieb am 08.11.2012 10:29:
> On Thu, Nov 08, 2012 at 10:26:11AM +0100, Laurent Pinchart wrote:
>> media-ctl doesn't show pad formats, that's a bit weird. Are you using a recent
>> version ?
> This could as well be an issue with the kernel API --- I think that kernel
> has a version which isn't in mainline. So the IOCTL used to access the media
> bus formats are quite possibly different.
>
> Regards,
>

Hi Sakari,
hi Laurent,


first, I could resolve my issues.

When I allocated buffers with the CMEM library from TI (provides aligned 
and contiguous memory buffers), I was able to use user pointers. And 
VIDIOC_STREAMON just failed because of a wrong but similar written 
pixelformat. Since yesterday, I am now able to capture frames and save 
them as YUV data in a file.

My Technexion kernel is based on the TI linux kernel and they 
(Technexion) probably backported some version of Media Controller into 
that kernel. In order to build Laurents media-ctl application, I had to 
rename all MEDIA_* constants in the source files (e.g. MEDIA_PAD_FL_SINK 
into MEDIA_PAD_FLAG_INPUT).
It's probably true, that this implementation is quite different from the 
one in mainline or other kernels. That might also be the reason, why 
media-ctl -p does not print pad formats.
But as long as Technexion keep board support for themselves, I cannot 
use another kernel. I already tried that with some mainline and 
linux-omap versions(3.2, 3.4, 3.6). They don't boot, or if they actually 
do, I don't see anything because network and tty is not available.

Lastly, the TVP5146 indeed generates interlaced frames.

All the best,
Andreas

  reply	other threads:[~2012-11-10 13:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 15:47 OMAP3 ISP: VIDIOC_STREAMON and VIDIOC_QBUF calls fail Andreas Nagel
2012-11-06 21:51 ` Sakari Ailus
2012-11-07 11:22   ` Andreas Nagel
2012-11-08  9:26     ` Laurent Pinchart
2012-11-08  9:29       ` Sakari Ailus
2012-11-10 13:49         ` Andreas Nagel [this message]
2012-11-10 20:22           ` Sakari Ailus
2012-11-12 11:27           ` Laurent Pinchart

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=509E5B58.1020108@gmx.net \
    --to=andreasnagel@gmx.net \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    /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.