Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1162151AbXECP4k (ORCPT ); Thu, 3 May 2007 11:56:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1162148AbXECP4k (ORCPT ); Thu, 3 May 2007 11:56:40 -0400 Received: from adicia.telenet-ops.be ([195.130.132.56]:57830 "EHLO adicia.telenet-ops.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1162152AbXECP4i (ORCPT ); Thu, 3 May 2007 11:56:38 -0400 Date: Thu, 3 May 2007 17:56:35 +0200 (CEST) From: Geert Uytterhoeven To: Jan Engelhardt Cc: Albert Cahalan , "H. Peter Anvin" , "Antonino A. Daplas" , linux-kernel , aeb@cwi.nl Subject: Re: console font limits In-Reply-To: Message-ID: References: <787b0d920704302109r352e6653wc71a0638cbfbdcce@mail.gmail.com> <1178021516.4372.62.camel@daplas> <46375738.1010007@zytor.com> <787b0d920705010849u52a4d6c3o2f1f800521ad5b95@mail.gmail.com> <787b0d920705022317j485cbe26wc83f071834c53584@mail.gmail.com> <787b0d920705030714k3b290d2csa38a5df63c692d6f@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2375 Lines: 60 On Thu, 3 May 2007, Jan Engelhardt wrote: > On May 3 2007 10:14, Albert Cahalan wrote: > > On 5/3/07, Jan Engelhardt 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. > > Some non-x86 boxes like sparc? OLPC is x86 ;-) > > 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) > > 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 ;-) Put people didn't like that, and disabled text output when the console is in KD_GRAPHICS mode... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/