From: David Miller <davem@davemloft.net>
To: airlied@gmail.com
Cc: benh@kernel.crashing.org, airlied@linux.ie,
dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5]: drm: ati_pcigart: Do not access I/O MEM space using pointer derefs.
Date: Sat, 14 Feb 2009 00:58:03 -0800 (PST) [thread overview]
Message-ID: <20090214.005803.234317382.davem@davemloft.net> (raw)
In-Reply-To: <21d7e9970902132342k1a756475t91ede4baf571c563@mail.gmail.com>
From: Dave Airlie <airlied@gmail.com>
Date: Sat, 14 Feb 2009 17:42:02 +1000
> On Sat, Feb 14, 2009 at 4:09 PM, David Miller <davem@davemloft.net> wrote:
> > 1) Mis-sizes the GART table save buffer, it uses PAGE_SIZE instead
> > of the constant 4096 to determine how many GART entries there
> > are. The PCI GART entries map 4096 bytes, always. So using
> > getpagesize() is wrong. (see RADEONDRIGetPciAperTableSize)
> >
> > I have this fixed in my local tree.
>
> Oops.
>
> > 2) It doesn't check the surface byte swapping settings, so it
> > could be saving in one byte order and restoing in another.
> >
> > I guess we could force RADEON_SURFACE_CNTL to zero around
> > the two memcpy()'s done in radeon_driver.c
>
> Might be a good plan.
I have patches for both of these things written, will submit
to the xorg-driver-ati list.
I also have a cunning plan to work around the surface swapping
GART issue in the DRM, will try that out right now.
next prev parent reply other threads:[~2009-02-14 8:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 10:15 [PATCH 1/5]: drm: ati_pcigart: Do not access I/O MEM space using pointer derefs David Miller
2009-02-12 10:35 ` Benjamin Herrenschmidt
2009-02-12 11:09 ` David Miller
2009-02-12 11:23 ` Dave Airlie
2009-02-12 22:17 ` David Miller
2009-02-12 21:26 ` Benjamin Herrenschmidt
2009-02-12 21:29 ` Benjamin Herrenschmidt
2009-02-14 6:09 ` David Miller
2009-02-14 7:42 ` Dave Airlie
2009-02-14 8:58 ` David Miller [this message]
2009-02-14 9:09 ` Benjamin Herrenschmidt
2009-02-14 9:07 ` Benjamin Herrenschmidt
2009-02-14 9:11 ` David Miller
2009-02-14 9:51 ` David Miller
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=20090214.005803.234317382.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=benh@kernel.crashing.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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