From: Brian Julin <bri@forcade.calyx.net>
  To  : ggi-develop@eskimo.com
  Date: Wed, 8 Jul 1998 15:53:54 -0400 (EDT)

Re: set_mode complexity

On Wed, 8 Jul 1998, Salvador Eduardo Tropea (SET) wrote:
> What I still thinking is that the complex negotiation must be moved 
> outside the core of the driver. Perhaps a solution could be make it 
> as another module (or the same just to make less troubles but very 
> well divided internally).

I believe I'm not the only one who's commented that except for the 
primitive code necessary to find default modes in an emergency or during 
initialization, the drivers should merely validate, cache, and program modes; 
not set them.

The only role they should play in the calculation process is providing 
info to whatever user-space programs handles calculating non-default modes.
Moving the rest into user-space removes the kludge of having a driver
"read a system configuration file," the calculation library does that.

(So There I was starting to work on a evstack-based way to replace the 
mode negotiation/hardware initialization system so things would
be more flexible, and then along came kgicon and, well, no more 
kgi-manager for a while, not that kgicon isn't a good thing to have
happened.)

--
Brian S. Julin