linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, Andrew Morton <akpm@osdl.org>,
	"Antonino A. Daplas" <adaplas@pol.net>
Subject: Re: The nvidiafb driver is requiring too much vmalloc space and other problems.
Date: Fri, 01 Apr 2005 09:10:08 +1000	[thread overview]
Message-ID: <1112310608.31848.181.camel@gaston> (raw)
In-Reply-To: <a44ae5cd05033014597bb3a2e@mail.gmail.com>

On Wed, 2005-03-30 at 14:59 -0800, Miles Lane wrote:
> Hello,
> 
> With guidance from Randy Dunlap, it has been determined that
> the nvidiafb driver will fail to operate correctly unless more than
> 128M of memory is provided by using "vmalloc=".  The default 
> kernel configuration provides for 128M, but Randy found that:

 .../...

it's a problem with ioremap of the framebuffer ? (which uses get_vm_area
as well) or is there an actual vmalloc in there ?

In radeonfb, I had to limit the amount of vram actually ioremap'd by the
kernel because of that.

Ben.




-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/hamr30

  reply	other threads:[~2005-03-31 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 22:59 The nvidiafb driver is requiring too much vmalloc space and other problems Miles Lane
2005-03-31 23:10 ` Benjamin Herrenschmidt [this message]
2005-03-31 23:18   ` Randy.Dunlap

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=1112310608.31848.181.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=rddunlap@osdl.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;
as well as URLs for NNTP newsgroup(s).