landru@stan.com (Mike Rosenlof) (02/14/89)
Hello!
I'm working on a driver for a new frame buffer to run on Solbourne's
Sun4 compatable workstations, and I'd like some feedback if I'm
approaching things corrrectly. I started questioning things after
hearing some of the presentations at the X conference (great job
everyone!)
Our current X server supports two Sun-compatable frame buffers, a
monochrome, and a CG4 compatable frame buffer, so this server I create
must also support these devices through the mfb and cfb code. Our new
frame buffer has a little hardware to accelerate a few operations like
line drawing and bit blt, but not everything the server needs.
/--> Pixmaps
/
+---------+ +-------------------+
+----------+ | | | |
| | ---> | CFB | -----> | |
| DIX | | | | f r a m e |
| and | +---------+ | |
| MI | +-----------+ | B u f f e r |
| | ---> | | | |
+----------+ | new | ---> | |
| functions| | |
+-----------+ +-------------------+
I have made no changes to the CFB functions, and the new functions are
all referenced through the GC, as usual.
Finally, my question---
My biggest difficulty was making the distinction between when to install
the CFB functions in a GC to handle pixmaps, or the new functions to
handle the frame buffer. I'm making the break in the new validage GC
function, keying of the drawable type to make that decision. Is this
the right place? If not, where? My trail of new functions can trace
back from validageGC to createGC to createWindow to initScreen...
thanks!
mike
--
Mike Rosenlof Solbourne (303)447-2861
2190 Miller Drive Computer, Inc. stan!landru@boulder.coloradoedu
Longmont Colorado landru@stan.uucp
80501 ...hao!boulder!stan!landru