From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: josh.wu@atmel.com
Cc: linux-media@vger.kernel.org
Subject: Using atmel-isi for direct output on framebuffer ?
Date: Thu, 1 Sep 2011 17:05:55 +0200 [thread overview]
Message-ID: <20110901170555.568af6ea@skate> (raw)
Hello Josh,
I am currently looking at V4L2 and your atmel-isi driver for an AT91
based platform on which I would like the ISI interface to capture the
image from a camera and have this image directly output in RGB format
at a specific location on the screen (so that it can be nicely
integrated into a Qt application for example).
At the moment, I grab frames from the V4L2 device to userspace, do the
YUV -> RGB conversion manually in my application, and then displays the
converted frame on the framebuffer thanks to normal Qt painting
mechanisms. This works, but obviously consumes a lot of CPU.
>From the AT91 datasheet, I understand that the ISI interface is capable
of doing the YUV -> RGB conversion and is also capable of outputting
the frame at some location in the framebuffer, but I don't see how to
use this capability with the Linux V4L2 and framebuffer infrastructures.
Is this possible ? If so, could you provide some pointers or starting
points to get me started ? If not, what is missing in the driver ?
Thanks a lot,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2011-09-01 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 15:05 Thomas Petazzoni [this message]
2011-09-01 18:45 ` Using atmel-isi for direct output on framebuffer ? Guennadi Liakhovetski
2011-09-02 9:08 ` Wu, Josh
2011-09-02 9:18 ` Thomas Petazzoni
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=20110901170555.568af6ea@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 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.