Attachment 39651 Details for Bug 28402 – Make sure MC vram map is >= pci aperture size

[patch] Make sure MC vram map is >= pci aperture size

0001-drm-radeon-kms-MC-vram-map-needs-to-be-pci-aperture-.patch (text/plain), 1.25 KB, created by Alex Deucher on 2010-10-23 06:56:27 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Alex Deucher

Created: 2010-10-23 06:56:27 UTC

Size: 1.25 KB

patch

obsolete

>From debc5199f16c48d08e76b5a0ff97d57486a7ced0 Mon Sep 17 00:00:00 2001
>From: Alex Deucher <alexdeucher@gmail.com>
>Date: Sat, 23 Oct 2010 09:51:36 -0400
>Subject: [PATCH] drm/radeon/kms: MC vram map needs to be >= pci aperture size
>
>The vram map in the radeon memory controller needs to be
>>= the pci aperture size.  Fixes:
>https://bugs.freedesktop.org/show_bug.cgi?id=28402
>
>The problematic cards in the above bug have 64 MB of vram,
>but the pci aperture is 128 MB and the MC vram map was only
>64 MB.  This can lead to hangs.
>
>Signed-off-by: Alex Deucher <alexdeucher@gmail.com>
>Cc: stable@kernel.org
>---
> drivers/gpu/drm/radeon/r100.c |    3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
>diff --git a/drivers/gpu/drm/radeon/r100.c b/drivers/gpu/drm/radeon/r100.c
>index da69db9..f2155bc 100644
>--- a/drivers/gpu/drm/radeon/r100.c
>+++ b/drivers/gpu/drm/radeon/r100.c
>@@ -2326,6 +2326,9 @@ void r100_vram_init_sizes(struct radeon_device *rdev)
> 		/* Fix for RN50, M6, M7 with 8/16/32(??) MBs of VRAM - 
> 		 * Novell bug 204882 + along with lots of ubuntu ones
> 		 */
>+		if (rdev->mc.aper_size > config_aper_size)
>+			config_aper_size = rdev->mc.aper_size;
>+
> 		if (config_aper_size > rdev->mc.real_vram_size)
> 			rdev->mc.mc_vram_size = config_aper_size;
> 		else
>-- 
>1.7.1.1
>

Actions: View | Splinter Review

Attachments on bug 28402: 36221 | 38307 | 38308 | 38309 | 38310 | 38311 | 38312 | 38313 | 38314 | 38458 | 38459 | 38468 | 38469 | 38516 | 38564 | 38576 | 38577 | 39455 | 39595 | 39651

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.