linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Miles Lane <miles.lane@gmail.com>, "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-fbdev-devel@lists.sourceforge.net, adaplas@pol.net,
	khali@linux-fr.org, akpm@osdl.org
Subject: Re: Re: 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen
Date: Mon, 25 Apr 2005 11:21:24 +0800	[thread overview]
Message-ID: <200504251121.24725.adaplas@hotpop.com> (raw)
In-Reply-To: <a44ae5cd05042410092055e3c4@mail.gmail.com>

On Monday 25 April 2005 01:09, Miles Lane wrote:
> On 4/22/05, Miles Lane <miles.lane@gmail.com> wrote:
> > Okay, it also fails with Antonio's patches applied in addition to yours.
>
> I know I implied this in my previous message, but I want to make it
> explicit. This combination of patches also fails to give a working
> framebuffer console when I specify vmalloc=128M.  I only get a working
> framebuffer console by specifying vmalloc=256M.
>
>            Miles

Can you try this patch?  This limits the amount of RAM that nvidiafb
will remap to 64 MiB.  This is on top of another patch I sent to Andrew:
"[Linux-fbdev-devel] [PATCH 1/6] nvidiafb: ioremap and i2c fixes"

Tony

diff -Nru a/drivers/video/nvidia/nvidia.c b/drivers/video/nvidia/nvidia.c
--- a/drivers/video/nvidia/nvidia.c	2005-04-16 11:54:44 +08:00
+++ b/drivers/video/nvidia/nvidia.c	2005-04-25 10:39:45 +08:00
@@ -1511,9 +1511,9 @@
 	if (vram && vram * 1024 * 1024 < par->FbMapSize)
 		par->FbMapSize = vram * 1024 * 1024;
 
-	/* Limit amount of vram to 128 MB */
-	if (par->FbMapSize > 128 * 1024 * 1024)
-		par->FbMapSize = 128 * 1024 * 1024;
+	/* Limit amount of vram to 64 MB */
+	if (par->FbMapSize > 64 * 1024 * 1024)
+		par->FbMapSize = 64 * 1024 * 1024;
 
 	par->FbUsableSize = par->FbMapSize - (128 * 1024);
 	par->ScratchBufferSize = (par->Architecture < NV_ARCH_10) ? 8 * 1024 :




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-04-25  3:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a44ae5cd0503242023233dc23f@mail.gmail.com>
2005-03-25  4:31 ` 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen Andrew Morton
2005-03-26  4:50   ` Miles Lane
2005-03-28 17:12     ` Randy.Dunlap
2005-03-29  0:22       ` Miles Lane
2005-03-29  0:37         ` Randy.Dunlap
2005-03-29  0:56       ` Miles Lane
2005-03-29  1:02         ` Randy.Dunlap
2005-03-29  1:12           ` Miles Lane
2005-03-29  3:01             ` Randy.Dunlap
2005-03-29  9:16             ` Jean Delvare
2005-03-29  1:13           ` Andrew Morton
2005-03-29  3:56             ` Miles Lane
2005-03-29  4:34     ` Randy.Dunlap
2005-03-29 16:25       ` [PATCH] nvidiafb: fix section references Randy.Dunlap
2005-04-14  5:51   ` Re: 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen Antonino A. Daplas
2005-04-14 17:06     ` Jean Delvare
2005-04-15  3:07       ` Antonino A. Daplas
2005-04-14  5:51   ` Antonino A. Daplas
2005-04-14 17:13     ` Jean Delvare
2005-04-14 18:19       ` Miles Lane
2005-04-15  3:07         ` Antonino A. Daplas
2005-04-15  3:07       ` Antonino A. Daplas
2005-04-16  8:21         ` Miles Lane
2005-04-21  5:51           ` Miles Lane
2005-04-21 16:22             ` Randy.Dunlap
2005-04-21 18:36               ` Randy.Dunlap
2005-04-23  0:03                 ` Miles Lane
2005-04-23  0:12                   ` Miles Lane
2005-04-24 17:09                     ` Miles Lane
2005-04-25  3:21                       ` Antonino A. Daplas [this message]
2005-04-25 20:31                         ` Miles Lane
2005-04-25 20:33                         ` Miles Lane

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=200504251121.24725.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=khali@linux-fr.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=miles.lane@gmail.com \
    --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).