linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Pfaff <tpfaff@pcs.com>
Cc: linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com
Subject: Re: [PATCH] [Resend] fbcon : fix color generation for monochrome framebuffer
Date: Thu, 31 Jan 2008 14:07:01 -0800	[thread overview]
Message-ID: <20080131140701.b584430e.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0801281052480.4385@lxtpfaff.pcs.ditec.de>

On Mon, 28 Jan 2008 11:03:38 +0100 (CET)
Thomas Pfaff <tpfaff@pcs.com> wrote:

> Patch recreated for 2.6.24.
> 
> The current attr_fgcol_ec / attr_bgcol_ec macros do a simple shift of bits to 
> get the color from vc_video_erase_char. For a monochrome display however the 
> attribute does not contain any color, only attribute bits. Furthermore the 
> reverse bit is lost because it is shifted out, the resulting color is always 0.
> 
> This can bee seen on a monochrome console either directly or by setting it to 
> inverse mode via "setterm -inversescreen on" . Text is written with correct 
> color, fb_fillrects from a bit_clear / bit_clear_margins will get wrong colors.
> 

I'm struggling to understand the seriousness of this bug.  Do you think
this patch needs to be backported to 2.6.24.x?

> +#define mono_col(info)							\
> +	(~(0xfff << (max((info)->var.green.length,			\
> +			 max((info)->var.red.length,			\
> +			     (info)->var.blue.length)))) & 0xff) 

This macro is dangerous because it references its arg more than a single
time.  If someone does mono_col(*foo++) they will get a surprise.

So please follow the general rule here: do not implement in a macro that
which could have been implemented in a C function.

Plus C fundtions have better type checking and for some reason people are
more likely to document C functions.

> +static inline int attr_col_ec(int shift, struct vc_data *vc,
> +			      struct fb_info *info, int is_fg)
> +{
> +	int is_mono01;
> +	int col;
> +	int fg;
> +	int bg;
> +
> +	if (!vc)
> +		return 0;
> +
> +	if (vc->vc_can_do_color)
> +		return is_fg ? attr_fgcol(shift,vc->vc_video_erase_char)
> +			: attr_bgcol(shift,vc->vc_video_erase_char);
> +
> +	if (!info)
> +		return 0;
> +
> +	col = mono_col(info);
> +	is_mono01 = info->fix.visual == FB_VISUAL_MONO01;
> +
> +	if (attr_reverse(vc->vc_video_erase_char)) {
> +		fg = is_mono01 ? col : 0;
> +		bg = is_mono01 ? 0 : col;
> +	}
> +	else {
> +		fg = is_mono01 ? 0 : col;
> +		bg = is_mono01 ? col : 0;
> +	}
> +
> +	return is_fg ? fg : bg;
> +}

This function is vastly too large to be inlined.  Even mono_col() is too
large to be inlined.

Please implement both as regular C functions, then take a look at the
before and after output from size(1).

> +#define attr_bgcol_ec(bgshift,vc,info)		\
> +	attr_col_ec(bgshift,vc,info,0);
> +#define attr_fgcol_ec(fgshift,vc,info)		\
> +	attr_col_ec(fgshift,vc,info,1);
> +

Could be implemented as C functions.

I'll queue the pastch up for testing as-is, but would like a de-macroed,
de-inlined version please.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-01-31 22:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 10:03 [PATCH] [Resend] fbcon : fix color generation for monochrome framebuffer Thomas Pfaff
2008-01-31 22:07 ` Andrew Morton [this message]
2008-01-31 22:18   ` Andrew Morton
2008-02-01  8:02   ` Geert Uytterhoeven
2008-02-01 11:58   ` Thomas Pfaff
2008-02-01 12:24     ` Geert Uytterhoeven
2008-02-01 13:01       ` Thomas Pfaff
2008-02-01 13:38         ` Geert Uytterhoeven
2008-02-01 13:55           ` Thomas Pfaff

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=20080131140701.b584430e.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adaplas@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=tpfaff@pcs.com \
    /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).