All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: "Antonino A. Daplas" <adaplas@pol.net>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Andrew Morton <akpm@osdl.org>, Miles Lane <miles.lane@gmail.com>
Subject: Re: Re: 2.6.12-rc1-mm2 -- nvidiafb driver gives black screen
Date: Thu, 14 Apr 2005 19:13:23 +0200	[thread overview]
Message-ID: <20050414191323.10d7d435.khali@linux-fr.org> (raw)
In-Reply-To: <200504141351.42971.adaplas@hotpop.com>

Hi Tony,

> This patch will always limit the amount of video RAM to remap at
> 128 MiB.

I don't much get the idea. What are you trying to prevent?

128 MiB seems a rather low limit. Graphics adapters with 256 MiB, 512
MiB or even 640 MiB exist, and I see little reason why it would stop
increasing.

> diff -Nru a/drivers/video/nvidia/nvidia.c b/drivers/video/nvidia/nvidia.c
> --- a/drivers/video/nvidia/nvidia.c	2005-04-14 13:33:38 +08:00
> +++ b/drivers/video/nvidia/nvidia.c	2005-04-14 13:44:15 +08:00
> @@ -1510,7 +1510,11 @@
>  	par->FbMapSize = par->RamAmountKBytes * 1024;
>  
>  	if (vram && vram * 1024 * 1024 < par->FbMapSize)
> -	    par->FbMapSize = vram * 1024 * 1024;
> +		par->FbMapSize = vram * 1024 * 1024;

You're fixing an indentation error you just introduced in the previous
patch. Maybe you could fix the first patch instead?

Thanks,
-- 
Jean Delvare


-------------------------------------------------------
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-14 17:13 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 [this message]
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
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=20050414191323.10d7d435.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=adaplas@pol.net \
    --cc=akpm@osdl.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=miles.lane@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.