linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Eger <eger@havoc.gtf.org>,
	James Simmons <jsimmons@infradead.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Sane behavior of fbset
Date: Thu, 24 Jun 2004 10:17:37 +0800	[thread overview]
Message-ID: <200406241017.37503.adaplas@hotpop.com> (raw)
In-Reply-To: <1088006149.1832.145.camel@gaston>

On Wednesday 23 June 2004 23:55, Benjamin Herrenschmidt wrote:
> > The flow of fbset is upstream:  fbset->fbdev->fbcon->vc (2.4 code)
> > The flow of stty is downstream: stty->vc->fbcon->fbdev (2.6 code)
> >
> > I don't know how radeonfb does it though.
>
> 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.
>

It started out like this, during 2.5 development. The discussions were
not very clear cut, as ironing bugs was the main concerned, but basically
it all boils down to the following points:

a. fbset functionality was lost (or removed), so how do we change the
resolution of fbdev?

b. what should be the correct behavior of stty?  

So there were 2 ideas:

1. An stty call will just have to modify the video mode. This will require
that fbdev must be able to handle mode change requests independently.

2. stty will just have to produce a smaller or larger viewport, without
changing the resolution of the video mode. This will involve that fbcon
must be able to do clipping, otherwise it will attempt to write past fb
memory if vc size > fbdev size.

So, I submitted 2 patches.

For 1, I added a hook for con_resize. And for 2,  I added clipping code
for all the accel_* functions, no con_resize hook.

You probably guessed correctly which got merged, 1. And 
because 1 requires fbdev to handle mode changes independently, it's
unavoidable that we need functions to help drivers validate and choose
the correct modelines.  So, EDID parsing,  GTF calculation, and mode
validation were introduced in fbmon.c

(fbset behavior remained undefined until this thread)

Tony




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

  parent reply	other threads:[~2004-06-24  2:21 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
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 [this message]
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=200406241017.37503.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=benh@kernel.crashing.org \
    --cc=eger@havoc.gtf.org \
    --cc=jsimmons@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).