On Sun, 23 Dec 2001, Andreas Reich wrote:
> >> isn't it funny - two germans talking english to each other. Heh. > > We always talk here in english, because that's an international ML. > > yes, sure. I still consider it funny though. :-) :-) > > GGI's functionality is always limited to the driver you're using. > > Double-Buffering means doubling the size of used onboard video memory for > > the video mode. Therefore, an appropriate boot setting is always required > > to make vesa doing what you want. > > OK, I looked at the Vesa docs and it seems to me that there is no way > to specify at boot time that the driver should use twice as much video > memory. > Is there any way to simulate double-buffering? I don't know. I've never used vesafb before. What you can do, really depends on vesafb. > I've read something about SetOrigin(). But AFAIK that requires > increasing the virtual screen size, which is, again, not possible > because of the vesa limitations. ggiSetOrigin() is used for panning on a virtual screen. For example, when you write a flipper game... :) > Is it a good solution to use DirectBuffer and memcpy()? When you use a PPC, then you shouldn't do that. Otherwise your programm crashs inside memcpy(). The reason is, that the PPC CPU uses a very special asm instruction, that caches the data in memory (or CPU cache?) instead writing the data back to the directbuffer. Then when the graphic card accesses its memory, then it reads the old data... > Or would that be too slow? No. It's ok for i386, but it's too fast for the PPC. :-) See above. > Thanks for your advice and merry christmas. 2U2! CU, Christoph Egger E-Mail: [EMAIL PROTECTED]
