From: David Mosberger <davidm@napali.hpl.hp.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: davidm@hpl.hp.com, davej@suse.de, linux-kernel@vger.kernel.org,
dri-devel@lists.sourceforge.net
Subject: Re: Improved DRM support for cant_use_aperture platforms
Date: Sun, 11 May 2003 11:09:00 -0700 [thread overview]
Message-ID: <16062.37308.611438.5934@napali.hpl.hp.com> (raw)
In-Reply-To: <1052653415.12338.159.camel@thor>
>>>>> On 11 May 2003 13:43:36 +0200, Michel Dänzer <michel@daenzer.net> said:
Michel> On Sam, 2003-05-10 at 12:09, David Mosberger wrote:
>> This patch is rather big, but actually very straight-forward: it
>> adds a "agp dev" argument to DRM_IOREMAP(),
>> DRM_IOREMAP_NOCACHE(), and DRM_IOREMAPFREE() and then uses it in
>> drm_memory.h to support platforms where CPU accesses to the AGP
>> space are not translated by the GART (true for ia64 and alpha,
>> not true for x86, I don't know about the other platforms). On
>> platforms where cant_use_aperture is always false, this whole
>> patch will look like a no-op. On ia64, it works. Don't know
>> about other platforms, but it should simplify things for Alpha at
>> least (and if it breaks a platform, I shall be happy to work with
>> the respective maintainer to get fix back to working).
Michel> I'd love to commit this to DRI CVS,
Great!
Michel> but there'd have to be fallbacks for older kernels (this is
Michel> against 2.4.20-ben8):
OK, we have a chicken & egg problem then: I could obviously add Linux
kernel version checks where needed, but to do that, the patch first
needs to go into the kernel. Dave, would you mind applying the patch
to your tree? Then once Linus picked it up, I can send a new patch to
dri-devel. Or does someone have a better suggestion?
--david
next prev parent reply other threads:[~2003-05-11 17:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 10:09 David Mosberger
2003-05-10 13:12 ` Dave Jones
2003-05-11 11:43 ` Michel Dänzer
2003-05-11 18:09 ` David Mosberger [this message]
2003-05-11 19:55 ` Dave Jones
2003-05-11 21:55 ` Michel Dänzer
2003-05-12 18:53 ` David Mosberger
2003-05-12 19:48 ` [Dri-devel] " Michel Dänzer
2003-05-12 20:19 ` David Mosberger
2003-05-12 21:21 ` Michel Dänzer
2003-05-12 21:51 ` David Mosberger
2003-05-12 21:57 ` Christoph Hellwig
2003-05-12 22:08 ` Andrew Morton
2003-05-12 22:20 ` Christoph Hellwig
2003-05-13 0:34 ` Michel Dänzer
2003-05-13 1:09 ` David Mosberger
2003-05-13 13:33 ` Ivan Kokshaysky
2003-05-13 16:20 ` David Mosberger
2003-05-14 9:41 ` Ivan Kokshaysky
2003-05-14 10:27 ` Michel Dänzer
2003-05-14 17:09 ` David Mosberger
2003-05-13 7:43 ` David Mosberger
2003-05-14 14:08 ` Michel Dänzer
2003-05-15 15:59 ` David Mosberger
2003-05-15 22:37 ` Michel Dänzer
2003-05-16 23:50 ` [Dri-devel] " Michel Dänzer
2003-05-12 20:40 ` David Mosberger
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=16062.37308.611438.5934@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davej@suse.de \
--cc=davidm@hpl.hp.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
/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
all inboxes | Powered by JetHome®