From: Gary Thomas <gary@mlbassoc.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Using MT9P031 digital sensor
Date: Tue, 08 Nov 2011 05:20:12 -0700 [thread overview]
Message-ID: <4EB91E7C.4050302@mlbassoc.com> (raw)
In-Reply-To: <201111041137.08254.laurent.pinchart@ideasonboard.com>
On 2011-11-04 04:37, Laurent Pinchart wrote:
> Hi Gary,
>
> On Tuesday 01 November 2011 19:52:49 Gary Thomas wrote:
>> I'm trying to use the MT9P031 digital sensor with the Media Controller
>> Framework. media-ctl tells me that the sensor is set to capture using
>> SGRBG12 2592x1944
>>
>> Questions:
>> * What pixel format in ffmpeg does this correspond to?
>
> I don't know if ffmpeg supports Bayer formats. The corresponding fourcc in
> V4L2 is BA12.
ffmpeg doesn't seem to support these formats
>
> If your sensor is hooked up to the OMAP3 ISP, you can then configure the
> pipeline to include the preview engine and the resizer, and capture YUV data
> at the resizer output.
I am using the OMAP3 ISP, but it's a bit unclear to me how to set up the pipeline
using media-ctl (I looked for documentation on this tool, but came up dry - is there any?)
Do you have an example of how to configure this using the OMAP3 ISP?
>
>> * Can I zoom/crop with this driver using the MCF? If so, how?
>
> That depends on what host/bridge you use. The OMAP3 ISP has scaling
> capabilities (controller by the crop rectangle at the resizer input and the
> format at the resizer output), others might not.
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-11-08 12:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 18:52 Using MT9P031 digital sensor Gary Thomas
2011-11-04 10:37 ` Laurent Pinchart
2011-11-08 12:20 ` Gary Thomas [this message]
2011-11-08 12:30 ` Javier Martinez Canillas
2011-11-08 12:33 ` Laurent Pinchart
2011-11-08 12:52 ` Gary Thomas
2011-11-08 13:06 ` Laurent Pinchart
2011-11-08 13:38 ` Gary Thomas
2011-11-08 13:40 ` Gary Thomas
2011-11-09 0:54 ` Laurent Pinchart
2011-11-09 11:01 ` Gary Thomas
2011-11-09 16:18 ` Laurent Pinchart
2011-11-09 16:24 ` Gary Thomas
2011-11-11 14:26 ` Laurent Pinchart
2011-11-14 11:42 ` Gary Thomas
2011-11-16 1:26 ` Laurent Pinchart
2011-11-16 12:03 ` Gary Thomas
2011-11-24 11:28 ` Laurent Pinchart
2011-11-25 11:50 ` Gary Thomas
2011-11-28 11:07 ` Laurent Pinchart
2011-11-28 12:42 ` Gary Thomas
2011-11-28 12:49 ` Laurent Pinchart
2011-11-28 12:53 ` Gary Thomas
2011-11-30 14:13 ` Gary Thomas
2011-11-30 14:30 ` Laurent Pinchart
2011-11-30 14:38 ` Hiremath, Vaibhav
2011-11-30 14:57 ` Gary Thomas
2011-11-30 17:00 ` Gary Thomas
2011-11-30 23:49 ` Laurent Pinchart
2011-11-30 23:42 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2012-03-23 19:01 Joshua Hintze
2012-03-26 5:13 ` Joshua Hintze
2012-03-26 8:25 ` Laurent Pinchart
2012-03-26 15:44 ` Joshua Hintze
2012-03-26 17:38 ` Laurent Pinchart
2012-03-26 17:43 ` Joshua Hintze
[not found] ` <4F708A66.8090303@mlbassoc.com>
2012-03-26 15:37 ` Joshua Hintze
2012-03-26 16:32 ` Gary Thomas
2012-03-26 16:55 ` Joshua Hintze
2012-03-27 14:44 ` jean-philippe francois
2012-03-29 11:33 ` 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=4EB91E7C.4050302@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=laurent.pinchart@ideasonboard.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