Index: [thread] [date] [subject] [author]
  From: James Simmons <jsimmons@edgeglobal.com>
  To  : ggi-develop@eskimo.com
  Date: Tue, 2 Feb 1999 14:54:17 -0500 (EST)

Re: C&T driver

> Umm, it used to be that way, and we changed it to 1 because the vga can't
> do 8bpp above 320x200 without bank switching; everyone was trying to 
> run at 80x25,8x16 8bpp and it was hosing the machine.
> 
> We _really_ should go all out to make kgicon.o work right for new users 
> -- unfortunately there are quite a few ways to screw it up.  IMO kgicon
> should check for what buffer layouts have been compiled into the 
> kernel and try the best one available, and then if that checkmode fails,
> try the next best bit depth and so on.  This should be the "dummy behavior"
> and if the user actually explicitly states the depth there should be 
> only one checkmode, at the requested depth.
>

Actually IMO in the call kgi_monitor_init we set kgi_display.mode with the
highest mode the monitor can support. Then when we call kgi_chipset_init
we check to see if the mode the monitor can support can be supported. If
not we set the mode to what the card can support etc. 

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