nanogui@linuxhacker.org
nanogui@linuxhacker.org
On Tuesday, May 18, 1999 5:24 PM, Alex Holden [SMTP:alex@linuxhacker.org] wrote:
> On Tue, 18 May 1999, Greg Haerr wrote:
> > No, it is far too slow to draw everything twice, once in main, then in graphics
ram. In
>
> I don't know if there is a way to specify the write mode with the
> framebuffer drivers, but if there isn't then the best way is to use a
> buffer.
I *think* that the user can write the hw registers while drawing into
the mmap'd screen buffer.
I don't understand you're idea of a "buffer", then.
>
> > addition, you'd never know what's been modified. However, the bitblt operations
you
>
> That depends on how you implement it.
>
> > speak of are solved with a rearchitecture of the driver model I spoke of in an earlier
> > mail msg. This involved allowing all graphics operations to be performed on a "bitmap",
>
> That's a seperate issue to the drawing modes.
No, the drawing modes are implemented whether you're drawing into an
offscreen buffer or a screen buffer. If you do it right, you don't have to re-implement
the routine differently, thus keeping it smaller (nano ;-)
nanogui@linuxhacker.org