[Dri-devel] FYI: savage vast_speed_improvement
Just checked out mesa/dri cvs and build the whole tree. And glxgears got from prior 400 to 490 fps on my t23 (1,1 ghz p3 mobile, supersavage). thats nearly 25 % faster ! good work --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] freedesktop cvs /tmp no space
it seems the freedesktop cvs machine is running out of space on /tmp : [EMAIL PROTECTED] mesa]# ./up.bat Logging in to :pserver:[EMAIL PROTECTED]:2401/cvs/mesa CVS password: can't create temporary directory /tmp/cvs-serv27957 No space left on device same on dri trunk. No problems with my /tmp ... so. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Fw: Re: [Dri-devel] savage-2-0-0 test notes
Begin forwarded message: Date: Fri, 27 Feb 2004 11:59:22 -0600 From: Steve Holland [EMAIL PROTECTED] To: Felix Khling [EMAIL PROTECTED] Subject: Re: [Dri-devel] savage-2-0-0 test notes I tested it with a fresh copy from the trunk (effective tuesday), and have the same problems. Here are some PNG's of the results from drawpix: 16 bit display, drawing to back buffer: http://69.5.151.193/~sdh4/drawpix16bit.png drawing to front buffer: http://69.5.151.193/~sdh4/drawpix16bitfrontbuffer.png 24 bit display drawing to back buffer: http://69.5.151.193/~sdh4/drawpix24bit.png (24 bit display drawing to front buffer was similar to 16-front buffer) I also noticed problems when switching video modes on a 24 bit display. For example, running tuxracer would get the display parameters wrong, leading to an incomprehensible display (even after quitting). Thanks, Steve The code i'm running is also about 2-3 days old. I've got the same Hardware (T23 - supersavage IX/SDR). What he means with corruption occurs when changing the display mode on-the-fly. Then the screen is corrupted. Switching back to the old resolution normalizes the screen again. This won't happen when starting initialy with the new setting. So setting XF86Config to a new res and restart X everything is fine. Acceleration stuff : -only works in 16 bpp (2d/3d) -in 24bpp there is no 2d nor any 3d accelleration. -2D accell worked with tims driver on 24bpp. Tuxracer is still fine. But blender didn't change. The screen is clean but all fonts are corrupted. It seems to me that the fonts in blender are also gl, but that's just an assumption. Besides that you did a _GREAT_ work, and the driver speeded up in the last 2-3 Months as gar as i can see. With savage-2-0-0 i had about 270 fps in the beginning of working dri-support for my chip. Than it got from 325 to 378. And with the last code in the savage branch it reached 408. That stayed with the HEAD Branch since then. regards marco --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] savage success report
hi. just checked out the most recent savage_2.0.0 branch. enabled dri and working ;) xv working, consoles scrambled. chromium looking good, tuxracer is somehow a bit choppy and not playable, but accelerated. all gl screensavers work. ;) on t23 , supersavage IX/SDR marco --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] supersavage IX / SDR - cvs
Hello. drm loads cleanly, finds card, inits. driver recognizes drm cleanly. xvideo is broken, no 2d acceleration at all. Speed is equal to vesa driver. glplanet exits with invalid texture size. glxgears locks up X (sometime). In any case there is nothing to see in 3d ;) After trying 3d stuff and restarting X, X is unusable. Even after warm boot of the machine X is not usable. When starting the login manager it takes about 3 minutes to get the picture completed. A shutdown/turnoff/restart solves the problem. regards marco --- 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
[Dri-devel] kernel 2.6.1 - supersavage
ok, changed the code and recompiled the source. Now the drm module recognizes the card and inits it. /dev/dri/card0 is present even though not accessable by any user besides root. (flags are ok and i also have a proper DRI Section in config...) glxinfo reports dri is enabled. no gl stuff works. glxgears shows nothing. in X log : this is the card : (II) SAVAGE(0): VESA VBE OEM Vendor: S3 Incorporated. (II) SAVAGE(0): VESA VBE OEM Product: VBE 2.0 (II) SAVAGE(0): VESA VBE OEM Product Rev: Rev 1.0 (--) SAVAGE(0): Chip: id 8c2e, SuperSavage/PM64IXC_SDR (--) SAVAGE(0): Engine: SuperSavage (--) SAVAGE(0): mapping MMIO @ 0xc010 with size 0x8 (II) SAVAGE(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (--) S3:support device 15. (--) S3:tv size 0x0. this is drm stuff : (--) SAVAGE(0): mapping framebuffer @ 0xe800 with size 0x100 (==) SAVAGE(0): Write-combining range (0xe800,0x100) (II) SAVAGE(0): Splitting WC range: base: 0xe400, size: 0x500 (==) SAVAGE(0): Write-combining range (0xe800,0x100) (==) SAVAGE(0): Write-combining range (0xe400,0x500) (II) SAVAGE(0): map aperture:0x41301000 (--) SAVAGE(0): SavageMatchBiosMode:chose mode 13e at 75Hz. (II) SavageSetVESAMode:mode=0x13e,refresh=75HZ (II) SAVAGE(0): [drm] bpp: 32 depth: 24 (II) SAVAGE(0): [drm] Sarea 2200+872: 3072 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: Searching for BusID pci::01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenByBusid: drmOpenMinor returns 7 drmOpenByBusid: drmGetBusid reports pci::01:00.0 (II) SAVAGE(0): [drm] DRM interface version 1.1 (II) SAVAGE(0): [drm] created savage driver at busid pci::01:00.0 (II) SAVAGE(0): [drm] added 8192 byte SAREA at 0xe08d9000 (II) SAVAGE(0): [drm] mapped SAREA 0xe08d9000 to 0x46301000 (II) SAVAGE(0): [drm] framebuffer handle = 0xe800 (II) SAVAGE(0): [drm] added 1 reserved context for kernel (II) SAVAGE(0): [agp] Mode 0x1f000217 [AGP 0x8086/0x3575; Card 0x5333/0x8c2e] (II) SAVAGE(0): [agp] 16384 kB allocated with handle 0x0001 (II) SAVAGE(0): [agp] agpTextures microcode handle = 0xd000 (II) SAVAGE(0): [agp] agpTextures mapped at 0x (II) SAVAGE(0): [drm] aperture handle = 0xe400 (II) SAVAGE(0): [drm] Status handle = 0xe08f4000 (II) SAVAGE(0): [agp] Status page mapped at 0x46303000 (II) SAVAGE(0): [dri] visual configs initialized (**) SAVAGE(0): DRI is enabled (II) SAVAGE(0): virtualX:1400,virtualY:1050 (II) SAVAGE(0): bpp:32,tiledwidthBytes:5632,tiledBufferSize:5947392 (II) SAVAGE(0): bpp:32,widthBytes:5632,BufferSize:5914624 (II) SAVAGE(0): videoRambytes:0x0100 (II) SAVAGE(0): textureSize:0xffce3000 (II) SAVAGE(0): textureSize:0x (II) SAVAGE(0): textureOffset:0x00fdf000 (II) SAVAGE(0): depthOffset:0x00a33000,depthPicth:5632 (II) SAVAGE(0): backOffset:0x00487000,backPicth:5632 (EE) SAVAGE(0): Memory manager initialization to (0,0) (1408,-1) failed (==) SAVAGE(0): Backing store disabled (**) Option dpms (**) SAVAGE(0): DPMS enabled (II) SAVAGE(0): X context handle = 0x0001 (II) SAVAGE(0): [drm] installed DRM signal handler (II) SAVAGE(0): [DRI] installation complete (II) SAVAGE(0): [junkers]pSAVAGEDRIServer: [LOTS OF STUFF DELETED] (II) SAVAGE(0): [junkers] BCIcmdBuf:map:0x0001 (II) SAVAGE(0): [junkers] status:handle:0xe08f4000 (II) SAVAGE(0): [junkers] status:offset:0x (II) SAVAGE(0): [junkers] status:size:0x2000 (II) SAVAGE(0): [junkers] status:map:0x (II) SAVAGE(0): [junkers] sarea_priv_offset:0x0898 (II) SAVAGE(0): Direct rendering enabled (--) SAVAGEInitMC: There is no enough memory! (**) SAVAGE(0): XvMC is not enabled (WW) SAVAGE(0): Option ForceInit is not used (==) RandR enabled -- snip. see the not enough memory error... Hope this helps... ;) regards Marco --- 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
[Dri-devel] supersavage-kernel 2.6.1
Hi. I managed to get everything compiled cleanly. Hardware is t23/ S3 Supersavage / 1400x1050 Kernel Module loads cleanly. but xfree writes in log : snip II) SAVAGE(0): map aperture:0x41301000 (--) SAVAGE(0): SavageMatchBiosMode:chose mode 13e at 75Hz. (II) SavageSetVESAMode:mode=0x13e,refresh=75HZ (EE) SAVAGE(0): DRI isn't enabled (II) SAVAGE(0): Using 998 lines for offscreen memory. (II) SAVAGE(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles [DELETED] (==) SAVAGE(0): Backing store disabled (**) Option dpms (**) SAVAGE(0): DPMS enabled (EE) SAVAGE(0): Direct rendering disabled (WW) SAVAGE(0): Option ForceInit is not used (==) RandR enabled snip-- Also the consoles on ctrl+alt+Fx are not useable any more. I tried the Forceinit option , but doesn't recognizes it any more. I'm so close ;) Help would be appreciated. regards Marco --- 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
