From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 28341] Flickering screen in Neverball on drm-radeon-testing
Date: Thu, 22 Jul 2010 13:23:08 -0700 (PDT)
Message-ID: <20100722202308.4623B13007C@annarchy.freedesktop.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id 636239EC1C
for ;
Thu, 22 Jul 2010 13:23:08 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=28341
--- Comment #18 from Mario Kleiner 2010-07-22 13:23:07 PDT ---
Jerome,
as far as i can see, your flush, invalidate patch is in the right direction,
but the dri2InvalidateDrawable() call just increments drawable->dri2.stamp and
the current radeon dri driver in current mesa isn't checking the
drawable->dri2.stamp for changes.
The intel driver has checks like...
if (drawable->lastStamp != drawable->dri2.stamp)
intel_update_renderbuffers(driContext, drawable);
... in various places. Similar checks and calls to
radeon_update_renderbuffers() would probably do the trick, because that would
call DRI2GetBuffersWithFormat() etc. which will throttle properly until a swap
is completed.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.