From: Rick H. <ric...@mi...> - 2004-01-04 09:38:15
|
Hi all, Am wondering what stage DRI support for the S3 Savage IX/MV cards is at (if any). Is there any work being currently done on the 3D driver for this card ? Regards, Rick |
From: Felix <fx...@gm...> - 2004-01-04 16:33:29
|
On Sun, 04 Jan 2004 20:08:12 +1030 Rick Harris <ric...@mi...> wrote: > Hi all, > > Am wondering what stage DRI support for the S3 Savage IX/MV cards is at > (if any). > > Is there any work being currently done on the 3D driver for this card ? Alex Deucher and I will start working on Savage IX/MV cards soon. Alex ordered some Savage 4 and Savage IX cards so that we have something to play with. In the mean time you may want to take a look at utah-glx.sf.net. > > Regards, > Rick > Stay tuned 8-) Felix ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, Kühling (_____\Ä/____/ /_____/ /________) just not everything fx...@gm... \___/ \___/ U at the same time. |
From: Alex D. <ag...@ya...> - 2004-01-07 19:53:50
|
Felix, I'm having trouble getting the savage DRM to build. Perhaps my kernel is too old. As I recall remap_page_range() changed. perhaps that's the problem. any idea how I can get it working with my current kernel? I'm having trouble getting 2.4.24 working properly for my set up. Alex gcc -I/data/savage/xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel -D__KERNEL__ -I/usr/src/linux-2.4.20-8/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DMODVERSIONS -include /usr/src/linux-2.4.20-8/include/linux/modversions.h -DREMAP_PAGE_RANGE_5_ARGS -nostdinc -iwithprefix include -DKBUILD_BASENAME=savage_drv -c -o savage_drv.o savage_drv.c savage_drv.c: In function `savage_alloc_continuous_mem': savage_drv.c:83: warning: int format, long unsigned int arg (arg 2) savage_drv.c:106: warning: passing arg 1 of `remap_page_range' makes pointer from integer without a cast savage_drv.c:106: incompatible type for argument 4 of `remap_page_range' savage_drv.c:106: too few arguments to function `remap_page_range' savage_drv.c: In function `savage_get_physics_address': savage_drv.c:170: warning: implicit declaration of function `pte_offset' savage_drv.c:170: warning: assignment makes pointer from integer without a cast make[2]: *** [savage_drv.o] Error 1 make[2]: Leaving directory `/data/savage/xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel' make[1]: *** [_mod_/data/savage/xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.20-8' make: *** [modules] Error 2 __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: Felix <fx...@gm...> - 2004-01-07 21:16:59
|
2.4.24 is probably rather too new than too old. I compiled the DRM successfully on 2.4.21. See the workaround that I added for 2.6 kernels. It disables the driver-specific ioctls completely as I didn't want to bother figuring out a real solution at that time, knowing that the DRM driver would be completely rewritten sooner or later anyway. The driver has only three driver ioctls and they are only used for PCI cards. Felix On Wed, 7 Jan 2004 11:53:49 -0800 (PST) Alex Deucher <ag...@ya...> wrote: > Felix, I'm having trouble getting the savage DRM to build. Perhaps my > kernel is too old. As I recall remap_page_range() changed. perhaps > that's the problem. any idea how I can get it working with my current > kernel? I'm having trouble getting 2.4.24 working properly for my set > up. >=20 > Alex >=20 > gcc > -I/data/savage/xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/ker= nel > -D__KERNEL__ -I/usr/src/linux-2.4.20-8/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common > -fomit-frame-pointer -pipe -mpreferred-stack-boundary=3D2 -march=3Di686 > -DMODULE -DMODVERSIONS -include > /usr/src/linux-2.4.20-8/include/linux/modversions.h > -DREMAP_PAGE_RANGE_5_ARGS -nostdinc -iwithprefix include > -DKBUILD_BASENAME=3Dsavage_drv -c -o savage_drv.o savage_drv.c > savage_drv.c: In function `savage_alloc_continuous_mem': > savage_drv.c:83: warning: int format, long unsigned int arg (arg 2) > savage_drv.c:106: warning: passing arg 1 of `remap_page_range' makes > pointer from integer without a cast > savage_drv.c:106: incompatible type for argument 4 of > `remap_page_range' > savage_drv.c:106: too few arguments to function `remap_page_range' > savage_drv.c: In function `savage_get_physics_address': > savage_drv.c:170: warning: implicit declaration of function > `pte_offset' > savage_drv.c:170: warning: assignment makes pointer from integer > without a cast > make[2]: *** [savage_drv.o] Error 1 > make[2]: Leaving directory > `/data/savage/xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kern= el' > make[1]: *** > [_mod_/data/savage/xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm= /kernel] > Error 2 > make[1]: Leaving directory `/usr/src/linux-2.4.20-8' > make: *** [modules] Error 2 >=20 >=20 > __________________________________ > Do you Yahoo!? > Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes > http://hotjobs.sweepstakes.yahoo.com/signingbonus ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, K=FChling (_____\=C4/____/ /_____/ /________) just not everything fx...@gm... \___/ \___/ U at the same time. |
From: Alex D. <ag...@ya...> - 2004-01-07 22:56:24
|
just as a follow up, I got the DRM to build under 2.4.24, (redhat uses 2.6 MM in rh9). Unfortunately, I can't get pcmcia to work for me in 2.4.24, so I can either hack on the savage driver or have network access, depending on which kernel I boot. I need to get that sorted out. anyone hear of any problems with rh9 and pcmcia with vanilla kernels? I tested the driver on my savage4 and I see the 2D corruption maximo was talking about with tile mode enabled. everything is fine with tilemode disabled. However, 3D doesn't seem to work in either mode. With or without tilemode disabled I get random black and white moving rectangles in the glxgears window. Also 3D only seems to work at 16 bpp. at 24 bpp, the drm complains about dma (I forget the exact message; something about savage_dma.c). I also gave it a try on my savage IX based card. Opening the drm fails so direct rendering is never enabled. Also I'm going to need to re-add the "crtonly" option (from tim's driver) since these cards seem to think there is a 640x480 flatpanel attached, so modes are limited to 640x480. Alex --- Felix Kühling <fx...@gm...> wrote: > 2.4.24 is probably rather too new than too old. I compiled the DRM > successfully on 2.4.21. See the workaround that I added for 2.6 > kernels. > It disables the driver-specific ioctls completely as I didn't want to > bother figuring out a real solution at that time, knowing that the > DRM > driver would be completely rewritten sooner or later anyway. The > driver > has only three driver ioctls and they are only used for PCI cards. > > Felix > > On Wed, 7 Jan 2004 11:53:49 -0800 (PST) > Alex Deucher <ag...@ya...> wrote: > > > Felix, I'm having trouble getting the savage DRM to build. Perhaps > my > > kernel is too old. As I recall remap_page_range() changed. > perhaps > > that's the problem. any idea how I can get it working with my > current > > kernel? I'm having trouble getting 2.4.24 working properly for my > set > > up. > > > > Alex > > > > gcc > > > -I/data/savage/xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel > > -D__KERNEL__ -I/usr/src/linux-2.4.20-8/include -Wall > > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing > -fno-common > > -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 > > -DMODULE -DMODVERSIONS -include > > /usr/src/linux-2.4.20-8/include/linux/modversions.h > > -DREMAP_PAGE_RANGE_5_ARGS -nostdinc -iwithprefix include > > -DKBUILD_BASENAME=savage_drv -c -o savage_drv.o savage_drv.c > > savage_drv.c: In function `savage_alloc_continuous_mem': > > savage_drv.c:83: warning: int format, long unsigned int arg (arg 2) > > savage_drv.c:106: warning: passing arg 1 of `remap_page_range' > makes > > pointer from integer without a cast > > savage_drv.c:106: incompatible type for argument 4 of > > `remap_page_range' > > savage_drv.c:106: too few arguments to function `remap_page_range' > > savage_drv.c: In function `savage_get_physics_address': > > savage_drv.c:170: warning: implicit declaration of function > > `pte_offset' > > savage_drv.c:170: warning: assignment makes pointer from integer > > without a cast > > make[2]: *** [savage_drv.o] Error 1 > > make[2]: Leaving directory > > > `/data/savage/xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel' > > make[1]: *** > > > [_mod_/data/savage/xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel] > > Error 2 > > make[1]: Leaving directory `/usr/src/linux-2.4.20-8' > > make: *** [modules] Error 2 > > > > > __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: Rafael M. <ma...@gl...> - 2004-01-08 11:54:05
|
At 07:56 PM 7/1/2004, Alex Deucher wrote: >I tested the driver on my savage4 and I see the 2D corruption maximo >was talking about with tile mode enabled. everything is fine with >tilemode disabled. However, 3D doesn't seem to work in either mode. >With or without tilemode disabled I get random black and white moving >rectangles in the glxgears window. Also 3D only seems to work at 16 >bpp. at 24 bpp, the drm complains about dma (I forget the exact >message; something about savage_dma.c). > Alex, I got the same problem with randon black and white and Felix suggested to=20 edit xc/programs/Xserver/hw/xfree86/drivers/savage/savage_bci.h because=20 there are some conditionals #if SAVAGE4 ... #endif and after "#define SAVAGE4 1" it got better and 3D worked with title mode=20 but the 2D was still corrupted. bye. Rafael M=E1ximo=20 |
From: Felix <fx...@gm...> - 2004-01-08 16:50:13
|
On Wed, 7 Jan 2004 14:56:24 -0800 (PST) Alex Deucher <ag...@ya...> wrote: > just as a follow up, I got the DRM to build under 2.4.24, (redhat uses > 2.6 MM in rh9). Unfortunately, I can't get pcmcia to work for me in > 2.4.24, so I can either hack on the savage driver or have network > access, depending on which kernel I boot. I need to get that sorted > out. anyone hear of any problems with rh9 and pcmcia with vanilla > kernels? >=20 > I tested the driver on my savage4 and I see the 2D corruption maximo > was talking about with tile mode enabled. everything is fine with > tilemode disabled. However, 3D doesn't seem to work in either mode.=20 > With or without tilemode disabled I get random black and white moving > rectangles in the glxgears window. Also 3D only seems to work at 16 > bpp. at 24 bpp, the drm complains about dma (I forget the exact > message; something about savage_dma.c). >=20 > I also gave it a try on my savage IX based card. Opening the drm fails > so direct rendering is never enabled. Also I'm going to need to re-add > the "crtonly" option (from tim's driver) since these cards seem to > think there is a 640x480 flatpanel attached, so modes are limited to > 640x480. To enable DRI on Savage IX you'll have to add the PCI IDs in two places. One is in SavageSreenInit in savage_driver.c, the other is DRIVER_PCI_IDS in the savage.h in the kernel module. >=20 > Alex >=20 ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, K=FChling (_____\=C4/____/ /_____/ /________) just not everything fx...@gm... \___/ \___/ U at the same time. |
From: Alex D. <ag...@ya...> - 2004-01-08 17:09:25
|
--- Felix Kühling <fx...@gm...> wrote: > On Wed, 7 Jan 2004 14:56:24 -0800 (PST) > Alex Deucher <ag...@ya...> wrote: > > > just as a follow up, I got the DRM to build under 2.4.24, (redhat > uses > > 2.6 MM in rh9). Unfortunately, I can't get pcmcia to work for me > in > > 2.4.24, so I can either hack on the savage driver or have network > > access, depending on which kernel I boot. I need to get that > sorted > > out. anyone hear of any problems with rh9 and pcmcia with vanilla > > kernels? > > > > I tested the driver on my savage4 and I see the 2D corruption > maximo > > was talking about with tile mode enabled. everything is fine with > > tilemode disabled. However, 3D doesn't seem to work in either > mode. > > With or without tilemode disabled I get random black and white > moving > > rectangles in the glxgears window. Also 3D only seems to work at > 16 > > bpp. at 24 bpp, the drm complains about dma (I forget the exact > > message; something about savage_dma.c). > > > > I also gave it a try on my savage IX based card. Opening the drm > fails > > so direct rendering is never enabled. Also I'm going to need to > re-add > > the "crtonly" option (from tim's driver) since these cards seem to > > think there is a 640x480 flatpanel attached, so modes are limited > to > > 640x480. > > To enable DRI on Savage IX you'll have to add the PCI IDs in two > places. > One is in SavageSreenInit in savage_driver.c, the other is > DRIVER_PCI_IDS in the savage.h in the kernel module. That's what I figured, I just hadn't gotten a chance to look at the DRM too much. thanks for the tip. Also, FWIW, I sort of have "crtonly" working. The driver claims to be programming the right mode, and the desktop is 1024x768, 800x600, etc., but the mode on the monitor still ends up being 640x480x60hz. at what's supposed to be 1024x768 the frame doesn't move, when you adjust to 800x600 or 640x480, the frame moves around as it should, but the actual mode never changes, so it appears the driver thinks it's in 1024x768, but it's not. I also tried with Tim's driver, but had even less luck there. Alex __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: Alex D. <ag...@ya...> - 2004-01-08 23:40:56
|
well, I managed to fix the 2D corruption in tile mode on savage4. the problem is that the bits of the GBD (MM816C) have different meaning on savage4 vs. twister/prosavage. The fix is to use the SavageEnableMode_M7() function for savage4 rather than SavageEnableMode_Twister(). This also negates the need to define SAVAGE4 in savage_bci.h since SavageEnableMode_M7() already uses 8 for BCI_ENABLE. alternatively you can edit the SavageEnableMode_Twister() to use the proper values, but the results are the same (and you don't break twister/prosavage). with tiling mode fixed, 3D behaves similarly to linear mode. the 3D app runs, but is scrambled somewhat. I'm not sure where the fix for that lies, probably on the 3D side. Also, with regard to VT switches, I haven't seen any lockups. Alex __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: Felix <fx...@gm...> - 2004-01-09 13:47:19
|
On Thu, 8 Jan 2004 15:40:55 -0800 (PST) Alex Deucher <ag...@ya...> wrote: > well, I managed to fix the 2D corruption in tile mode on savage4. the > problem is that the bits of the GBD (MM816C) have different meaning on > savage4 vs. twister/prosavage. The fix is to use the > SavageEnableMode_M7() function for savage4 rather than > SavageEnableMode_Twister(). This also negates the need to define > SAVAGE4 in savage_bci.h since SavageEnableMode_M7() already uses 8 for > BCI_ENABLE. > alternatively you can edit the SavageEnableMode_Twister() to use the > proper values, but the results are the same (and you don't break > twister/prosavage). I don't understand. How would using SavageEnableMode_M7 for Savage4 break ProSavage? >=20 > with tiling mode fixed, 3D behaves similarly to linear mode. the 3D > app runs, but is scrambled somewhat. I'm not sure where the fix for > that lies, probably on the 3D side. Are you sure that tiled mode is enabled correctly? I think Rafael reported earlier that 3D (glxgears) worked ok for him with tiled mode enabled, even though 2D was garbled. >=20 > Also, with regard to VT switches, I haven't seen any lockups. Then it's probably something specific to ProSavage. :-( >=20 > Alex >=20 ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, K=FChling (_____\=C4/____/ /_____/ /________) just not everything fx...@gm... \___/ \___/ U at the same time. |
From: Rafael M. <ma...@gl...> - 2004-01-09 14:50:00
|
At 10:46 AM 9/1/2004, Felix K=FChling wrote: >Are you sure that tiled mode is enabled correctly? I think Rafael >reported earlier that 3D (glxgears) worked ok for him with tiled mode >enabled, even though 2D was garbled. Yes, that's correct but after editing savage_bci.h and defining "SAVAGE4 1" bye. Rafael M=E1ximo=20 |
From: Alex D. <ag...@ya...> - 2004-01-09 16:12:07
|
savage4 uses 8 for bci enable while it's 0 on prosavage. that's why you have to define SAVAGE4 to make it work. the enablemode_m7() function uses 8 arlready. the BD's and BCI seems to work differently on savage4 vs. prosavage. Also FWIW, I tried both with and without the cob enabled and it doesn't seem to make a difference (there are several comments in the code that the cob is busted on savage4 and prosavage). Alex --- Rafael Maximo <ma...@gl...> wrote: > At 10:46 AM 9/1/2004, Felix Kühling wrote: > > >Are you sure that tiled mode is enabled correctly? I think Rafael > >reported earlier that 3D (glxgears) worked ok for him with tiled > mode > >enabled, even though 2D was garbled. > > Yes, that's correct but after editing savage_bci.h and defining > "SAVAGE4 1" > > bye. > > > Rafael Máximo > > > > ------------------------------------------------------- > 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 > Dri...@li... > https://lists.sourceforge.net/lists/listinfo/dri-devel __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: Alex D. <ag...@ya...> - 2004-01-09 16:04:48
|
--- Felix Kühling <fx...@gm...> wrote: > On Thu, 8 Jan 2004 15:40:55 -0800 (PST) > Alex Deucher <ag...@ya...> wrote: > > > well, I managed to fix the 2D corruption in tile mode on savage4. > the > > problem is that the bits of the GBD (MM816C) have different meaning > on > > savage4 vs. twister/prosavage. The fix is to use the > > SavageEnableMode_M7() function for savage4 rather than > > SavageEnableMode_Twister(). This also negates the need to define > > SAVAGE4 in savage_bci.h since SavageEnableMode_M7() already uses 8 > for > > BCI_ENABLE. > > alternatively you can edit the SavageEnableMode_Twister() to use > the > > proper values, but the results are the same (and you don't break > > twister/prosavage). > > I don't understand. How would using SavageEnableMode_M7 for Savage4 > break ProSavage? It wouldn't. what I was trying to say is that "fixing" SavageEnableMode_Twister() would break prosavage. Obviously you could add some "if(savage4)" stuff, but it's cleaner just using the m7 function. > > > > > with tiling mode fixed, 3D behaves similarly to linear mode. the > 3D > > app runs, but is scrambled somewhat. I'm not sure where the fix > for > > that lies, probably on the 3D side. > > Are you sure that tiled mode is enabled correctly? I think Rafael > reported earlier that 3D (glxgears) worked ok for him with tiled mode > enabled, even though 2D was garbled. > yes, I'm seeing the same behavior. glxgears works with tiling on, but then 2D doesn't. if I fix 2D tiled mode, 3D gets scrambled. I think the problem lies in savage_dri.c I think there is a disconnect on how the different bitmap descriptors and tiling registers are set up. The GBD (global bitmap descriptor) and tiling reg 0 are used for the 2D engine. the PBD (primary bitmap descriptor) and tiling regs 0-2 are used for the front/back/depth buffers. I'm not sure exactly how they all need to be set up to work properly. I'll be playing with that today. The problem with the code is that there is no consistency with it. they define mneumonics, but never stick to them. The comment and SAVAGE4, etc. mneumonics at the top of savage_bci.h describe the behavior of the bitmap descriptors. If they had used the mneumonics in the EnableMode() functions in savage_driver.c tiling would have worked off the bat on savage4. On prosavage bits 25-24 select tile format: linear, tile, texture or destination. on savage4 those bits are different: they are linear, 16bit tiles, or 32 bit tiles. SavageEnableMode_Twister() sets the tile format (bits 25-24) to 1 which is tile mode on prosavage, but is nothing on savage4. savage4 needs to be set to 2 (16bpp) or 3 (32 bpp). setting that properly clears the corruption for 2D. I suspect the 3D needs to be restructured to work that way as well. the reason 3d works when 2D doesn't is because all the bitmap descriptors are probably set up the same (for prosavage). I suspect fixing the setup of the the bitmap descriptors and tiling regs in savage_dri.c will fix 3d. they might also be changes need in the DRI as well, I haven't really looked at it much yet. then again I could be wrong... > > > > Also, with regard to VT switches, I haven't seen any lockups. > > Then it's probably something specific to ProSavage. :-( > > > > > Alex > > > > ------------ __\|/__ ___ ___ > ------------------------- > Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, > Kühling (_____\Ä/____/ /_____/ /________) just not everything > fx...@gm... \___/ \___/ U at the same time. __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: Alex D. <ag...@ya...> - 2004-01-09 17:30:53
|
FYI, I just got 3D and 2D working on savage4. the PBD setup was wrong in savage_dri.c. I'll be posting a patch soon. Also, what bpp should depth buffer be? the same as the framebuffer? Alex --- Felix Kühling <fx...@gm...> wrote: > On Thu, 8 Jan 2004 15:40:55 -0800 (PST) > Alex Deucher <ag...@ya...> wrote: > > > well, I managed to fix the 2D corruption in tile mode on savage4. > the > > problem is that the bits of the GBD (MM816C) have different meaning > on > > savage4 vs. twister/prosavage. The fix is to use the > > SavageEnableMode_M7() function for savage4 rather than > > SavageEnableMode_Twister(). This also negates the need to define > > SAVAGE4 in savage_bci.h since SavageEnableMode_M7() already uses 8 > for > > BCI_ENABLE. > > alternatively you can edit the SavageEnableMode_Twister() to use > the > > proper values, but the results are the same (and you don't break > > twister/prosavage). > > I don't understand. How would using SavageEnableMode_M7 for Savage4 > break ProSavage? > > > > > with tiling mode fixed, 3D behaves similarly to linear mode. the > 3D > > app runs, but is scrambled somewhat. I'm not sure where the fix > for > > that lies, probably on the 3D side. > > Are you sure that tiled mode is enabled correctly? I think Rafael > reported earlier that 3D (glxgears) worked ok for him with tiled mode > enabled, even though 2D was garbled. > > > > > Also, with regard to VT switches, I haven't seen any lockups. > > Then it's probably something specific to ProSavage. :-( > > > > > Alex > > > > ------------ __\|/__ ___ ___ > ------------------------- > Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, > Kühling (_____\Ä/____/ /_____/ /________) just not everything > fx...@gm... \___/ \___/ U at the same time. __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |
From: Alex D. <ag...@ya...> - 2004-01-09 17:50:57
Attachments:
savage4.patch
|
The attached patch is a pretty raw. it will break prosavage and it needs a major clean up, but for those looking to run 3D on savage4 cards, have at it. glxgears works flawlessly (~570 fps). tuxracer and chromium BSU look a bit like someone ran an impressionist gimp filter on them and they also lock up with in about 30 seconds. Also 2d doesn't seem to work right with tilemode enabled and the dri disabled. it's also available here: http://www.botchco.com/alex/savage/savage4.patch Alex __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus |