running Wayland on set-top-box

[Zhao, Juan J]

> -----Original Message-----
> From: wayland-devel-bounces+juan.j.zhao=intel.com at lists.freedesktop.org
> [mailto:wayland-devel-bounces+juan.j.zhao=intel.com at lists.freedesktop.org]
> On Behalf Of Daniel
> Sent: Wednesday, October 19, 2011 2:36 AM
> To: 'wayland-devel at lists.freedesktop.org'
> Subject: RE: running Wayland on set-top-box
> 
> El dl 17 de 10 de 2011 a les 08:12 +0800, en/na Zhao, Juan J va
> escriure:
> > Yes, you problem can be resolved by a wayland compositor with a
> > DirectFB backend.
> >
> > The compositor’s drawing work can be done by directFB with your own HW
> > acceleration.
> 
> I was under the impression that Wayland relied on clients using EGL for
> drawing, as EGL buffers is all it understands. Is that wrong?
> 

DirectFB can also use EGL/GLESv2 with kms/drm for drawing. Wayland can try to get the egl context or create another egl context to do the drawing work. 
If DirectFB uses framebuffer directly, wayland can still create its EGL context and use gl.
And of course, we hope with DirectFB, we would like to use DirectFB to draw. We can modify the output related interface to do this.

> > Be patient, there will be such an component sooner or later. J
> >
> 
> What code would need to be written to have a framebuffer version of
> Wayland?
For wayland running on directfb, we need to write a wayland-directfb backend.
We need to fix the following problems: How to init egl with directfb, the mechanism of the output surfaces and the input mechanisms.

> >
> >
> > -----
> >
> > *^_^* BRs,
> >
> > Juan
> >
> >
> >
> > From: wayland-devel-bounces
> > +juan.j.zhao=intel.com at lists.freedesktop.org
> > [mailto:wayland-devel-bounces
> > +juan.j.zhao=intel.com at lists.freedesktop.org] On Behalf Of haithem
> > rahmani
> > Sent: Monday, October 17, 2011 4:43 AM
> > To: wayland-devel at lists.freedesktop.org
> > Subject: Re: running Wayland on set-top-box
> >
> >
> >
> >
> >         I read on Phoronix that Wayland can run on plain Linux
> >         framebuffer, you
> >         could also try building Mesa with just swrast without the
> >         accelerated
> >         drivers but I'm not sure how it works (performance might be
> >         degraded) and I
> >         haven't tried since I'm currently running Wayland on Nouveau
> >         (finally I can
> >         see something, just the window decorator but that's way better
> >         than
> >         garbage).
> >
> >
> http://www.phoronix.com/scan.php?page=news_item&px=ODgxMg
> >
> http://www.phoronix.com/scan.php?page=news_item&px=OTI0MA
> >
> >
> >
> >
> > OK, but it said that a simple terminal consumed 8Gb of RAM, I don't
> > have such memory on
> >
> >
> > a set-top-box :(
> >
> >
> >
> >
> >
> >
> >
> >
> >         If your application is written using GTK+ or Qt it might be
> >         better to try
> >         running it on DirectFB instead of using Wayland.
> >
> >
> >
> >
> > Actually this is the origin of my issues, GTK+-3.x has dropped the
> > directfb backend and
> >
> >
> > is providing a wayland one now, qt lighthouse will be based on wayland
> > too, and in the set-top-box world the most famous library supporting
> > hw acceleration is DirectFB, so I'm looking to see if it is possible
> > to have wayland on DirectFB or not.
> >
> >
> >
> >
> >
> > --
> >
> >
> > "If you ask a question - you will be a fool for 5 minutes, otherwise
> > ignorant for rest of your life"
> >
> >
> >
> >
> >
> > _______________________________________________
> > wayland-devel mailing list
> > wayland-devel at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/wayland-devel
> 
> 
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel