Re: [Dri-devel] Re: More on TCL Testing...
Michael wrote: > > On Fri, Mar 01, 2002 at 05:42:38PM +, Keith Whitwell wrote: > > In the meantime I'me about to commit something rather nice: A dedicated > > Begin/End engine for the radeon tcl driver with dynamic code generation for > > commands like glVertex, glColor, etc. > > Looks good. > > Are you still in the process of doing this? If not, looks like you've > missed some files on the commit (there's no Driver.NotifyBegin) > OK. There's stuff from extras/Mesa I'll commit now. Keith ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: More on TCL Testing...
On Fri, Mar 01, 2002 at 05:42:38PM +, Keith Whitwell wrote: > In the meantime I'me about to commit something rather nice: A dedicated > Begin/End engine for the radeon tcl driver with dynamic code generation for > commands like glVertex, glColor, etc. Looks good. Are you still in the process of doing this? If not, looks like you've missed some files on the commit (there's no Driver.NotifyBegin) -- Michael. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: More on TCL Testing...
Michael wrote: > > On Mon, Feb 25, 2002 at 05:53:51PM -0500, Adam K Kirchhoff wrote: > > > > On Mon, 25 Feb 2002, Keith Whitwell wrote: > > > > > > > > OK, great - it looks like some things work for you... That's an improvement, > > > anyway... > > > > > > What would be helpful would be to look at Mesa/samples, and identify what in > > > there works & doesn't work. Start with 'depth', 'prim', 'stars', 'tri'. > > > > > > Similarly for the Mesa/demos directory. > > > > > > > I'm breaking them into either "works" or "doesn't work". I'm skipping the > > ones that need unsupported extensions. If you'd like more detail on any > > (or all) of them, just let me know. > > > > Here's the rundown on the Mesa/samples... > > > > accum -- works > > bitmap1 -- works > > bitmap2 -- works > ... etc > > Could be a red herring, but pretty much the output of grep -l DEPTH_TEST > ~/Mesa/samples/*.c == 'doesn't work' in your list. > I'd really been scratching my head about that one. I'll look into this. In the meantime I'me about to commit something rather nice: A dedicated Begin/End engine for the radeon tcl driver with dynamic code generation for commands like glVertex, glColor, etc. This has significantly improved scores on some of the viewperf tests, and once it's better integrated, should do so for most of them. Keith ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: More on TCL Testing...
On Mon, Feb 25, 2002 at 05:53:51PM -0500, Adam K Kirchhoff wrote: > > On Mon, 25 Feb 2002, Keith Whitwell wrote: > > > > > OK, great - it looks like some things work for you... That's an improvement, > > anyway... > > > > What would be helpful would be to look at Mesa/samples, and identify what in > > there works & doesn't work. Start with 'depth', 'prim', 'stars', 'tri'. > > > > Similarly for the Mesa/demos directory. > > > > I'm breaking them into either "works" or "doesn't work". I'm skipping the > ones that need unsupported extensions. If you'd like more detail on any > (or all) of them, just let me know. > > Here's the rundown on the Mesa/samples... > > accum -- works > bitmap1 -- works > bitmap2 -- works ... etc Could be a red herring, but pretty much the output of grep -l DEPTH_TEST ~/Mesa/samples/*.c == 'doesn't work' in your list. -- Michael. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: More on TCL Testing...
On Mon, 25 Feb 2002, Keith Whitwell wrote: > > OK, great - it looks like some things work for you... That's an improvement, > anyway... > > What would be helpful would be to look at Mesa/samples, and identify what in > there works & doesn't work. Start with 'depth', 'prim', 'stars', 'tri'. > > Similarly for the Mesa/demos directory. > I'm breaking them into either "works" or "doesn't work". I'm skipping the ones that need unsupported extensions. If you'd like more detail on any (or all) of them, just let me know. Here's the rundown on the Mesa/samples... accum -- works bitmap1 -- works bitmap2 -- works blendeq -- works blendxor -- works cursor -- works depth -- doesn't work eval -- doesn't work fog -- doesn't work font -- works line -- works logo -- doesn't work nurb -- works olympic -- works point -- works prim -- works quad -- doesn't work select -- works sphere -- doesn't work star -- works stencil -- works tri -- works wave -- doesn't work Mesa/demos bounce -- works clearspd -- works drawpix -- works fire -- doesn't work gears -- doesn't work geartrain -- doesn't work gloss -- doesn't work glutfx -- doesn't work ipers -- doesn't work isosurf -- doesn't work (even after switching to "reflect" as I mentioned earlier) morph3d -- doesn't work multiarb -- works pointblast -- doesn't work ray -- doesn't work readpix -- works reflect -- doesn't work renormal -- works spectex -- doesn't work stex3d -- doesn't work teapot -- doesn't work terrain -- doesn't work tessdemo -- works texcyl -- works texenv -- works texobj -- works tunnel -- works tunnel2 -- works (great demo, BTW!) winpos -- works ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: More on TCL Testing...
Adam K Kirchhoff wrote: > > For what it's worth, I did a little more testing with some games and GL > xscreensaver hacks. > > pulsar works great, as does cage and starwars. Atlantis just gives the > usual blue background. The others just seem to give a black box (except > for glplanet, which shows the stars). > > Tuxracer shows the background, but not the track itself, nor tux. > > Parsec shows lots of stars, and the weapons that come floating by. No > planets... > > heretic2 starts up, and loads a running game. However, that screen for > loading games stays up, even after it's loaded. I can quit easily enough > because the menus work fine. > > With SOF, the screen remains completely blank. OK, great - it looks like some things work for you... That's an improvement, anyway... What would be helpful would be to look at Mesa/samples, and identify what in there works & doesn't work. Start with 'depth', 'prim', 'stars', 'tri'. Similarly for the Mesa/demos directory. Keith ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: More on TCL Testing...
For what it's worth, I did a little more testing with some games and GL xscreensaver hacks. pulsar works great, as does cage and starwars. Atlantis just gives the usual blue background. The others just seem to give a black box (except for glplanet, which shows the stars). Tuxracer shows the background, but not the track itself, nor tux. Parsec shows lots of stars, and the weapons that come floating by. No planets... heretic2 starts up, and loads a running game. However, that screen for loading games stays up, even after it's loaded. I can quit easily enough because the menus work fine. With SOF, the screen remains completely blank. I can try some more if you think it'll help :-) Adam ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
