On Tue, 14 Dec 1999, Jon M. Taylor wrote:
On Mon, 13 Dec 1999, teunis wrote:
And many of the interfaces
developed (ping/pong buffers as an example) are either currently unusable
or not really tested all that much. I'd -love- to see some sort of formal
FAQ/RFC on this issue...
Hi !
I am running debian, so i installed the libggi2 package, and the libgii
package, etc. Then i went to put kgi in my kernel. I found
framebufferconsole (fbcon) support, and thought that kgi stuff was renamed
to fbcon, so i selected it for my ATI mach64 PCI video card. (selected vesa
Well. Concerning this issue, currently, with GGI: you do not need to patch
your kernel, but you can of course if you really insist in doing it.
It may sound funny, but, in fact:
- KGIcon is a bridge that allows to use KGI (1998 version) drivers
within the context of the (now standard) linux
Anyway, my system booted and i got the penguin on bootup, and figured
all
must be working just peachy... then i went to run heretic as a demo...
My
screen started jumping, and my monitors menu had a cow. It reported
that
the video card was trying to refresh at 214Hz.
If you use a
On Wed, 15 Dec 1999, Firstname Lastname wrote:
ok, I'm fuzzy here. if libggi can use KGI or fbcon, then why make a KGIcon
driver (differnt fron the KGI driver) which redirects KGI calls to fbcon
calls?
kgicon is a way to use KGI drivers without patching the kernel, by
having them emulate
