From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
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: Thu, 31 Mar 2005 15:18:26 -0800 [thread overview]
Message-ID: <424C8542.9020607@osdl.org> (raw)
In-Reply-To: <1112310608.31848.181.camel@gaston>
Benjamin Herrenschmidt wrote:
> 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 ?
It's ioremap of the frame buffer -- 128 MB being requested and it
fails if the default 128 MB kernel vmalloc area size is used.
> In radeonfb, I had to limit the amount of vram actually ioremap'd by the
> kernel because of that.
I guess that Tony will know what to do when he sees this....
--
~Randy
-------------------------------------------------------
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
prev parent reply other threads:[~2005-03-31 23:18 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
2005-03-31 23:18 ` Randy.Dunlap [this message]
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=424C8542.9020607@osdl.org \
--to=rddunlap@osdl.org \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).