From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Seitz Subject: Re: Video tearing on Sandybridge Date: Mon, 02 Apr 2012 13:30:22 +0200 Message-ID: <4F798DCE.1060205@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 DD08D9E710 for ; Mon, 2 Apr 2012 04:30:24 -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: Intel Graphics Development List-Id: intel-gfx@lists.freedesktop.org > Video tearing in windows is a known issue on SandyBridge And also on IvyBridge, I presume. Then I'll try to be patient until there's a new implementation of vsynced update logic in the driver :-) Thanks for the explanations and all the good work! Kiste