3 ms·
The memory mapped frame buffer is video memory, that's why you have to use a driver API to map it. Though obviously on many systems it ends up just being syste
by ajross 8y ago
The memory mapped frame buffer is video memory, that's why you have to use a driver API to map it. Though obviously on many systems it ends up just being system dram with different caching settings anyway.
And this isn't something you'd code a game with, but you'd be surprised at how high modern memory bandwidth is.
- Vendan 8y agoYeah, but linux framebuffer can do a very optimal swap... Just make the "virtual buffer" twice as tall, and then swap which "half" is "active" with a panDisplay IOCTL... That's why memcpy is such a bad idea, cause there is a very cheap method that can prevent tearing and such.
- pjmlp 8y agoAh memories of swapping card registers for double buffering on MS-DOS. Here is a tutorial about it, that I just googled for. http://www.brackeen.com/vga/unchain.html http://www.brackeen.com/vga/unchain.html
- onirom 8y agoI am aware of those, this might land in a future update. The library initial focus was just to get multiple cores to work for graphics task...
- v_lisivka 8y agoWith CRT monitors, it was possible to swap buffer in the middle of the frame, to display different buffers in different areas of the screen. It was used on 16bit systems for fast scrolling and to display status line.