On Sun, 29 Oct 2000, Stefan Seefeld wrote:
> "Jon M. Taylor" wrote:
> >
> > I just committed a bunch of GGIMesa fixes to the Mesa CVS tree. It
> > _should_ all build just fine again, but I have weird libtool and autoconf
> > incompatibilities popping up which are preventing the final library
> > install so I can't test it over here. If someone else could test it for
> > me, that would be cool. Brian, I still have to merge those config file
> > patches you sent me - some of that stuff isn't strictly correct.
>
> big kudos to Jon ! Great to hear that MesaGGI isn't dead. What do these changes
> provide ?
Just fixes to bring the GGIMesa sources up to speed with the Mesa
internal API changes.
> Do they solve the sticky double buffer issue we were discussing last
> year ?
Not yet. I need to merge the config file fixes that Brian Paul
sent me, and then I'll tackle that one. That, and getting LibGGI to link
properly with Mesa. All the libtool games that both packages are playing
have started to interfere with each other....
> Is there any openGL level acceleration provided for GGIMesa targets ?
Not yet. Well, there is the same flat-shaded span acceleration
via DrawHLine() that LibXMI uses in the stubs code, but that's pretty
minimal. I'll try to whip up a minimal DrawTriangle-accelerated Matrox
sub-target for the fbdev target as an example - I have a G200 at home.
> How precisely
> do Mesa and GGI interact ?
Mesa has a set of internal device driver API function hooks, quite
similar to GGI's target system. GGIMesa will thus act quite similarly to
any other GGI extension.
Jon
---
'Cloning and the reprogramming of DNA is the first serious step in
becoming one with God.'
- Scientist G. Richard Seed
