Index: [thread] [date] [subject] [author]
  From: Steffen Seeger <seeger@physik.tu-chemnitz.de>
  To  : ggi-develop@eskimo.com
  Date: Wed, 29 Jul 1998 17:02:01 +0200 (MEST)

Re: I've seen the stars too... [Re: kgicon, etc]

 
> On Wed, 29 Jul 1998, Rodolphe Ortalo wrote:
> 
> > >IIRC it's a known problem (since the kernel's driver will already have
> > >claimed the vga space).  The #if 0 is alright in the short term, I'm not
> > >sure what exactly should be done in the long term...

Write a proper console driver that doesn't claim these ports.
The situation is just the following: you have a in-kernel driver 
claiming resources for a device it serves in a kind of compatibility mode.
Later, a user-process starts and fiddles with the same device. If it
is polite, it even tells the kernel what it did (VT_RESIZE is the ioctl
IIRC). 

You know, my opinion about the console code can't be printed, can not 
even be said in front of an audience. To say the least, it's a mess.

The KGI i386 boot display driver code doesn't use more than
a plain frame buffer. And it is shut up when a real driver loads.
That's why I am skeptical about the kgicon approach, but hey,
I am willing to learn.

> > Please could someone with experience on this topic provide hints ?
> > (Steffen, Andreas ?) I noted that the Matrox dali kgi drivers do _not_
> > use the VGA IO region. Is this a feature of the card ?

Yes.

			Steffen

----------------- e-mail: seeger@physik.tu-chemnitz.de -----------------

Index: [thread] [date] [subject] [author]