From: "Jakub Piotr Cłapa" <jpc-ml@zenburn.net>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock]
Date: Fri, 26 Jul 2013 21:02:35 +0200 [thread overview]
Message-ID: <51F2C7CB.9040806@zenburn.net> (raw)
In-Reply-To: <2345948.CFuZYJZjKT@avalon>
On 26.07.13 17:52, Laurent Pinchart wrote:
>>> Using omapfb, or...? I hope not
>>> omap_vout, because that's rather unmaintained =).
>>
>> Laurent's live application is using the V4L2 API for video output (to
>> get free YUV conversion and DMA) so I guess this unfortunatelly counts
>> as using omap_vout. Are there any alternatives I should look into? IIUC
>> to use omapfb I would need to manually copy RGB data into the
>> framebuffer on each frame.
>
> It should be possible to port the live application to use DRM/KMS with omapdrm
> for the display side, without requiring any memory copy. That's somewhere on
> my TODO list, but I won't have time to work on that before way too long.
I could look into it myself but is there any documentation on omapdrm?
From what I found libdrm should probably be used but information about
it's API is really scarce:
https://dvdhrm.wordpress.com/2012/09/13/linux-drm-mode-setting-api/
http://dvdhrm.wordpress.com/2012/12/21/advanced-drm-mode-setting-api/
http://virtuousgeek.org/blog/index.php/jbarnes/2011/10/31/writing_stanalone_programs_with_egl_and_
The last one seems focused on OpenGL so I don't think it applies.
Are there any good sources to learn about this? Or maybe some pointers
on where to start with reading source code?
--
regards,
Jakub Piotr Cłapa
LoEE.pl
next prev parent reply other threads:[~2013-07-26 19:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 1:00 [omap3isp] xclk deadlock Jakub Piotr Cłapa
2013-07-04 20:21 ` Jakub Piotr Cłapa
2013-07-04 21:11 ` Laurent Pinchart
2013-07-04 22:36 ` Jakub Piotr Cłapa
2013-07-05 10:48 ` Laurent Pinchart
2013-07-12 14:44 ` Jakub Piotr Cłapa
2013-07-17 12:50 ` Laurent Pinchart
2013-07-17 22:17 ` Jakub Piotr Cłapa
2013-07-26 15:51 ` Laurent Pinchart
2013-07-26 23:51 ` Jakub Piotr Cłapa
2013-07-26 7:50 ` Tomi Valkeinen
2013-07-26 15:37 ` [omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock] Jakub Piotr Cłapa
2013-07-26 15:52 ` Laurent Pinchart
2013-07-26 19:02 ` Jakub Piotr Cłapa [this message]
2013-07-26 19:13 ` Laurent Pinchart
2013-07-29 6:19 ` Tomi Valkeinen
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=51F2C7CB.9040806@zenburn.net \
--to=jpc-ml@zenburn.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=tomi.valkeinen@ti.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