From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Seitz Subject: Re: Video tearing on Sandybridge Date: Mon, 02 Apr 2012 12:40:47 +0200 Message-ID: <4F79822F.50009@vtnd.de> References: <4F774449.5080906@vtnd.de> <1333361053_198990@CP5-2952> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from srv6.berlinhosting.de (srv6.berlinhosting.de [87.118.86.113]) by gabe.freedesktop.org (Postfix) with ESMTP id 006A29F75D for ; Mon, 2 Apr 2012 03:40:50 -0700 (PDT) In-Reply-To: <1333361053_198990@CP5-2952> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Chris Wilson Cc: Intel Graphics Development List-Id: intel-gfx@lists.freedesktop.org > The only workaround is [...] to only use fullscreen DRI video applications > (OpenGL or libva decoders) that use SwapBuffers. Yes, works perfectly while only one screen is connected. That means, this definition of "fullscreen" is "the whole framebuffer", and not "the content of one display"? This would in some way explain why tearing can not be reliably prevented while more than one screen is active. Thanks for the explanations! Greets, Kiste