From: Emmanuel Marty <core@suntech.fr>
  To  : ggi-develop@eskimo.com
  Date: Fri, 07 Aug 1998 07:51:59 +0000

Re: Mach64 support? and some questions

Hi Peter,

> Is anything happening on the area of ATI Mach64 support? Is any progress
> being made on this front? (is there still anyone developing the driver?)

Someone was supposedly working on a Mach driver, but granted we didn't
have much news about that lately. A shame, the ATI line of chips is probably
the only big one that KGI misses a driver for. Interested in developing one? :)

> Now some more questions:
> 1) Why do kgi (the original) and kgicon have seperate driver
> directories? Surely if the drivers are the same between the two, there
> should be no need for two different sets of drivers? (kgi/...
> kgicon/kgi/...)

Jon set it up that way because he didn't want to disturb regular kgi
development.. But there won't be two driver trees, no. kgicon uses
standard Dali drivers (with some namespace cleanup, but that's it), and
will use Steffen's new KGI API whenever ..

> 2) Is kgi still being developed? Or have people dumped it in favour of
> kgicon / fbcon?

Steffen Seeger is working on a new KGI.. It will share drivers with kgicon
so that developers and users don't pull the rest of their hair. The best
is to mail Steffen directly..

> 3) Why doesn't the kgicon IBM vga driver compile? I go to the directory
> kgicon/kgi, do a ./configure, select all the IBM vga options, and then
> do a 'make'. It bombs on the first file complaining about missing header
> files.

Headers not installed in the right place maybe, what's the exact error message ?

> 4) How about some kgicon docs? There are none right now.

kgicon is a bridge between two documented pieces of code - a kgi driver
(conforming to the KGI programming interface) and fbcon (documented in
Documentation/fb in the standard 2.1.x kernel source tree from 2.1.107
and up). One shouldn't need much documentation about it..

Right now the project is in a strange state, but when we have the saint
graal (KGI new api) and that all driver developers polish their code for
kgicon / the new KGI, all should be fine again..

--
Emmanuel