All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <syrjala@sci.fi>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	"Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: [PATCH] fbdev: workaround for broken X servers
Date: Fri, 5 Nov 2004 12:43:47 +0200	[thread overview]
Message-ID: <20041105104347.GA16300@sci.fi> (raw)
In-Reply-To: <Pine.GSO.4.61.0411051052490.15464@waterleaf.sonytel.be>

On Fri, Nov 05, 2004 at 10:56:04AM +0100, Geert Uytterhoeven wrote:
> On Fri, 5 Nov 2004, Ville [iso-8859-1] Syrjälä wrote:
> > On Fri, Nov 05, 2004 at 04:49:36PM +1100, Benjamin Herrenschmidt wrote:
> > > Ok, can we agree here on what has to be done ? X is hard-coding numbers
> > > that don't seem to be make any sense vs. our constants. In radeonfb, I
> > > used switch case on constants, not +1, so there is something I'm not
> > > getting. Besides, radeon always try to power down TFT panels when
> > > blank != 0, maybe I should improve that ... What is this +1 thing, where
> > > does it comes from ?
> > 
> > Maybe it's there because someone wanted to blank the display without 
> > disabling sync signals.
> 
> Yes of course! (/me wasn't completely awake yet)
> 
> > I suggest a new set of constants that cover all legal values. Here's the 
> > first drawft.
> > 
> > --- linux-orig/include/linux/fb.h	2004-11-05 12:25:14.087807848 +0200
> > +++ linux/include/linux/fb.h	2004-11-05 12:28:02.734169704 +0200
> > @@ -27,7 +27,7 @@
> >  /* #define FBIOSWITCH_MONIBIT	0x460E */
> >  #define FBIOGET_CON2FBMAP	0x460F
> >  #define FBIOPUT_CON2FBMAP	0x4610
> > -#define FBIOBLANK		0x4611		/* arg: 0 or vesa level + 1 */
> > +#define FBIOBLANK		0x4611		/* see FB_BLANK_* */
> >  #define FBIOGET_VBLANK		_IOR('F', 0x12, struct fb_vblank)
> >  #define FBIO_ALLOC              0x4613
> >  #define FBIO_FREE               0x4614
> > @@ -258,6 +258,12 @@
> >  #define VESA_HSYNC_SUSPEND      2
> >  #define VESA_POWERDOWN          3
> >  
> > +#define FB_BLANK_NO_BLANKING	0
> > +#define FB_BLANK_BLANKING	1
> > +#define FB_BLANK_VSYNC_SUSPEND	2
> > +#define FB_BLANK_HSYNC_SUSPEND	3
> > +#define FB_BLANK_POWERDOWN	4
> > +
> 
> Yep, these nicely cover the current intended behavior.
> 
> But every existing application that uses (shiver) the kernel headers will break
> after this change...

If the VESA constants are left intact nothing should change. BTW neither 
XFree86/X.Org nor DirectFB use them so chances are nothing else does.

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/


-------------------------------------------------------
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

  reply	other threads:[~2004-11-05 10:43 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ä [this message]
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=20041105104347.GA16300@sci.fi \
    --to=syrjala@sci.fi \
    --cc=adaplas@hotpop.com \
    --cc=benh@kernel.crashing.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.