linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Mercer <r.a.mercer@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Cc: marcelo@conectiva.com.br
Subject: [PATCH 2.4.21-rc1] vesafb with large memory
Date: Wed, 30 Apr 2003 09:09:10 +0100	[thread overview]
Message-ID: <20030430080910.GA5011@skymoo.dyndns.org> (raw)

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

Hi

I've recently been having a problem with the vesafb refusing to boot on
my system, after investigation the problem further I found that it had
been mentioned on the 27 March 2003, in this thread

http://marc.theaimsgroup.com/?l=linux-kernel&m=104878364823195&w=2

In the thread Walt H, waltabbyh <at> comcast <dot> net, provides a fix.
After just downloading 2.4.21-rc1 I noticed that this fix was not
present. So heres a patch against 2.4.21-rc1 to fix this probelm.

Please CC me with any responses as I'm not on the list.

Cheers

Adam

diff -urN linux-2.4.21-rc1-orig/drivers/video/vesafb.c linux-2.4.21-rc1/drivers/video/vesafb.c
--- linux-2.4.21-rc1-orig/drivers/video/vesafb.c  2002-11-28 23:53:15.000000000 +0000
+++ linux-2.4.21-rc1/drivers/video/vesafb.c 2003-04-30 08:32:02.000000000 +0100
@@ -520,7 +520,7 @@
	video_width         = screen_info.lfb_width;
	video_height        = screen_info.lfb_height;
	video_linelength    = screen_info.lfb_linelength;
-	video_size          = screen_info.lfb_size * 65536;
+	video_size          = screen_info.lfb_width *	screen_info.lfb_height * video_bpp;
	video_visual = (video_bpp == 8) ?
		FB_VISUAL_PSEUDOCOLOR : FB_VISUAL_TRUECOLOR;						

[-- Attachment #2: 2.4.21-rc1-vesafb-highmem.patch --]
[-- Type: text/plain, Size: 651 bytes --]

diff -urN linux-2.4.21-rc1-orig/drivers/video/vesafb.c linux-2.4.21-rc1/drivers/video/vesafb.c
--- linux-2.4.21-rc1-orig/drivers/video/vesafb.c	2002-11-28 23:53:15.000000000 +0000
+++ linux-2.4.21-rc1/drivers/video/vesafb.c	2003-04-30 08:32:02.000000000 +0100
@@ -520,7 +520,7 @@
 	video_width         = screen_info.lfb_width;
 	video_height        = screen_info.lfb_height;
 	video_linelength    = screen_info.lfb_linelength;
-	video_size          = screen_info.lfb_size * 65536;
+	video_size          = screen_info.lfb_width * screen_info.lfb_height * video_bpp;
 	video_visual = (video_bpp == 8) ?
 		FB_VISUAL_PSEUDOCOLOR : FB_VISUAL_TRUECOLOR;
 

             reply	other threads:[~2003-04-30  7:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30  8:09 Adam Mercer [this message]
2003-04-30 11:26 ` [PATCH 2.4.21-rc1] vesafb with large memory Alan Cox
2003-04-30 18:58 O.Sezer
2003-04-30 21:33 O.Sezer
2003-05-01 12:00 ` Thomas Backlund
2003-05-01 12:07   ` Alan Cox
2003-05-01 15:01     ` Thomas Backlund
2003-05-01 14:49       ` Alan Cox
2003-05-01 17:39         ` Thomas Backlund
2003-05-02  0:14         ` Thomas Backlund
2003-05-02 13:03           ` Willy Tarreau
2003-05-03 12:46             ` Thomas Backlund
2003-05-03 21:58               ` Willy Tarreau
2003-05-04  9:49               ` Willy TARREAU
2003-05-06  0:21                 ` Thomas Backlund
2003-05-01 14:20 O.Sezer
2003-05-01 15:03 ` Thomas Backlund
2003-05-01 15:09   ` O.Sezer
2003-05-06 15:58 Walt H

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=20030430080910.GA5011@skymoo.dyndns.org \
    --to=r.a.mercer@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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).