From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 43655] Latest radeon dri driver on HD6950 with GRUB set "GRUB_GFXPAYLOAD_LINUX=keep" put the display in a flickering state Date: Sat, 30 Mar 2013 00:38:44 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1983686424==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 639BFE5C11 for ; Fri, 29 Mar 2013 17:38:44 -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 --===============1983686424== Content-Type: multipart/alternative; boundary="1364603924.Ac7F0.11491"; charset="us-ascii" --1364603924.Ac7F0.11491 Date: Sat, 30 Mar 2013 00:38:44 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=43655 --- Comment #22 from Alex Deucher --- The current code should do the right thing with respect to disabling display access to vram when we reconfigure the memory controller. The current code disables memory reads but leaves the display controllers enabled while we change the MC setup. Turning off the crtcs as the patch you mentioned does has two problems: 1. it breaks some systems which the current method fixes 2. it defeats the purpose of GRUB_GFXPAYLOAD_LINUX=keep which is to avoid turning off the displays for flickerless boot up. If you turn off the crtcs you have to re-init the entire display pipeline. The problem seems to be that disabling the crtc memory reads seems to take longer than expected on some systems which leads to invalid reads while the MC is being reprogrammed. One possible solution may be to leave the MC as configured by the vbios and try and put the gart aperture either before or after the location of varm in the GPU's address space. -- You are receiving this mail because: You are the assignee for the bug. --1364603924.Ac7F0.11491 Date: Sat, 30 Mar 2013 00:38:44 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 22 on bug 43655 from 
The current code should do the right thing with respect to disabling display
access to vram when we reconfigure the memory controller.  The current code
disables memory reads but leaves the display controllers enabled while we
change the MC setup.  Turning off the crtcs as the patch you mentioned does has
two problems:
1. it breaks some systems which the current method fixes
2. it defeats the purpose of GRUB_GFXPAYLOAD_LINUX=keep which is to avoid
turning off the displays for flickerless boot up.  If you turn off the crtcs
you have to re-init the entire display pipeline.
The problem seems to be that disabling the crtc memory reads seems to take
longer than expected on some systems which leads to invalid reads while the MC
is being reprogrammed.  One possible solution may be to leave the MC as
configured by the vbios and try and put the gart aperture either before or
after the location of varm in the GPU's address space.

You are receiving this mail because:
  • You are the assignee for the bug.
--1364603924.Ac7F0.11491-- --===============1983686424== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1983686424==--