linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: jsimmons@pentafluge.infradead.org
Cc: adaplas@pol.net, David Eger <eger@havoc.gtf.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Sane behavior of fbset
Date: Wed, 23 Jun 2004 14:38:45 -0500	[thread overview]
Message-ID: <1088019524.1855.159.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.56.0406231958340.27210@pentafluge.infradead.org>

On Wed, 2004-06-23 at 14:00, jsimmons@pentafluge.infradead.org wrote:
> > I still think (didn't I repeat it often enough) that the whole idea
> > of stty "inventing" modes based on console size is broken. We simply
> > can't rely on good enough monitor detection & mode list building to
> > be able to pick proper modes. Not only our code is far from ready for
> > that, but it will also call all sort of problems to users (remember
> > you monitors that need different subtle geometry settings for each
> > different mode you use ?)
> > 
> > It may have looked like a nice idea, but I think it's just wrong.
> 
> Its a POSIX standard. You need to yell at them. 

I don't remember seeing anything in POSIX regarding tweaking monitor
video modes ;)

> > fbset sends an ioctl straight to the fbdev, and doesn't update fbcon
> > at the moment. The callback mecanism I added for power management
> > should allow to restore 2.4 functionality there, but this has not
> > been implemented yet afaik.
> 
> It will be added back. I didn't merge the one from before because it had 
> problems. 
-- 
Benjamin Herrenschmidt <benh@kernel.crashing.org>



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

  reply	other threads:[~2004-06-23 19:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18  1:45 Sane behavior of fbset Antonino A. Daplas
2004-06-18  8:24 ` Geert Uytterhoeven
2004-06-23 18:52   ` jsimmons
2004-06-23 18:59     ` Geert Uytterhoeven
2004-06-23 19:07       ` jsimmons
2004-06-23 19:17         ` Geert Uytterhoeven
2004-06-23 19:21           ` jsimmons
2004-06-18 13:31 ` John Zielinski
2004-06-18 17:38 ` David Eger
2004-06-18 18:40   ` Antonino A. Daplas
2004-06-19  3:16     ` David Eger
2004-06-19  6:13       ` Antonino A. Daplas
2004-06-19 15:59         ` John Zielinski
2004-06-23 18:57           ` jsimmons
2004-06-23 15:55         ` Benjamin Herrenschmidt
2004-06-23 16:08           ` Geert Uytterhoeven
2004-06-23 17:29           ` John Zielinski
2004-06-23 20:39             ` jsimmons
2004-06-23 21:44               ` John Zielinski
2004-06-23 19:00           ` jsimmons
2004-06-23 19:38             ` Benjamin Herrenschmidt [this message]
2004-06-23 20:03               ` jsimmons
2004-06-23 20:12                 ` Benjamin Herrenschmidt
2004-06-23 23:50                   ` Antonino A. Daplas
2004-06-24  2:17           ` Antonino A. Daplas
2004-06-19 15:50       ` John Zielinski
2004-06-23 18:55       ` jsimmons

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=1088019524.1855.159.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=adaplas@pol.net \
    --cc=eger@havoc.gtf.org \
    --cc=jsimmons@pentafluge.infradead.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 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).