[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <787b0d920705030714k3b290d2csa38a5df63c692d6f@mail.gmail.com>
Date: Thu, 3 May 2007 10:14:30 -0400
From: "Albert Cahalan" <acahalan@...il.com>
To: "Jan Engelhardt" <jengelh@...ux01.gwdg.de>
Cc: "H. Peter Anvin" <hpa@...or.com>,
"Antonino A. Daplas" <adaplas@...il.com>,
"Geert Uytterhoeven" <geert@...ux-m68k.org>,
linux-kernel <linux-kernel@...r.kernel.org>, aeb@....nl
Subject: Re: console font limits
On 5/3/07, Jan Engelhardt <jengelh@...ux01.gwdg.de> wrote:
> On May 3 2007 02:17, Albert Cahalan wrote:
> > Those sizes are unreadable on the 200 dpi OLPC XO screen,
>
> Hm that should have read, for you:
> I don't object implementing support for larger sizes.
> (But I wonder how that should work without FB/CVIDIX/SVGA/VESA extensions.)
>
> Note that I was assuming that no FB is used:
I'm assuming that the FB is used. Neither of my two
computers can do VGA text mode. Even for computers
which can do VGA text mode, if you want large fonts
(either by number of characters or by character width)
you need to use FB. That's just a requirement; anything
else would be insane.
> For everything beyond Latin, fbiterm should work a lot better.
Then, as with X, you have problems with kernel messages.
Reliably sending printk through a userspace console is not
even possible. (consider a panic, OOM, or runaway RT task)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists