dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42920] Radeon with KMS and UMA works only up to 128MB
Date: Tue, 13 Mar 2012 13:34:14 GMT	[thread overview]
Message-ID: <201203131334.q2DDYEsr016487@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42920-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=42920


Alex Deucher <alexdeucher@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexdeucher@gmail.com




--- Comment #1 from Alex Deucher <alexdeucher@gmail.com>  2012-03-13 13:34:13 ---
Looks like the bios sets up the vram size wrong for values > 128 MB.  Can you
print the value of the CONFIG_MEMSIZE register (0x5428) when you select various
vram sizes over 128 MB?  You can either use radeonreg
(http://cgit.freedesktop.org/~airlied/radeontool/):

radeonreg regmatch 0x5428

or the following patch:

diff --git a/drivers/gpu/drm/radeon/r600.c b/drivers/gpu/drm/radeon/r600.c
index 426cc65..6f02970 100644
--- a/drivers/gpu/drm/radeon/r600.c
+++ b/drivers/gpu/drm/radeon/r600.c
@@ -1204,6 +1204,7 @@ int r600_mc_init(struct radeon_device *rdev)
        /* Setup GPU memory space */
        rdev->mc.mc_vram_size = RREG32(CONFIG_MEMSIZE);
        rdev->mc.real_vram_size = RREG32(CONFIG_MEMSIZE);
+       DRM_INFO("CONFIG_MEMSIZE: 0x%08x\n", RREG32(CONFIG_MEMSIZE));
        rdev->mc.visible_vram_size = rdev->mc.aper_size;
        r600_vram_gtt_location(rdev, &rdev->mc);

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  reply	other threads:[~2012-03-13 13:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 13:11 [Bug 42920] New: Radeon with KMS and UMA works only up to 128MB bugzilla-daemon
2012-03-13 13:34 ` bugzilla-daemon [this message]
2012-03-13 13:55 ` [Bug 42920] " bugzilla-daemon
2012-03-13 14:13 ` bugzilla-daemon
2012-03-14 14:46 ` bugzilla-daemon
2012-03-14 15:02 ` bugzilla-daemon
2012-03-14 15:49 ` bugzilla-daemon
2012-03-15 14:26 ` bugzilla-daemon
2012-04-02 13:58 ` bugzilla-daemon
2012-04-02 14:13 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201203131334.q2DDYEsr016487@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).