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, davej@codemonkey.org.uk
Subject: Re: [PATCH 2/2] uninorth: Add module param 'aperture' for aperture size
Date: Wed, 23 Aug 2006 08:17:13 +1000	[thread overview]
Message-ID: <1156285033.21752.107.camel@localhost.localdomain> (raw)
In-Reply-To: <1156236954.16513.141.camel@thor.lorrainebruecke.local>

> > It's basically expected that we set it ourselves and a module option 
> > doesn't seem like a terribly good idea to me...
> 
> Well, wasn't it you who suggested this? :)

Possibly, I don't always have good ideas :) I would rather have that
size be configured by the client driver... oh well, let's workaround
that for now by using a better default _and_ the module option.

> > Maybe we should just have the driver default to something more sensible
> > in addition to what AGPSize comes from userland ? like 64M ?
> 
> Might be a good idea.
> 
> 

  reply	other threads:[~2006-08-22 22:17 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
2006-08-22  8:55       ` Michel Dänzer
2006-08-22 22:17         ` Benjamin Herrenschmidt [this message]
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=1156285033.21752.107.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=davej@codemonkey.org.uk \
    --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).