mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Bogusz <qboosh@pld-linux.org>
To: linux-kernel@vger.kernel.org, linux-fbdev-devel@lists.sourceforge.net
Subject: [PATCH 2.6][RESEND] fbcon margins colour fix
Date: Thu, 18 Mar 2004 00:31:35 +0100	[thread overview]
Message-ID: <20040317233135.GB3510@satan.blackhosts> (raw)

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

I sent it a few times to linux-kernel and at least one to
linux-fbdev-devel, but haven't seen any comments - and this annoying
changing margins colour seems to be still there in 2.6.4 (at least on
tdfxfb).


-- 
Jakub Bogusz    http://cyber.cs.net.pl/~qboosh/

[-- Attachment #2: linux-fbcon-margins.patch --]
[-- Type: text/plain, Size: 1373 bytes --]

This fixes "margin colour" (colour used to clear top and bottom margins -
e.g. remaining half of line at the bottom of 100x37 console on 800x600
framebuffer).

I don't know what was the intention behind using attr_bgcol_ec() here,
but it caused using of background colour of last erase character to clear
margins (thus it was changing from time to time when switching consoles
or so).
I think that margin colour should be equal overscan colour, which seems
to be always black.
This patch changes margin colour to black (or colour 0 in palette modes)
in accel_clear_margins() and removes unused then bgshift variable.

	-- Jakub Bogusz <qboosh@pld-linux.org>

--- linux-2.6.4/drivers/video/console/fbcon.c.orig	2004-03-11 03:55:36.000000000 +0100
+++ linux-2.6.4/drivers/video/console/fbcon.c	2004-03-17 20:47:38.749388312 +0100
@@ -489,7 +489,6 @@
 void accel_clear_margins(struct vc_data *vc, struct fb_info *info,
 				int bottom_only)
 {
-	int bgshift = (vc->vc_hi_font_mask) ? 13 : 12;
 	unsigned int cw = vc->vc_font.width;
 	unsigned int ch = vc->vc_font.height;
 	unsigned int rw = info->var.xres - (vc->vc_cols*cw);
@@ -498,7 +497,7 @@
 	unsigned int bs = info->var.yres - bh;
 	struct fb_fillrect region;
 
-	region.color = attr_bgcol_ec(bgshift, vc);
+	region.color = 0; /* margins color = overscan color */
 	region.rop = ROP_COPY;
 
 	if (rw && !bottom_only) {

             reply	other threads:[~2004-03-17 23:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 23:31 Jakub Bogusz [this message]
2004-03-18  9:21 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2004-03-18  9:37   ` Jakub Bogusz
2004-03-18  9:42     ` Geert Uytterhoeven

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=20040317233135.GB3510@satan.blackhosts \
    --to=qboosh@pld-linux.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

all inboxes | Powered by JetHome®