On Thu, 2 Nov 2000, [iso-8859-1] Niklas H�glund wrote:
> On Tue, Oct 31, 2000 at 01:59:37PM -0800, Jon M. Taylor wrote:
> > On Mon, 30 Oct 2000, beef wrote:
> >
> > > On Sat, 28 Oct 2000, Jon M. Taylor wrote:
> > > It kindof works, but flickers horribly on the fbdev.
> >
> > > what/where _could_ this doublebuffer problem be?
> >
> > So, I did a QuickHack(tm) to work around the problem - I pointed
> > both buffers to the ggi_visual |->. This let me render to either the
> > front or back buffer, mapped to either hardware or software
> > front/backbuffers, with or without hardware acceleration for both drawing
> > triangles and the page flips. As you have seen it also causes horrible
> > flickering. But it "worked" and at the time that was all I was interested
> > in. The hack was never meant to be more than a stopgap until I figured
> > out how to do it all properly. Unfortunately, there wasn't much in the
> > way of buffer management API cut-ins in Mesa at the time, so it turned out
> > to be more work than I had anticipated, and a few weeks later my Savage4
> > driver project got canned and I stopped working on GGIMesa except for the
> > occasional build fixes to keep up with the changing Mesa internals.
>
> At that time I found that using a main loop looking like this does sort of
> proper double-buffering using GGIMesa. Note that the SetMode call sets the
> virtual width to twice the physical width.
[snip]
Thanks for the input, but I'm afraid that the "pageflip using
SetOrigin" hack won't work on all targets. You _can_ allocate a
DirectBuffer or a memory_visual and use that as a backbuffer on every
target.
Jon
---
'Cloning and the reprogramming of DNA is the first serious step in
becoming one with God.'
- Scientist G. Richard Seed
