Jon M. Taylor wrote:
> On Tue, 16 May 2000, Stefan Seefeld wrote:
>
> > Marcus Sundberg wrote:
> >
> > Interesting. My concern is, as I already said, with the hacked double
> > buffer in GGIMesa. We tried to run berlin on /dev/fb on a conference in
> > November and it turned out that Jon had set the second pointer to point
> > to the same memory as the first, i.e. circumventing double buffering
> > without the client's notice.
>
> I've been wanting to fix this, but I lost my CVS privs when Mesa
> CVS moved to SourceForge and I can't seem to get hold of anyone over
> there. Also the current CVS doesn't link properly, so I can't even
> produce patches |-/. Sorry guys, maybe you should consider switching to
> Marcus' GGIGL extension for a while. It sounds like it might be a better
> solution for you in the short term than GGIMesa, which I really don't have
> time to work on seriously now anyway.
>
> > Since the next conference is approaching rapidly (Stuttgart, end of June)
> > I'd really like to be able to run berlin without X, first, because
> > this is what berlin is intended for and second, because it will (hopefully)
> > be much faster due to the avoided crossblitting.
>
> ? What crossblitting? What do you mean? There _was_
> crossblitting with Uwe's old GGIMesa doublebuffer scheme - render into the
> backbuffer visual, crossblit it to the frontbuffer visual every SYNC.
> Slow as hell and prohibits hardware acceleration from being used, which is
> why I took it out.
>
A few weeks ago I downloaded the Mesa-3.1 - sources and eventually succeeded in
getting FlightGear running without X. It flickers awfully !
I had a closer look in the GGIMesa - sources and there _is_ still crossblitting
implemented !
Martin.
