All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: David Eger <eger@havoc.gtf.org>, jsimmons@infradead.org
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Sane behavior of fbset
Date: Sat, 19 Jun 2004 14:13:28 +0800	[thread overview]
Message-ID: <200406191413.28339.adaplas@hotpop.com> (raw)
In-Reply-To: <20040619031650.GC14319@havoc.gtf.org>

On Saturday 19 June 2004 11:16, David Eger wrote:
> On Sat, Jun 19, 2004 at 02:40:46AM +0800, Antonino A. Daplas wrote:
> > In 2.6
> >
> > 1. If you use fbset, you will get screen corruption or hang the GPU
> >
> > 2. stty will do the function of fbset.  However, stty will only pass rows
> > and cols (xres and yres respectively).  There is no information for bit
> > depth, timings, virtual resolution, etc.
>
> So *this* is what's going on with my port of the cirrusfb driver--why fbset
> wasn't working... for radeonfb fbset still works in 2.6, so i didn't
> realize there was this problem... What's so wonky with the fbset code path
> that screws things up? and why does stty work?

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.

Tony




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND

  reply	other threads:[~2004-06-19  6:13 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 [this message]
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
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=200406191413.28339.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --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 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.