linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: resizing results.
Date: Tue, 16 Mar 2004 11:10:37 +1100	[thread overview]
Message-ID: <1079395837.1968.194.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0403151732090.19671-100000@phoenix.infradead.org>

On Tue, 2004-03-16 at 04:38, James Simmons wrote:
> Hi folks. 
> 
>    I have been doing some work on cleaning up and debugging the resize 
> issue of fbcon. The first think I discovered where I never paid attention 
> to before was that the number of columns and rows change you you run 
> setfont. Isn't this wrong. The number of rows and columns should remain 
> the same. Only the font size chaneg which causes a console resolution 
> change.

I don't agree. As a user, if I change the font, I expect a row/col
change rather than a resolution change...

Note that the resolution change code doesn't work properly anyway,
not until we have proper code to look for a matching mode along with
monitor detection in drivers, which we don't have.

Ben.




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  parent reply	other threads:[~2004-03-16  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15 17:38 resizing results James Simmons
2004-03-15 19:34 ` Chad A Daelhousen
2004-03-15 21:48 ` Geert Uytterhoeven
2004-03-16  0:10 ` Benjamin Herrenschmidt [this message]
2004-03-16  0:52   ` James Simmons

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=1079395837.1968.194.camel@gaston \
    --to=benh@kernel.crashing.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).