Prigent, Christophe wrote:
Bill,
Can you find out if my "fix" of printing to a terminal on the same
screen also works on your system?
Is this fix integrated?
I recently synchronized and built again. I'm still reproducing the problem of
slowness.
No, my "fix" is bogus. It relies on a prin
wayland-devel-bounces+christophe.prigent=intel@lists.freedesktop.org
[mailto:wayland-devel-bounces+christophe.prigent=intel@lists.freedesktop.org]
On Behalf Of Ander Conselvan de Oliveira
Sent: Monday, June 11, 2012 10:07 AM
To: Bill Spitzak
Cc: wayland
Subject: Re: Patch that "fixes
On 06/08/2012 10:26 PM, Bill Spitzak wrote:
Actually I am running classic with no effects already and I am having
this bug.
That explains why nothing happened when I ran ccsm and turned the
detector on/off. There was no program to kill/restart.
Ok, so we're dealing with different problems.
U
Actually I am running classic with no effects already and I am having
this bug.
That explains why nothing happened when I ran ccsm and turned the
detector on/off. There was no program to kill/restart.
Unless the x11_compositor_handle_event() is the *last* thing called
before it does the epol
On 06/06/2012 04:10 AM, Bill Spitzak wrote:
On 06/05/2012 02:09 PM, Kristian Høgsberg wrote:
Argh, you're right, thanks. But you said that just adding the count
and returning that alone didn't fix it, right? I wonder if we need a
xcb_flush(compositor->conn);
in x11_output_repaint() after the
On 06/05/2012 02:09 PM, Kristian Høgsberg wrote:
Argh, you're right, thanks. But you said that just adding the count
and returning that alone didn't fix it, right? I wonder if we need a
xcb_flush(compositor->conn);
in x11_output_repaint() after the eglSwapBuffers() call. Maybe just
Kristian Høgsberg wrote:
Argh, you're right, thanks. But you said that just adding the count
and returning that alone didn't fix it, right? I wonder if we need a
xcb_flush(compositor->conn);
in x11_output_repaint() after the eglSwapBuffers() call. Maybe just
before returning from
x1
On Tue, Jun 5, 2012 at 3:11 PM, Bill Spitzak wrote:
> Kristian Høgsberg wrote:
>
>> What do you mean by "produces a composite" and how do you know? The
>> x11 backend renders every 10ms when it's rendering continuously, not
>> after every X event. At least that's how it's supposed to work (and
>
Kristian Høgsberg wrote:
What do you mean by "produces a composite" and how do you know? The
x11 backend renders every 10ms when it's rendering continuously, not
after every X event. At least that's how it's supposed to work (and
how it works here), if that doesn't happen for you, it would be
On Sun, Jun 03, 2012 at 12:12:20AM -0700, Bill Spitzak wrote:
> For me weston compositor-x11 always ran really slow, as it produces
> a composite after every X event. I managed to "fix" this with the
> attached patch, and now multiple X events are read at a time, making
> wayland look *much* faster
ayland-devel-bounces+christophe.prigent=intel@lists.freedesktop.org]
On Behalf Of Prigent, Christophe
Sent: Tuesday, June 05, 2012 10:40 AM
To: Bill Spitzak; wayland
Subject: RE: Patch that "fixes" compositor-x11
Hello,
I'm also having the problem.
I'm using Ubuntu 11.04. M
he.prigent=intel@lists.freedesktop.org
[mailto:wayland-devel-bounces+christophe.prigent=intel@lists.freedesktop.org]
On Behalf Of Bill Spitzak
Sent: Monday, June 04, 2012 10:38 PM
To: wayland
Subject: Re: Patch that "fixes" compositor-x11
Any comments or insight on this proble
Any comments or insight on this problem?
I'm wondering if the slowness of compositor-x11 is a problem that only I
am encountering? If everybody else is using much faster machines perhaps
they won't see it, though I think if you run enough clients it should be
obvious on any machine. Is there s
For me weston compositor-x11 always ran really slow, as it produces a
composite after every X event. I managed to "fix" this with the attached
patch, and now multiple X events are read at a time, making wayland look
*much* faster!
However this only fixes it because it prints something into a g
14 matches
Mail list logo
