[PATCH 2.6.7-bk] vram boot option

[PATCH 2.6.7-bk] vram boot option

[Marc-Christian Petersen]

[-- Attachment #1: Type: text/plain, Size: 318 bytes --]

Hi Linus,

could we either change that boot opion to "vram:" to be equal to 2.4 or should 
we change 2.4 to be equal to 2.6.7-bk? I guess we should do the 1st.

I'm speaking about this one:

http://linux.bkbits.net:8080/linux-2.5/gnupatch@40ba1aa0CbdwIRz9E1pww0NREOd4nQ

And document the option, please!

ciao, Marc



[-- Attachment #2: vram-sane-with-2.4.patch --]
[-- Type: text/x-diff, Size: 950 bytes --]

--- a/Documentation/fb/vesafb.txt	2003-12-18 03:59:06.000000000 +0100
+++ b/Documentation/fb/vesafb.txt	2004-05-31 01:01:12.000000000 +0200
@@ -146,6 +146,10 @@ pmipal	Use the protected mode interface 
 
 mtrr	setup memory type range registers for the vesafb framebuffer.
 
+vram:n	remap 'n' MiB of video RAM. If 0 or not specified, remap memory 
+	according to video mode. (2.5.66 patch/idea by Antonino Daplas 
+	reversed to give override possibility (allocate more fb memory 
+	than the kernel would) to 2.4 by tmb@iki.fi)
 
 Have fun!
 
--- a/drivers/video/vesafb.c	2004-05-31 00:59:41.000000000 +0200
+++ b/drivers/video/vesafb.c	2004-05-31 01:00:29.000000000 +0200
@@ -207,7 +207,7 @@ int __init vesafb_setup(char *options)
 			mtrr=1;
 		else if (! strcmp(this_opt, "nomtrr"))
 			mtrr=0;
-		else if (! strncmp(this_opt, "vram=", 5))
+		else if (! strncmp(this_opt, "vram:", 5))
 			vram = simple_strtoul(this_opt+5, NULL, 0);
 	}
 	return 0;