> -Original Message-
> From: wayland-devel-bounces+juan.j.zhao=intel@lists.freedesktop.org
> [mailto:wayland-devel-bounces+juan.j.zhao=intel@lists.freedesktop.org]
> On Behalf Of Daniel
> Sent: Wednesday, October 19, 2011 2:36 AM
> To: 'wayland-devel@lists.freedesktop.org'
> Subje
2011/10/16 haithem rahmani
> 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 runn
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 relie
From: Ander Conselvan de Oliveira
Move this to a separate function to better accommodate changes in the
following commit.
Signed-off-by: Ander Conselvan de Oliveira
---
compositor/compositor.c | 27 ++-
1 files changed, 18 insertions(+), 9 deletions(-)
diff --git a/
From: Ander Conselvan de Oliveira
On repaint, wlsc_output_repaint will replace output->scanout_buffer with
the new front buffer and then output->present() will cause this buffer
to be displayed. When wlsc_output_finish_frame is called, the
compositor will send a release buffer event for output->s
From: Ander Conselvan de Oliveira
If scanning out a client buffer, the compositor will send a buffer
release event for the front buffer as soon as the flip completes. This
series change the behavior to send the release event for the previous
front buffer.
The second patch is a kind of ugly and d
