On Friday 15 December 2017, Tapani Pälli wrote:
>
> On 15.12.2017 16:40, Thomas Hellstrom wrote:
> > On 12/15/2017 02:50 PM, Tapani Pälli wrote:
> >> Hi;
> >>
> >> On 15.12.2017 10:10, Thomas Hellstrom wrote:
> >>> On 12/11/2017 06:53 AM, Tapani Pälli wrote:
> Hi;
>
> Any comments?
On Thursday 05 October 2017, Thomas Hellstrom wrote:
> On 10/03/2017 12:44 PM, Thomas Hellstrom wrote:
> > Hi!
> >
> > On 10/02/2017 11:51 PM, Fredrik Höglund wrote:
> >> On Monday 02 October 2017, Thomas Hellstrom wrote:
> >>> Hi, Fredrik,
> >>&g
On Tuesday 03 October 2017, Thomas Hellstrom wrote:
> Hi!
>
> On 10/02/2017 11:51 PM, Fredrik Höglund wrote:
> > On Monday 02 October 2017, Thomas Hellstrom wrote:
> >> Hi, Fredrik,
> >>
> >> On 10/02/2017 07:10 PM, Fredrik Höglund wrote:
> >>>
On Monday 02 October 2017, Thomas Hellstrom wrote:
> Hi, Fredrik,
>
> On 10/02/2017 07:10 PM, Fredrik Höglund wrote:
> > On Tuesday 26 September 2017, Thomas Hellstrom wrote:
> >> Hi, Fredrik,
> >>
> >> On 09/26/2017 11:53 AM, Fredrik Höglund wrote:
&g
Tested-by: Fredrik Höglund <fred...@kde.org>
On Wednesday 27 September 2017, Thomas Hellstrom wrote:
> Previously, before GLX_OML_swap_method was fixed, both the X server and
> client ignored the swapMethod fbconfig value, which meant that, if the dri
> driver thought it expose
On Tuesday 26 September 2017, Thomas Hellstrom wrote:
> Hi, Fredrik,
>
> On 09/26/2017 11:53 AM, Fredrik Höglund wrote:
> > On Wednesday 06 September 2017, Thomas Hellstrom wrote:
> >> For the built in visuals, we'd typically select the "best" fbconfig
> &
On Wednesday 06 September 2017, Thomas Hellstrom wrote:
> For the built in visuals, we'd typically select the "best" fbconfig
> without considering the swap method. If the client then requests a
> specific swap method, say GLX_SWAP_COPY_OML, it may well happen that the
> first fbconfig matching
On Monday 02 January 2017, Adam Jackson wrote:
> (accidentally sent only to Alex, resending so the list gets it too)
>
> On Thu, 2016-12-22 at 19:43 -0800, Alex Goins wrote:
>
> > > One option would be to expose the drawables with existing visuals
> > > through the core protocol, then provide an
On Friday 11 September 2015, Michel Dänzer wrote:
> On 11.09.2015 06:33, Fredrik Höglund wrote:
> > Otherwise we stash an uninitalized value, and later use it to compute
> > the msc_offset for the window. Also initialize ust and crtc_msc so we
> > never use uni
off.
Signed-off-by: Fredrik Höglund <fred...@kde.org>
---
present/present.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/present/present.c b/present/present.c
index a634601..7ddffbd 100644
--- a/present/present.c
+++ b/present/present.c
@@ -710,9
On Monday 19 January 2015, Chris Wilson wrote:
Allow the DDXes to opt-in and handle swap-interval=0 requests for
themselves, for example by using asynchronous pageflips, rather than
forcing a blit. This has the important side-effect of also
disambiguating CopyRegion calls to always be client
On Tuesday 16 December 2014, Jason Ekstrand wrote:
Yeah... Still not working for me. Not sure why mutter is different than
KWin, but I still get black after the screen lock and, when I restart
gnome-shell it's tearing like crazy.
--Jason
KWin doesn't use GLX_INTEL_swap_event (although that's
On Wednesday 20 November 2013, Keith Packard wrote:
Fredrik Höglund fred...@kde.org writes:
I also decided to try passing a regular sync fence to DRI3FDFromFence.
I expected it to generate an error, but it didn't. Instead it returned
a valid file descriptor. I don't know if this is a bug
On Wednesday 20 November 2013, Keith Packard wrote:
Keith Packard kei...@keithp.com writes:
This makes the xshmfence stuff only used if the driver specifies it,
allowing drivers to specify other FD-passing based fences, and also
avoiding errors if a driver doesn't initialize any
14 matches
Mail list logo
