From: David Mosberger <davidm@napali.hpl.hp.com>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: davidm@hpl.hp.com, Dave Jones <davej@codemonkey.org.uk>,
linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: Improved DRM support for cant_use_aperture platforms
Date: Mon, 12 May 2003 18:09:16 -0700 [thread overview]
Message-ID: <16064.17852.647605.663544@napali.hpl.hp.com> (raw)
In-Reply-To: <1052786080.10763.310.camel@thor>
Michel> There are a couple more, like pte_offset_kernel(),
Michel> pte_pfn(), pfn_to_page() and
Michel> flush_tlb_kernel_range(). Getting this working with 2.4
Michel> seems like a lot of work and/or ugly. :\
Just goes to show how quickly one gets used to 2.5... ;-)
Let me take a look at these.
>> (apart from PAGE_AGP, which is taken care of by the latest
>> patch).
Michel> Not quite, PAGE_KERNEL_NOCACHE isn't defined on all
Michel> architectures either.
OK, I believe the only other architecture that sets
"cant_use_aperture" is Alpha. I asked some Alpha folks several months
ago about my patch, but never got a conclusive answer. IIRC, on Alpha
the physical address itself determines cacheablity. If so, we can use
PAGE_KERNEL (which is universal) instead of PAGE_KERNEL_NOCACHE.
Clearly the patch needs to be tested on Alpha. The upside is that it
should let the Alpha folks get rid of a lot of ugliness in the
ioremap() code.
--david
next prev parent reply other threads:[~2003-05-13 0:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 10:09 Improved DRM support for cant_use_aperture platforms David Mosberger
2003-05-10 13:12 ` Dave Jones
2003-05-11 11:43 ` Michel Dänzer
2003-05-11 18:09 ` David Mosberger
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 [this message]
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=16064.17852.647605.663544@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davej@codemonkey.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).