From: "Chris Rankin" <rankincj@yahoo.com>
To: root@chaos.analogic.com
Cc: VANDROVE@vc.cvut.cz, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Screen corruption in 2.4.18
Date: Tue, 2 Apr 2002 23:40:53 +0100 (BST) [thread overview]
Message-ID: <20020402224053.14575.qmail@web13107.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020402172447.7371A-100000@chaos.analogic.com>
--- "Richard B. Johnson" <root@chaos.analogic.com>
wrote: > On Tue, 2 Apr 2002, Chris Rankin wrote:
> [SNIPPED...]
>
> >
> > A few other things:
> > - since I have about 1.25 GB of RAM, I have
> enabled a 256 MB AGP aperture.
>
> What? 'since amount of RAM' has nothing to do with
> AGP aperature. The
> aperature should be the same as the amount of AGP
> shared RAM used for
> the screen-card on-board graphics. This is normally
> set by the BIOS but
> can be reset if the BIOS doesn't 'understand' your
> screen card.
>
> So, unless you have 256 MB on your screen board,
> typically 32 MB for
> high-resolution true-color boards, you will be
> disabling PCI hardware
> hand-shaking for a lot of addresses above your
> screen board. This
> can make DRAM-controler, controlled RAM accesses
> interfere.
I set the AGP aperture based upon the following
information:
"The AGP aperture is an area of system RAM reserved
for use by the AGP card for storing textures if it
needs to. The RAM is available for use by the system
as normal if not used by the graphics card."
...
"It is generally advised to set the AGP aperture to
half the system RAM ."
Therefore, it seemed reasonable to maximise my AGP
aperture size for all and any conceivable textures (I
have system RAM to spare), with no harm done.
Admittedly, 256 MB does seem excessive, but anyway ...
;-).
Chris
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
next prev parent reply other threads:[~2002-04-02 22:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 21:43 Chris Rankin
2002-04-02 22:33 ` Richard B. Johnson
2002-04-02 22:40 ` Chris Rankin [this message]
2002-04-03 14:00 ` Richard B. Johnson
2002-04-03 20:34 ` Chris Rankin
2002-04-02 23:38 ` Erik Ljungström
-- strict thread matches above, loose matches on Subject: below --
2002-04-02 22:50 Petr Vandrovec
2002-04-02 22:09 ` Chris Rankin
2002-03-29 12:26 Petr Vandrovec
2002-03-28 22:46 Bill Hammock
2002-03-29 0:14 ` Danijel Schiavuzzi
2002-03-29 2:05 ` Andre Pang
2002-03-25 17:59 Petr Vandrovec
2002-03-19 21:12 Danijel Schiavuzzi
2002-03-20 0:03 ` Steven Walter
[not found] ` <200203201506.QAA13795@jagor.srce.hr>
[not found] ` <20020320172516.GA14024@hapablap.dyn.dhs.org>
[not found] ` <200203211209.NAA11121@jagor.srce.hr>
2002-03-21 17:22 ` Steven Walter
[not found] ` <200203222204.XAA01121@jagor.srce.hr>
2002-03-22 23:23 ` Steven Walter
[not found] ` <200203231526.QAA09302@jagor.srce.hr>
2002-03-23 16:06 ` Steven Walter
2002-03-24 7:05 ` Andre Pang
2002-03-24 15:07 ` Danijel Schiavuzzi
2002-03-24 16:51 ` Alan Cox
2002-03-24 17:13 ` Danijel Schiavuzzi
2002-03-25 1:43 ` Andre Pang
2002-03-25 2:40 ` Steven Walter
2002-03-25 3:00 ` Andre Pang
2002-03-25 8:50 ` Marc Wilson
2002-03-25 17:07 ` Daniel Gryniewicz
2002-03-25 21:02 ` Steven Walter
2002-03-25 21:19 ` Marc Wilson
2002-03-29 2:06 ` Andre Pang
2002-03-29 3:16 ` Marc Wilson
2002-03-25 1:55 ` Andre Pang
2002-03-25 19:52 ` Danijel Schiavuzzi
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=20020402224053.14575.qmail@web13107.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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®