From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] fbdev: workaround for broken X servers
Date: Fri, 5 Nov 2004 20:55:14 +0800 [thread overview]
Message-ID: <200411052055.17316.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.GSO.4.61.0411051313130.15464@waterleaf.sonytel.be>
On Friday 05 November 2004 20:15, Geert Uytterhoeven wrote:
> On Fri, 5 Nov 2004, Benjamin Herrenschmidt wrote:
> > > But every existing application that uses (shiver) the kernel headers
> > > will break after this change...
> >
> > Geert, can you explain the whole story please ?
>
> The story about the +1 or the story about the breakage?
>
> The Story About The +1
> ----------------------
> Since the VESA levels do not provide a way to blank (`make it black') the
> screen, the +1 is introduced. Hence 0 means unblank, 1 means black screen,
> 2 means lowest power save level, and so on...
And make it black is usually done in software (by memsetting the screen with
the black color).
So why not this: In fbcon_blank(), if the blank parameter is:
0 - unblank the screen, and call info->fbops->fb_blank(VESA_NO_BLANKING),
then return a nonzero value to force a redraw.
1,2,3,4 - clear the screen with all black
2,3,4 - call info->fbops->fb_blank(blank - 1);
Similarly, we can do the same thing in fbmem.c:fb_blank(), but without the software
blanking.
Drivers will just need to follow the VESA_* defines in fb.h (which happens to be also
defined in console.h)
Tony
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next prev parent reply other threads:[~2004-11-05 12:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 2:13 [PATCH] fbdev: workaround for broken X servers Benjamin Herrenschmidt
2004-11-03 3:26 ` Ville Syrjälä
2004-11-03 13:09 ` Antonino A. Daplas
2004-11-03 14:01 ` Ville Syrjälä
2004-11-03 21:42 ` Antonino A. Daplas
2004-11-05 5:49 ` Benjamin Herrenschmidt
2004-11-05 9:04 ` Geert Uytterhoeven
2004-11-05 9:36 ` Ville Syrjälä
2004-11-05 9:56 ` Geert Uytterhoeven
2004-11-05 10:43 ` Ville Syrjälä
2004-11-05 11:47 ` Benjamin Herrenschmidt
2004-11-05 12:15 ` Geert Uytterhoeven
2004-11-05 12:55 ` Antonino A. Daplas [this message]
2004-11-05 12:58 ` Geert Uytterhoeven
2004-11-05 13:15 ` Antonino A. Daplas
2004-11-05 15:00 ` Maciej W. Rozycki
2004-11-05 15:21 ` Geert Uytterhoeven
2004-11-05 15:59 ` Maciej W. Rozycki
2004-11-06 0:38 ` Benjamin Herrenschmidt
2004-11-06 2:02 ` Antonino A. Daplas
2004-11-06 3:06 ` Benjamin Herrenschmidt
2004-11-06 11:18 ` Antonino A. Daplas
2004-11-05 15:30 ` Ville Syrjälä
2004-11-05 15:48 ` Geert Uytterhoeven
2004-11-06 0:37 ` Benjamin Herrenschmidt
2004-11-06 2:07 ` Antonino A. Daplas
2004-11-05 11:46 ` Benjamin Herrenschmidt
2004-11-05 12:25 ` 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=200411052055.17316.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.