mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Cc: Dave Airlie <airlied@linux.ie>, Arjan van de Ven <arjanv@redhat.com>
Subject: Re: [RFC/patch] macro_removal_agp_mtrr.diff
Date: Sat, 4 Sep 2004 11:47:35 -0400	[thread overview]
Message-ID: <200409041147.35522.gene.heskett@verizon.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0409041418450.25475@skynet>

On Saturday 04 September 2004 09:23, Dave Airlie wrote:
>Okay here is an updated patch:
>
>I've taken suggestions from Christoph and Arjan on board,
>
>My only issue is with the stuff in drm_os_linux.h, I've had to make
> a dummy AGP structure, and add the mtrr_add/mtrr_del stubs (as they
> are fine on x86 but don't exist on anything else..) but perhaps a
> small ugly in there is better than big uglies elsewhere...
>
>I might be able to drop the OS_HAS_AGP from the drivers, but that'll
> be a job that requires testing via CVS (as that is where we have
> the people with the different cards..)
>
>Dave.

Having followed this discussion a bit without really understanding it, 
I'd like to make a commment.

I was over to the x.org site this morning, looking to see if I could 
dl the latest tag to see if it would speed up my Extacy(ATI radeon) 
9200SE w/128 MB of memory any.  Tuxracer is a 2 seconds per frame 
game now, and of course unplayable.  And requires a reboot to restore 
x when you *have* managed to quit it, quite a feat in itself 
considering the mouse updates are equally slow, and apparently being 
'smoothed', meaning multiple frame lags after the mouse has been 
stopped.

Unforch, it appears not to be available as a tarball, or group of 
tarballs stuffed in a "grab all these" directory.  While I probably 
wouldn't be anything but a src of distracting questions, I still 
wouldn't mind an opportunity to build and test (and report on the 
grins and scowls) this if it can be built in a sandbox, leaving the 
existing X.org-6.7 release intact for rescue recovery.  I have the 
disk space, and plenty of cpu cycles I can steal from setiathome, so 
thats not a major problem.

Is the present, developers only access intended, or am I a dummy that 
can't see a link if it bit me?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.25% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

  parent reply	other threads:[~2004-09-04 15:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-04 10:02 Dave Airlie
2004-09-04 10:11 ` Christoph Hellwig
2004-09-04 10:14 ` Arjan van de Ven
2004-09-04 10:21   ` Dave Airlie
2004-09-04 10:30   ` Dave Airlie
2004-09-04 10:36     ` Arjan van de Ven
2004-09-04 10:37     ` Arjan van de Ven
2004-09-04 13:23       ` Dave Airlie
2004-09-04 13:30         ` Arjan van de Ven
2004-09-04 15:47         ` Gene Heskett [this message]
2004-09-04 16:33           ` Alan Cox
2004-09-04 22:04             ` Lee Revell

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=200409041147.35522.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --cc=airlied@linux.ie \
    --cc=arjanv@redhat.com \
    --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

all inboxes | Powered by JetHome®