Re: GGI, EGCS/PGCC, Kernel source

Jes Degn Soerensen (jds@kom.auc.dk)
02 Mar 1998 16:03:49 +0100


>>>>> "Jason" == Jason McMullan <jmcc@pepsi.visus.com> writes:

Jason> Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be> wrote
Jason> with confidence:
>> 2. The abstract console stuff is multi-platform, and supports both
>> VGA text (currently 80x25 only), graphical consoles and GSPs
>> (e.g. TIGA 340x0). It's known to work on at least: - ia32 (aka
>> i386): VGA text mode (vgacon)

Jason> Your only weak spot - no VGA framebuffer.....

But we rely on XFree to handle that for the moment, when these new AGP
boards without VGA-text modes become available people will need fbdev
anyway ;-)

>> 4. Of course CONFIG_ABSTRACT_CONSOLE is just a config option. We
>> provide a new console.c (console.new.c) and some changes in a few
>> other files.

Jason> Ditto with the current GGI-EvStack code. It's all a config
Jason> option. We even provide in the EvStack branch a `conlinux'
Jason> linux console emulation helper to allows SVGAlib and XFree86 to
Jason> work, provided you haven't install a KGI display driver.

But over time the config option should go away and the choice should
rather be whether people have VGA style text-mode (vgacon), fbcon or
both.

Jason> Oh, and by the way, I Like VI. I'll pull a paint gun on any of
Jason> you Eight Megs And Constantly Swapping lisp-lovers! ;^) [see
Jason> http://www.linuxexpo.com for why I said this.]

Ahhh, thats the reason - beware!

>> Final reason (more emotionally): is there any good reason why the
>> first non-Intel port of Linux (for the ignorant: the m68k port) is
>> still not completely integrated, while we had all those nice things
>> running back in 1994 (no typo, one nine nine four!)????

Jason> Agreed. This type of well-architected code should have been in
Jason> the kernel from v1.0.

IMHO that is actually one of the main problems for us, the port was
started too early (if one can say that ;-) so that portabillity was
not really an issue and many things had to be done the hard way. The
result was that the m68k port diverted a bit too far from the native
source. Fortunately this is moving in the right direction these days.

Jes

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu