On Tue, Jul 5, 2011 at 1:28 AM, Zhao, Juan J <juan.j.z...@intel.com> wrote: > Meego TV platform have a special function--multi plane(multi pipeline). > On Xorg, we use window manager to support this multi plane function. > When moving to wayland, I think the compositor is still the best place to > support such functionality. > So I raised this question; want to follow the meego compositer authors and > help to add our special functionality into that compositor.
The way it works in Wayland is indeed that the compositor manages the display planes. Whether it's just a single yuv overlay (like much desktop graphics hardware has) or a more flexible multi-plane pipeline, the compositor is in charge of the display hardware. The clients will pass their surfaces to the compositor (including yuv buffers), and the compositor will be able to use a combination of gpu rendering and display planes to present the final output. For example, it can choose to present a fullscreen yuv surface using a yuv plane and then composite subtitles, on-screen controls and a wheater applet into a fullscreen argb display plane on top. If the applet and controls go away in the next frame, it can switch to just displaying the subtitle surface as an overlay. Kristian > ----- > *^_^* BRs, > Juan > > >> -----Original Message----- >> From: meego-dev-boun...@meego.com >> [mailto:meego-dev-boun...@meego.com] On Behalf Of Kristian H?gsberg >> Sent: Thursday, June 30, 2011 10:46 PM >> To: Ville M. Vainio >> Cc: meego-dev@meego.com >> Subject: Re: [MeeGo-dev] which compositer will meego use for wayland? >> >> On Thu, Jun 30, 2011 at 10:22 AM, Ville M. Vainio <vivai...@gmail.com> >> wrote: >> > On Thu, Jun 30, 2011 at 2:41 PM, Thiago Macieira <thi...@kde.org> wrote: >> > >> >> It doesn't. I was going to ask steven what reasons he had for using the qt >> >> compositor. It's just a sample compositor, showing what is possible to do >> >> if >> >> you integrate the wayland libraries into a QML-based application. I've >> >> seen >> >> other experiments doing the same, some of which would definitely never >> qualify >> >> for a product. >> > >> > One advantage of using Qt Compositor as starting point would be making >> > the compositor easy to modify, e.g. for OEM's looking for >> > differentiated experience at compositor level. >> > >> > If you don't get worse performance with Qt Compositor, is there a good >> > reason not to use it (as a starting point again, since it's not a >> > "product" in itself)? >> >> It's not ready yet, and won't be for 1.3. >> >> Kristian >> _______________________________________________ >> MeeGo-dev mailing list >> MeeGo-dev@meego.com >> http://lists.meego.com/listinfo/meego-dev >> http://wiki.meego.com/Mailing_list_guidelines > _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
