On Wed, Nov 04, 2015 at 12:58:18PM -0800, Bryce Harrington wrote:
> On Wed, Nov 04, 2015 at 02:47:33PM -0600, Derek Foreman wrote:
> > commit e76f185 stopped using visuals with "native visual id" == 0
> >
> > This broke some systems, so we now try 0 as a worst case fallback if
> > everything else
On Wed, Nov 04, 2015 at 10:16:27PM +0100, Manuel Bachmann wrote:
> Hi Derek, and thanks for your answer,
>
> You are right, maybe we could search a config with matching visual_id, and
> if one does not exist, then fallback to a "0" config.
>
> I can rework the patch to do this ; but if you alread
Hey,
I just got around to trying Wayland on my ThinkPad X1 Carbon 2015.
The machine has a 2560x1440px display with 220 DPI, hence I’m using it as a
“retina display”, i.e. with a scale factor of 2. On Xorg, I achieve this by
setting “Xft.dpi: 192” in my ~/.Xresources. All the applications then com
17.09.2015, 21:56, Bryce Harrington kirjoitti:
On Thu, Sep 17, 2015 at 03:05:25PM +0300, Tomi Leppänen wrote:
There were two files (doc/svg/{edge,twofinger}-scrolling.svg) that had both
arrow heads pointing to wrong direction. Those arrow heads used markers but
their ids were defined wrong and t
With respect to
http://lists.freedesktop.org/archives/wayland-devel/2014-September/017259.html
and https://bugzilla.gnome.org/show_bug.cgi?id=698226:
I own a ThinkPad Twist, which has a tablet mode. When in tablet mode,
the back of the screen touches the trackpoint and touchpad, which makes
the mo
Hi,
On 7 November 2015 at 17:49, Jasper St. Pierre wrote:
> OK. So the bug *wasn't* fixed two years ago like you were saying, and
> under transformations, mesa is still wrong.
It was fixed two years ago for clients using plain eglSwapBuffers,
which I posit is functionally equivalent to all of th
OK. So the bug *wasn't* fixed two years ago like you were saying, and
under transformations, mesa is still wrong.
So we fix the bug by adding wl_surface.buffer_damage, since it's
impossible for Mesa to know about buffer transformations... and then
what?
The only way we can properly interpret the
Hi,
On 7 November 2015 at 16:59, Jasper St. Pierre wrote:
> I don't see where. I see eglSwapBuffersWithDamage still looking like
> it shoves the rects across the wire in buffer space, without any
> modification.
>
> http://cgit.freedesktop.org/mesa/mesa/tree/src/egl/drivers/dri2/platform_wayland.
I don't see where. I see eglSwapBuffersWithDamage still looking like
it shoves the rects across the wire in buffer space, without any
modification.
http://cgit.freedesktop.org/mesa/mesa/tree/src/egl/drivers/dri2/platform_wayland.c#n705
I checked the Mali driver implementation I have, and it does
On 6 November 2015 at 19:08, Jasper St. Pierre wrote:
> To help clear things up, I think we should deprecate the
> wl_surface.damage request and document that the coordinates are
> effectively undefined -- for legacy reasons, if you see
> wl_surface.damage, it should be considered a damage for the
10 matches
Mail list logo
