linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Michel Dänzer" <michel@tungstengraphics.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] uninorth: Add module param 'aperture' for aperture size
Date: Tue, 22 Aug 2006 17:25:36 +1000	[thread overview]
Message-ID: <1156231536.21752.100.camel@localhost.localdomain> (raw)
In-Reply-To: <1156176559.16513.78.camel@thor.lorrainebruecke.local>

On Mon, 2006-08-21 at 18:09 +0200, Michel Dänzer wrote:

> In contrast to most if not all PC BIOSes, OpenFirmware (OF) on PowerMacs with
> UniNorth bridges does not allow changing the aperture size. The size set up by
> OF is usually 16 MB, which is too low for graphics intensive environments.
> Hence, add a module parameter that allows changing the aperture size at driver
> initialization time. When the parameter is not specified, the default is still
> to leave the size unchanged, usually as set up by OF.

The right fix is to allow changing it by the driver ... can't we do it
such that AGPSize will work & change it ? The firmware doesn't actually
configure it at all I suspect... those 16M are basically 
what the HW comes up with as a default setting (unless the firmware runs
some diagnostics and sets it as a result of these). It's basically
expected that we set it ourselves and a module option doesn't seem like
a terribly good idea to me...

Maybe we should just have the driver default to something more sensible
in addition to what AGPSize comes from userland ? like 64M ?

Ben.

  reply	other threads:[~2006-08-22  7:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <115608447678-git-send-email->
2006-08-21 16:09 ` [PATCH 1/2] uninorth: Use same sizes array everywhere Michel Dänzer
     [not found] ` <11560844762890-git-send-email->
2006-08-21 16:09   ` [PATCH 2/2] uninorth: Add module param 'aperture' for aperture size Michel Dänzer
2006-08-22  7:25     ` Benjamin Herrenschmidt [this message]
2006-08-22  8:55       ` Michel Dänzer
2006-08-22 22:17         ` Benjamin Herrenschmidt
2006-08-23  9:14           ` Michel Dänzer
2006-08-23 11:15           ` [PATCH] " Michel Dänzer
2006-10-04 10:44           ` Michel Dänzer
2006-10-04 12:24             ` Andreas Schwab

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=1156231536.21752.100.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michel@tungstengraphics.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;
as well as URLs for NNTP newsgroup(s).