[Dri-devel] Radeon 9000 patch

2002-10-29 Thread dri-devel . sourceforge
Hi

With an old binary snapshot (over a month old) I got my Radeon 9000 Pro card working 
with XFree86 including DRI support.  This was achieved by setting the ChipId in the 
XF86Config file to 0x4242.

I noticed that the latest drivers actually recognise the card (RV250_If), but that DRI 
is disabled, so I created the attached patch against CVS from 20021026.  This gets DRI 
working on my system using the r200 DRI driver.  It's not perfect, but it works.  
Thought you might like to apply the patch so others can have DRI on the Radeon 9000 
and 9700 cards.

Regards.

Scott Harrison.

diff -ru xc.orig/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c 
xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c
--- xc.orig/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.cWed Oct 23 
06:05:13 2002
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_dri.c Tue Oct 29 21:03:38 
+2002
@@ -1002,6 +1002,8 @@
 
 if (info->ChipFamily == CHIP_FAMILY_R200)
drmInfo.func = DRM_RADEON_INIT_R200_CP;
+else if (info->ChipFamily == CHIP_FAMILY_RV250)
+   drmInfo.func = DRM_RADEON_INIT_R200_CP;
 else
drmInfo.func = DRM_RADEON_INIT_CP;
 
@@ -1222,6 +1224,8 @@
 
 if (info->ChipFamily == CHIP_FAMILY_R200)
pDRIInfo->clientDriverName= R200_DRIVER_NAME;
+else if (info->ChipFamily == CHIP_FAMILY_RV250)
+   pDRIInfo->clientDriverName= RV250_DRIVER_NAME;
 else 
pDRIInfo->clientDriverName= RADEON_DRIVER_NAME;
 
@@ -1346,6 +1350,9 @@
int req_minor, req_patch;
 
if (info->ChipFamily == CHIP_FAMILY_R200) {
+   req_minor = 5;
+   req_patch = 0;  
+   } else if (info->ChipFamily == CHIP_FAMILY_RV250) {
req_minor = 5;
req_patch = 0;  
} else {
diff -ru xc.orig/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 
xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c
--- xc.orig/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c Sat Oct 26 
00:33:56 2002
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c  Tue Oct 29 21:04:29 
+2002
@@ -3450,12 +3450,6 @@
   (pScrn->displayWidth * pScrn->virtualY *
info->CurrentLayout.pixel_bytes * 3 + 1023) / 1024);
info->directRenderingEnabled = FALSE;
-   } else if (info->ChipFamily >= CHIP_FAMILY_RV250) {
-   /* Is this correct or do RV250's and M9's work? */
-   info->directRenderingEnabled = FALSE;
-   xf86DrvMsg(scrnIndex, X_WARNING,
-  "Direct rendering not yet supported on "
-  "Radeon 9000 and newer cards\n");
} else {
if (info->IsSecondary)
info->directRenderingEnabled = FALSE;
diff -ru xc.orig/programs/Xserver/hw/xfree86/drivers/ati/radeon_version.h 
xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_version.h
--- xc.orig/programs/Xserver/hw/xfree86/drivers/ati/radeon_version.hWed Oct 23 
00:38:43 2002
+++ xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_version.h Tue Oct 29 21:05:46 
+2002
@@ -27,6 +27,7 @@
 #define RADEON_NAME  "RADEON"
 #define RADEON_DRIVER_NAME   "radeon"
 #define R200_DRIVER_NAME "r200"
+#define RV250_DRIVER_NAME "r200"
 
 #define RADEON_VERSION_MAJOR 4
 #define RADEON_VERSION_MINOR 0



Re: [Dri-devel] Radeon 9000 Trials and Tribulations

2002-11-02 Thread dri-devel . sourceforge
Hi

I don't know much about 3D or the ATI graphics cards, but I can tell you how I got the 
DRI CVS to work with my ATI 9000 Pro card (ID 4966).

First I took the source to XFree86 4.2.0 compiled and installed, I then checked out 
the latest DRI source from CVS.  Applied my patch, then make World, make install.  I 
then had to do "chmod -R ugo+rX /usr/X11R6" to get the permissions right on the 
drivers.  Then in the DRI CVS tree I went into 
xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel did a "make -f 
Makefile.linux" and copied the radeon.o to /lib/modules/x.y.z/kernel/drivers/char/drm 
and ran "depmod -a".  I then installed agpgart kernel module followed by radeon, then 
started X.  Then when I run glxgears it works great.

To get the DRI permissions set right add the following to the bottom of your XF86 
Config file

Section "DRI"
   Mode 0666
EndSection

Problems:

I do have problems with the 3D support, as I said it is not perfect.  I use the 3D to 
run WarCraft III under Wine in opengl mode, I haven't tried any other programs.  The 
problems I get are, if I try to move the window in which Warcraft starts it will 
completely lock up the graphics card.  The only way of getting any picture back on the 
monitor is by rebooting.  Also some of the 3D objects don't always appear properly and 
can partially appear then disappear, I have also seen some flashing colors.  However, 
This isn't significant enough to make the game unplayable, in fact it is still very 
playable.

Scott Harrison

On Thu, Oct 31, 2002 at 01:18:02PM -0800, [EMAIL PROTECTED] 
wrote:
> Date: Thu, 31 Oct 2002 15:16:26 -0600 (CST)
> From: "D. Hageman" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Dri-devel] Radeon 9000 Trials and Tribulations
> 
>   This message is in MIME format.  The first part should be readable text,
>   while the remaining parts are likely unreadable without MIME-aware tools.
>   Send mail to [EMAIL PROTECTED] for more info.
> 
> --2081949219-247632633-1036098986=:979
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> 
> 
> I was discussing on the XFree86 Developers list concerning DRI on the 
> Radeon 9000 when Sven Luther forwarded me a message from this list posted 
> by Scott Harrison.  It indicated that he had some success in getting it to 
> work with very small patch.  I decided that I would check it out myself 
> and found that I didn't have the same luck. Listed below is the process 
> that I went through -- maybe someone here can point me in a good direction 
> to what to look into next.
> 
> The test machine is a Dell Insipiron 8200 with a 64 ATI Radeon Mobility 
> 9000:
> 
> -
> class: VIDEO 
> bus: PCI
> detached: 0
> driver: Card:ATI Radeon Mobility 9000
> desc: "ATI|Radeon RV250 Lf [Radeon Mobility 9000]"
> vendorId: 1002
> deviceId: 4c66
> subVendorId: 1028
> subDeviceId: 00d4
> pciType: 1
> -
> 
> I was running the latest CVS version of the XFree86 tree and pulled over 
> the lastest changes to the DRM/DRI structure.  I then made the 
> modifications that Scott Harrison indicated.  After rebuilding the kenerl 
> modules and the XFree86 tree - I loaded up tuxracer to test things out.  I 
> noticed that I didn't have permission to access /dev/dri/card0 so I 
> modified access so I could get to it.  Tuxracer started up, blanked the 
> screen and the machine would lock hard.
> 
> Relevant entries from my /var/log/messages:
> 
> Oct 31 14:55:09 moko modprobe: modprobe: Can't locate module 
> char-major-13-0
> Oct 31 14:55:09 moko last message repeated 3 times
> Oct 31 14:55:09 moko modprobe: modprobe: Can't locate module 
> char-major-13-64
> Oct 31 14:55:09 moko last message repeated 31 times
> Oct 31 14:55:09 moko modprobe: modprobe: Can't locate module 
> char-major-13-0
> Oct 31 14:55:10 moko last message repeated 31 times
> Oct 31 14:55:10 moko kernel: [drm:radeon_freelist_get] *ERROR* returning 
> NULL!
> Oct 31 14:55:10 moko last message repeated 2485 times
> 
> Attached is my XFree86.0.log ...
> 
> Any ideas would be appreciated ... I will continue to play on my end and 
> see what I can come up with.
> 
> -- 


---
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



[Dri-devel] Problems with MOHAA spearhead under wine on ATI 128.

2003-09-03 Thread dri-devel . sourceforge
Hello

I'm not sure that you will be too interested in this problem, but here goes...

I am running xfree86 4.3.0 with the ATI 128 drivers from 2nd Sept.  I am trying to run 
Medal of Honor Allied Assault with the Spearhead expansion pack under the August wine 
drop.  If I disable hardware opengl then the game runs fine (although extreemely 
slowly), running with hardware acceleration gives an error "Bad getprocaddress" from 
the program.

Now obviously this isn't enough for you guys to try and debug the problem, unless of 
course you have encountered similar problems, so where do I start in trying to debug 
the problem ?  I was thinking it might be possible to replace some of the API in the 
hardware version with the software opengl, but I wouldn't know where to start.  Is 
there an easy way of recompiling the hardware drivers with debug enabled ?

Thanks

Scott Harrison


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel