From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
"Ville Syrjälä" <syrjala@sci.fi>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] fbdev: workaround for broken X servers
Date: Wed, 3 Nov 2004 21:09:29 +0800 [thread overview]
Message-ID: <200411032109.29734.adaplas@hotpop.com> (raw)
In-Reply-To: <20041103032613.GA3677@sci.fi>
On Wednesday 03 November 2004 11:26, Ville Syrjälä wrote:
> On Wed, Nov 03, 2004 at 01:13:39PM +1100, Benjamin Herrenschmidt wrote:
> > Hi !
> >
> > + /* Workaround for broken X servers */
> > + if (blank > VESA_POWERDOWN)
> > + blank = VESA_POWERDOWN;
> > +
> > if (info->fbops->fb_blank && !info->fbops->fb_blank(blank, info))
> > return 0;
>
> This goes against documented behaviour (see fb.h). Also drivers/char/vt.c
> seems to agree with fb.h, as do at least atyfb and matroxfb. I also used
> the vesa level+1 convention in DirectFB. So AFAICS this patch would
> confuse console power management, XFree86/X.Org, DirectFB and some fb
> drivers.
True enough. The convention is if the display is active, then suspend. If
it is suspended, then powerdown. And if already powered down, then do
nothing. It does so by by sending a blank flag of VESA_POWERDOWN + 1.
This is the convention used by the vt layer, I don't what is used by user apps.
The above patch won't break console power management as the console calls
fbcon_blank(), not fb_blank().
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_idU88&alloc_id\x12065&op=click
next prev parent reply other threads:[~2004-11-03 13:09 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 [this message]
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
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=200411032109.29734.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=syrjala@sci.fi \
--cc=torvalds@osdl.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).