Ok, stop right here!

We don't need more ioctl() callable accel commands, and if it isn't
immediately obvious how to generalize an interface it should not be
generalized at the KGI level.

Once you got the mode-setting working and implemented a few of the
existing ioctl()s to get a feel for the accelerator you can forget
about the ioctl() toy. Drivers communicate with LibGGI either through
direct mapped accel registers, ping-pong buffers, or some other
optimized method.

All intelligence and interfaces belong in LibGGI. The sole purpose of
KGI drivers is to set modes and maintain system security while exporting
the graphics hardware to LibGGI as direct as possible.

//Marcus
-- 
-------------------------------+------------------------------------
        Marcus Sundberg        | http://www.stacken.kth.se/~mackan/
 Royal Institute of Technology |       Phone: +46 707 295404
       Stockholm, Sweden       |   E-Mail: [EMAIL PROTECTED]

Reply via email to