From: "Michel Dänzer" <michel@daenzer.net>
To: Jochen Rollwagen <joro-2013@t-online.de>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: possible regression Radeon RV280 (R3xx/R4xx ?) card freeze, re-apply old patch ?
Date: Thu, 14 Nov 2013 10:37:42 +0900 [thread overview]
Message-ID: <1384393062.18541.25.camel@thor.local> (raw)
In-Reply-To: <5283BFE9.5060208@t-online.de>
On Mit, 2013-11-13 at 19:07 +0100, Jochen Rollwagen wrote:
> I started investigating the problem because AGP mode used to work with
> the UMS drivers (although I now understand they didn’t really use AGP
> memory)
They used AGP memory but didn't dynamically bind memory to the AGP
aperture or unbind it from there.
> and in the second patch I mentioned below Benjamin Herrenschmidt
> stated that “there's a chip errata (for the pre-R600 chips). On those
> chips, the aperture must be aligned to the aperture size (that is
> FB_START in MC_FB_LOCATION must be aligned to the aperture size).”
> Since that workaround/patch definitely isn’t in the current DRM code
> any more (probably got lost in the transition to KMS) my idea was to
> re-apply the three-line workaround/patch (which should be quite
> trivial given the comment in radeon_vram_location in the drm kernel
> code).
So, have you verified that the aperture is not aligned to its size for
you? If it's not, does aligning it help stability with AGP?
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-11-14 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <526A6C61.1030405@t-online.de>
2013-11-08 7:35 ` possible regression Radeon RV280 (R3xx/R4xx ?) card freeze, re-apply old patch ? Jochen Rollwagen
2013-11-11 20:35 ` Alex Deucher
2013-11-13 18:07 ` Jochen Rollwagen
2013-11-14 1:37 ` Michel Dänzer [this message]
2013-11-15 7:49 ` Jochen Rollwagen
2013-11-15 8:27 ` Michel Dänzer
2013-11-17 10:02 ` Jochen Rollwagen
2013-11-22 13:21 ` Jochen Rollwagen
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=1384393062.18541.25.camel@thor.local \
--to=michel@daenzer.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=joro-2013@t-online.de \
/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).