linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: davidm@hpl.hp.com
Cc: "Wiedemeier, Jeff" <Jeff.Wiedemeier@hp.com>,
	"Michel Dänzer" <michel@daenzer.net>,
	"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: Tue, 13 May 2003 17:33:47 +0400	[thread overview]
Message-ID: <20030513173347.A25865@jurassic.park.msu.ru> (raw)
In-Reply-To: <16064.17852.647605.663544@napali.hpl.hp.com>; from davidm@napali.hpl.hp.com on Mon, May 12, 2003 at 06:09:16PM -0700

On Mon, May 12, 2003 at 06:09:16PM -0700, David Mosberger wrote:
> OK, I believe the only other architecture that sets
> "cant_use_aperture" is Alpha.

Note that some Alphas may have "cant_use_aperture" cleared.
I mean Nautilus - unfortunate product of Athlon northbridge
and EV6 interbreeding... I've just managed to get agpgart working
to some degree on one of these beasts (UP1500), but with so many
ugly and fragile hacks that I'm not sure that I ever want
to submit this. ;-)

>  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.

Yes.

> 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.

That would be great. 
[Cc'd to Jeff, who wrote Alpha AGP code]

Ivan.

  reply	other threads:[~2003-05-13 13:23 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
2003-05-13 13:33                       ` Ivan Kokshaysky [this message]
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=20030513173347.A25865@jurassic.park.msu.ru \
    --to=ink@jurassic.park.msu.ru \
    --cc=Jeff.Wiedemeier@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).