All normal graphics hardware has this property. You can't do posted reads
but you can do posted writes.
> buffer in main DRAM, and no 2D accel. (I'm thinking of my favourite ARM
> parts, like the ARM7500, CL-PS7110, EP7211 etc.) On these, reading the
> buffer is as fast as any other memory, so DinX should work fine the way it
> is now.
These already support nanogui and the Linux frame buffer driver
> Right. The idea is just to take clipping and blitting out of the server
> process and put them in the kernel, to avoid lots of context switches and
> big complex buffering code.
If your gui system is doing batching of commands this makes no difference.
Its one of the things X11 showed that was quite suprising.
> each, so the complexity of the visible area goes on the stack. Now, how
> much stack space does the kernel have? :)
Bang...
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/