Andreas Beck writes:
> > The X server (XGGI) uses direct access to the buffers, so you never
> > know when it has changed something or not. The only solution is to
> > make a smarter X server.
>
> Yes basically, though a possible workaround would be to use some kind of
> checksumming procedure that would try to autodetect the changed regions.
>
> Not exactly an elegant solution, but a possible workaround. (Remote control
> software for Windoze uses this technique).
>
> The idea would be to make checksums over the rows and columns when blitting
> and comparing current results with the last results. This will result in
> a rectangle that needs to be updated by leaving all lines alone that have not
> changed and only changing thouse columns that have changes.
Ahh. I can see how that would be good when transfer time is a lot
bigger than read time (e.g. over a network). It won't work when
transfer time is comparable to read time (e.g. tile blitting into
local framebuffers), right ?
One idea I was pondering was to use the MMU "dirty" bit to track which
areas of the buffer had been modified -- prolly not possible in Linux
(IIRC the dirty bit is used by Linux for doing swapping stuff).
Cheers,
__
\/ Andrew Apted <[EMAIL PROTECTED]>
