On Thu, 6 May 2004, Jon Smirl wrote:
> Another topic that I missed was, why did kgi fail and what can we do to avoid
> repeating the same path this time around.
IIRC, the main reasons were:
- GGI wanted to do too much at once and was too intruisive (conclusion:
always advance in small steps, not big leaps):
o kernel graphics drivers (KGI)
o new input subsystem (similar to what we're heading to now)
o user space library (libggi, AFAIK the only part that's still alive)
- fbdev was better in multi-platform handling (m68k -> PPC -> ia32 -> SPARC
-> alpha -> ...)
Please correct me if I'm wrong ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
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
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
