linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Winischhofer <thomas@winischhofer.net>
Cc: adaplas@pol.net, jsimmons@infradead.org,
	linux-fbdev-devel@lists.sourceforge.net
Subject: [Fwd: Re: Some questions]
Date: Thu, 06 Mar 2003 10:31:42 +0100	[thread overview]
Message-ID: <3E67157E.3090607@winischhofer.net> (raw)



-------- Original Message --------
Subject: Re: [Linux-fbdev-devel] Some questions
Date: Thu, 06 Mar 2003 10:30:21 +0100
From: Thomas Winischhofer <thomas@winischhofer.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
References: <Pine.GSO.4.21.0303061006180.28248-100000@vervain.sonytel.be>

Geert Uytterhoeven wrote:
 > What if fbcon implements a text console _on top of_ fbdev? I.e. it
 > uses the current resolution?
 >
 > If you use stty to change the number of cols/rows, or change the font,
 > or use fbset, your text console may end up being smaller or larger
 > than the real screen size, in which case margins are cleared, or
 > columns/lines are lost. (Optionally, we can center the text console if
 >  it's smaller than the real  screen size.)
 >
 > IMHO this is the most orthogonal approach. Fbcon takes care of the
 > text console, fbdev takes care of the graphics hardware and the video
 > mode. Both parts do (try to) not influence each other.
 >
 > Optionally, fbset can call stty to change the number of cols/rows, if
 > the user wants that.
 >
 > What do you think?

I think that sounds like the best solution, and it also respects the
fact that fbcon and fbdev are two different pairs of shoes.

Thomas

-- 
Thomas Winischhofer
Vienna/Austria
mailto:thomas@winischhofer.net            http://www.winischhofer.net/






-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

                 reply	other threads:[~2003-03-06  9:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3E67157E.3090607@winischhofer.net \
    --to=thomas@winischhofer.net \
    --cc=adaplas@pol.net \
    --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).