From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: "Wu, Josh" <Josh.wu@atmel.com>
Cc: <linux-media@vger.kernel.org>
Subject: Re: Using atmel-isi for direct output on framebuffer ?
Date: Fri, 2 Sep 2011 11:18:53 +0200 [thread overview]
Message-ID: <20110902111853.292d7f26@skate> (raw)
In-Reply-To: <4C79549CB6F772498162A641D92D532802A09156@penmb01.corp.atmel.com>
Hello Josh,
Le Fri, 2 Sep 2011 17:08:32 +0800,
"Wu, Josh" <Josh.wu@atmel.com> a écrit :
> My understanding is that you want to use Atmel ISI to output RGB data
> then work with framebuffer. So yes, it is possible.
Good.
> Since current atmel_isi.c only uses its codec path to output YUV
> data. So first need add RGB format support in
> isi_camera_get_formats(). Then you have two choices to enable RGB
> output of ISI: 1. Enable isi's preview path(DMA, interrupts) to
> convert YUV to RGB. 2. Or still use codec path but don't need add
> much ISI code, just set camera sensor(if it support RGB565 output) to
> output RGB565 data for ISI, then what the data ISI output now should
> be RGB565 format. But in this way you cannot do any scale.
Doing the YUV -> RGB within the V4L2 driver is something I understand
quite well. The part I miss is how the V4L2 driver interacts with the
framebuffer driver to output the camera image into the framebuffer.
> For V4L2_CAP_VIDEO_OVERLAY type driver, I don't know much about that.
Hum, ok, found http://v4l2spec.bytesex.org/spec/x6570.htm which seems
to explain a bit the userspace interface for this.
Thanks for your feedback!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-09-02 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 15:05 Using atmel-isi for direct output on framebuffer ? Thomas Petazzoni
2011-09-01 18:45 ` Guennadi Liakhovetski
2011-09-02 9:08 ` Wu, Josh
2011-09-02 9:18 ` Thomas Petazzoni [this message]
2011-09-02 9:33 ` Sylwester Nawrocki
2011-09-02 11:42 ` Laurent Pinchart
2011-09-02 11:51 ` Thomas Petazzoni
2011-09-02 12:00 ` 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=20110902111853.292d7f26@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=Josh.wu@atmel.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