From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: "ext Shah, Hardik" <hardik.shah@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"video4linux-list@redhat.com" <video4linux-list@redhat.com>
Subject: RE: [PREVIEW] New display subsystem for OMAP2/3
Date: Mon, 15 Sep 2008 15:36:47 +0300 [thread overview]
Message-ID: <1221482207.6312.69.camel@tubuntu> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB02C4347CE3@dbde02.ent.ti.com>
Hi,
On Mon, 2008-09-15 at 17:22 +0530, ext Shah, Hardik wrote:
>
> DSS library gives the flexibility to change to add the as many overlay managers or as many encoder on the overlay manager.
Is an encoder here the same as an output from DISPC? So OMAP2 and 3 have
two encoders, the tv-out and lcd out?
> > Also I still don't quite know how to present displays to user space.
> > Currently my omapfb just uses the first display, and that's it. I think
> > in the end the user (be it X server, or perhaps some entity over it),
> > needs to have some understanding of what OMAP offers and how it can use
> > the displays. And there probably needs to be some product spesific
> > configuration regarding this in userspace.
> >
> Most of the open source applications are not aware of the hardware capabilities. So it should be transparently handled by the low level drivers/libraries.
That is true, and that's why the default mode should be something
"normal". However, if there are two LCDs on the device, someone has to
understand that only one of them can be updated with DISPC (and thus can
have the overlays), and the other is just a plain framebuffer.
An application doesn't probably have to understand this, but some
display manager entity has. So this is only needed for HW that is
something else than the normal one LCD device.
Tomi
next prev parent reply other threads:[~2008-09-15 12:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 14:55 [PREVIEW] New display subsystem for OMAP2/3 Tomi Valkeinen
2008-09-12 14:29 ` Shah, Hardik
2008-09-12 15:29 ` Daniel Stone
2008-09-13 20:27 ` Koen Kooi
2008-09-13 21:47 ` Måns Rullgård
2008-09-15 8:40 ` Shah, Hardik
2008-09-15 12:05 ` Tomi Valkeinen
2008-09-15 19:27 ` Måns Rullgård
2008-09-17 7:32 ` Tomi Valkeinen
2008-09-17 8:47 ` Måns Rullgård
2008-09-15 11:07 ` Tomi Valkeinen
2008-09-15 11:52 ` Shah, Hardik
2008-09-15 12:36 ` Tomi Valkeinen [this message]
2008-09-15 12:04 ` Daniel Stone
2008-09-15 13:32 ` Hiremath, Vaibhav
2008-09-15 14:38 ` Tomi Valkeinen
2008-09-15 16:20 ` Hiremath, Vaibhav
-- strict thread matches above, loose matches on Subject: below --
2008-10-01 10:51 Hiremath, Vaibhav
2008-10-02 8:24 ` Tomi Valkeinen
2008-10-03 12:47 ` Hiremath, Vaibhav
2008-10-03 13:25 ` Tomi Valkeinen
2008-10-03 13:34 ` Tony Lindgren
2008-10-03 14:16 ` Hiremath, Vaibhav
2008-10-24 9:50 ` Shah, Hardik
2008-10-03 14:03 ` Hans Verkuil
2008-10-03 14: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=1221482207.6312.69.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=hardik.shah@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=video4linux-list@redhat.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