linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] [BK fbdev updates]
Date: 02 Nov 2002 03:41:33 +0800	[thread overview]
Message-ID: <1036178902.572.33.camel@daplas> (raw)
In-Reply-To: <Pine.LNX.4.33.0210311258040.1721-100000@maxwell.earthlink.net>

On Fri, 2002-11-01 at 05:03, James Simmons wrote:
> 
> Sorry about not producing a regular diff. The final changes really did a
> number on the framebuffer console code in fbcon.c so I had some massive
> work to do. I still have a massive amount of cleaning up to do. Also a lot
> of drivers stil haven't been ported.
> 
> So here is the regular diff against 2.5.45
> 
> http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz
> 

James,

I tried the patch, and it does produce a cleaner and smaller driver. 
Overall, I like it. Some observations:

1. Without the fb_set_var() hook, switching from X messes up the
console.  I would guess this will be addressed by the console?

2. Console panning/wrapping does not work.  updatevar includes a check
"if (con == info->currcon)", and my guess is info->currcon is obsoleted
so the check always fails.

3. fbdev can be loaded without taking over the console.  After running
an fb-based application, exiting fbdev messes up the vga console
(actually hangs the system).  Should the fbdev driver provide the
capability to restore the VGA state then, ie at info->fb_release?

4. The initial font loaded is 8x8. It seems that 8x16 fonts are limited
for the SGI console console only.  Any reason why?

5.  The cfb_* drawing functions still behave erratically, especially in
emacs.  Geert has made some versions that work correctly for me.  This
was discussed in a thread sometimes ago.

Some of the above problems may be from the driver side (ie. #3).

Tony

Attached is a diff that will allow the logo to be drawn at 8-bpp
pseudocolor:

diff -Naur linux-2.4.45-fbdev/drivers/video/console/fbcon.c linux/drivers/video/console/fbcon.c
--- linux-2.4.45-fbdev/drivers/video/console/fbcon.c	Fri Nov  1 19:19:13 2002
+++ linux/drivers/video/console/fbcon.c	Fri Nov  1 19:20:00 2002
@@ -2281,12 +2281,12 @@
 		}
 		saved_palette = info->pseudo_palette;
 		info->pseudo_palette = palette;
-		image.width = LOGO_W;
-		image.height = LOGO_H;
-		image.depth = depth;
-		image.data = logo;
-		image.dy = 0;
 	}
+	image.width = LOGO_W;
+	image.height = LOGO_H;
+	image.depth = depth;
+	image.data = logo;
+	image.dy = 0;
 #endif
  
     for (x = 0; x < num_online_cpus() * (LOGO_W + 8) &&



  


 

  parent reply	other threads:[~2002-11-01 19:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 21:03 [BK fbdev updates] James Simmons
2002-10-31 21:42 ` [Linux-fbdev-devel] " Antonino Daplas
2002-11-01  0:44   ` James Simmons
2002-11-01  9:05 ` Sven Luther
2002-11-01 17:12   ` James Simmons
2002-11-01 19:41 ` Antonino Daplas [this message]
2002-11-01 23:29   ` James Simmons
2002-11-02  4:06     ` Antonino Daplas
2002-11-08  0:01       ` James Simmons
2002-11-03  8:40     ` [Linux-fbdev-devel] " Antonino Daplas
2002-11-07 22:18       ` James Simmons

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=1036178902.572.33.camel@daplas \
    --to=adaplas@pol.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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).