linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yves Jäger" <yves.jaeger@fraenz-jaeger.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: own driver crashes + patch
Date: 08 Aug 2002 15:01:11 +0200	[thread overview]
Message-ID: <1028811676.1323.26.camel@dilbert> (raw)

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

Hi all, 

I'm writing a Framebuffer driver for an embedded system that contains an
LCD display and and Toshiba T6963 controller. 

I had the problem, that my driver crashed because the screensize
(126x64) is lower than the boot-logo (80x80). And this parameter is not
checked in fbcon.c

To see a Kernel with the virtual framebuffer crash, apply the patch
vfb.diff and enable the Virtual Framebuffer in your configuration and
kernel command line.

The workaround is shown in file fbcon-2.4.18.patch. 
I'm not sure if that is the right place to check the boot-logo size.
Perhaps somebody has a better idea.

Best regards 
Yves Jaeger 


[-- Attachment #2: Type: text/plain, Size: 384 bytes --]

--- vfb.c	Wed Aug  7 15:14:05 2002
+++ vfb.c.new	Wed Aug  7 15:34:58 2002
@@ -62,7 +62,7 @@
 
 static struct fb_var_screeninfo vfb_default = {
     /* 640x480, 8 bpp */
-    640, 480, 640, 480, 0, 0, 8, 0,
+    128, 64, 128, 64, 0, 0, 1, 0,
     {0, 8, 0}, {0, 8, 0}, {0, 8, 0}, {0, 0, 0},
     0, 0, -1, -1, 0, 20000, 64, 64, 32, 32, 64, 2,
     0, FB_VMODE_NONINTERLACED

[-- Attachment #3: fbcon-2.4.18.patch --]
[-- Type: text/x-patch, Size: 600 bytes --]

diff -ru linux/drivers/video/fbcon.c linux-2.4.18-t6963/drivers/video/fbcon.c
--- linux/drivers/video/fbcon.c	Mon Feb 25 20:38:07 2002
+++ linux-2.4.18-t6963/drivers/video/fbcon.c	Thu Aug  8 14:43:39 2002
@@ -754,8 +754,14 @@
     }
 	
     if (logo) {
-	logo_shown = -2;
-    	conp->vc_top = logo_lines;
+	if (logo_lines > conp->vc_bottom)
+	{
+		logo_shown = -1;
+		printk(KERN_INFO "fbcon_startup: disable boot-logo (boot-logo bigger than screen).\n");
+	} else {
+		logo_shown = -2;
+		conp->vc_top = logo_lines;
+	}
     }
     
     if (con == fg_console && softback_buf) {

                 reply	other threads:[~2002-08-08 13:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1028811676.1323.26.camel@dilbert \
    --to=yves.jaeger@fraenz-jaeger.de \
    --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).