[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0705032020130.18504@yvahk01.tjqt.qr>
Date: Thu, 3 May 2007 20:27:11 +0200 (MEST)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
cc: Albert Cahalan <acahalan@...il.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Antonino A. Daplas" <adaplas@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>, aeb@....nl
Subject: Re: console font limits
On May 3 2007 17:56, Geert Uytterhoeven wrote:
>>
>> Actually, the kernel could just "jump in". That is, when you start
>> in fb mode, you get the regular 8x16 vga font - on your choice of
>> resolution, and can also set it with setfont. So far so nice.
>> Now, when you start fbiterm -- for example to read CJK --, fbiterm
>> presents you with what looks like a 12x24 font. Also good.
>> It _looks_ to me like fbiterm does the drawing itself; ok too.
>> Now when the kernel is oopsing, it could just spew out the oops
>> trace in the regular font (vga8x16 or in case you use CONFIG_FONTS,
>> then that), possibly obstructing some output generated by fbiterm,
>> but in case of oops, I think this is ok.
>
>Funny, that's exactly how kernel messages where handled in the early
>fbdev days: just draw them to the frame buffer, whatever mode it is
>in...
>Just like on the SunOS boxes ;-)
Right, I remember! But not only SunOS, _SPARCs_ 'themselves' also do it.
OBP is always sun-style, i.e. black-on-white and a big 12x22 font,
even if you jump to it from Linux using Stop-A.
>Put people didn't like that, and disabled text output when the console
>is in KD_GRAPHICS mode...
at the cost of not getting the kernel oops, heh.
Jan
--
-
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