er... well, the bitmap descriptor speed up in my last email was a fluke... that code I changed never actually gets run, so the speed up was just a random fluke I guess.
What is SavageInitBuffers() in savage_dri.c supposed to do? all of its content is commented out. it seems to contain the actual code that writes to the front/depth/back descriptors (via SavageSelectBuffer()). uncommenting the code produces a big black rectangle in the lower right of the screen when 3D apps are run. I can't seem to find where the front/back/depth BitmapDesc and Offset are written to their respective regs. I thought thats what SavageSelectBuffer() did, but it never gets called, and yet the values seem to get there somehow... perhaps in the DRI driver? Anyway, I'm gonna commit what I have so far. Alex --- Felix Kühling <[EMAIL PROTECTED]> wrote: > I tested your patch on my ProSavage. It works and it speeds up > glxgears > by over 50fps. I was surprised to read numbers over 500fps on Savage4 > as > that's about what I'm getting with ProSavage too. It used to be about > 490, with your patch it's about 550 now. > > BTW, I just saw your other mail about the bitmap descriptors. I don't > know what exactly they are, but I can't wait to see that speedup > myself. > :) Nice work. > > Regards, > Felix > > On Fri, 9 Jan 2004 12:45:10 -0800 (PST) > Alex Deucher <[EMAIL PROTECTED]> wrote: > > > The attached patch is a cleaned up version of the one I made this > > morning. It enables DRI support for savage4 and shouldn't break > > prosavage or twister, however, I'd like someone with prosvage or > > twister to check it out before I commit it. > > Both tiled and linear framebuffer mode now work with 3D. I've made > > linear mode the default because it picks about about 30 fps in > glxgears > > and both modes seem to render the same is all apps I've tested. > > glxgears works, tuxracer works, but seems, like I said earlier, but > the > > opening screen looks odd (impressionist). once you start it, works > > pretty well, but about half way through a level, the textures stop > > rendering for everything accept ice. and I'm left with > > semi-transparent grey rectangles/triangles for the ground, trees, > and > > fish. I suspect savage4 may do texturing slightly differently than > > prosavage. tuxracer also no longer locks up. Chromium BSU starts > ok, > > but shows the same corruption as the tuxracer start screen, then > within > > 20-30 second is eats the X server, not a hard lock just the video > card. > > I can still switch to a different VT and reboot the computer. > > > > The patch also enables the "crtonly" option for disabling the lcd > on > > mobile chips. it sort of works... see my previous post for more > info > > on that. > > > > Alex > > > > __________________________________ > > Do you Yahoo!? > > Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes > > http://hotjobs.sweepstakes.yahoo.com/signingbonus > > > ------------ __\|/__ ___ ___ > ------------------------- > Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, > Kühling (_____\Ä/____/ /_____/ /________) just not everything > [EMAIL PROTECTED] \___/ \___/ U at the same time. __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
