Re: [Dri-devel] Ati Rage 3D IIC with PCI slot (integrated)

lease reply... You can compile agpgart into a kernel with no agp slots just fine, this wil fix the unresolved symbols. Whether it will make your card work is another matter, but it's a start. Regards, Philip Willoughby - -- echo [EMAIL PROTECTED] | tr "bizndfohces" "pwgd9ociak

[Dri-devel] Kernel module sources for XFree86 4.1.0

, but please, please, try and use a mirror where possible. Regards, Philip Willoughby - -- echo [EMAIL PROTECTED] | tr "bizndfohces" "pwgd9ociaku" -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7O3D

Re: [Dri-devel] Max Radeon Texture size

to specify each >individual mipmap level offset. > >The change will affect the SAREA layout (if I remember correctly), but >that's about it. If there's a problem, let me know. Just out of interest, does 2kx2k texture support mean 2048x2048 or 2050x2050 (for borders?). Regards

Re: [Dri-devel] Texture sizes larger than screen dimensions + blanking at x=1355

getting blanked out. Is this a limitation of the Radeon or >> the DRI? > >I'm not seeing that problem here. Nor am I. Regards, Philip Willoughby -- echo [EMAIL PROTECTED] | tr "bizndfohces" "pwgd9ociaku" ___ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel

Re: [Dri-devel] Rage128 and VIA KT133

. There is no guarantee that this will solve it for everyone -- your motherboard manufacturer may not have included the fix that mine has. Regards, Philip Willoughby - -- echo [EMAIL PROTECTED] | tr "bizndfohces" "pwgd9ociaku" -BEGIN PGP SIGNATURE- Version: GnuPG

Re: [Dri-devel] Re: Radeon on Irongate: DRI locks up machine instantly

Today, Stephen C. Tweedie wrote: >I'm using VIA Irongate too. Err, AMD make the irongate chipsets -- the 75x series. VIA don't -- they make the Apollo series Which have you got? Regards, Philip Willoughby -- echo [EMAIL PROTECTED] | tr "bizndfo

Re: [Dri-devel] Determining the proper Glide library to use atruntime

e RPM work out the appropriate symlink (you can tell the card by looking in /proc/bus/pci/devices). If you want to be especially safe, you could rescan at every boot from an init script and resymlink if necessary. Regards, Philip Willoughby -- echo [EMAIL PROTECTED] | tr "bizndfohces&

Re: [Dri-devel] DRI installation script README

SIX compliant tar archive when creating archives. It does nothing when untarring. You need to use -o when creating archives if the archive will ever be used with a non-GNU tar, although it is probably a lot better to use cpio anyway... Regards, Philip Willoughby -- echo [EMAIL PROTECTED] |

[Dri-devel] Control over buffer sizes

ality, stable driver for the radeon, it gives me plenty of ammo against my nvidia loving friends. Regards, Philip Willoughby -- echo [EMAIL PROTECTED] | tr "bizndfohces" "pwgd9ociaku" ___ Dri-devel mailing list [EMAIL PROTECTED] htt

Re: [Dri-devel] Re: Dri-devel digest, Vol 1 #740 - 15 msgs

this time) but it's not stable there either but can't say >is this because of games or what (3DMark2000 goes trough properly). (and >no I'm not overclocking) Unfortunately you cannot rule out broken AGP on your motherboard. The Voodoo3 would work fine because it doesn't u

Re: [Dri-devel] xc/xc

Today, Daryll Strauss wrote: >On Fri, Apr 20, 2001 at 05:24:37PM +0100, Alan Hourihane wrote: >> On Fri, Apr 20, 2001 at 05:17:25PM +0100, Philip Willoughby wrote: >> > Is there a good reason for the xc directory nested in the DRI CVS xc >> > directory? I ask becaus

[Dri-devel] xc/xc

Is there a good reason for the xc directory nested in the DRI CVS xc directory? I ask because it requires 119Mb of disk space, takes an age to download for new users, and it is not used by `make World' or `make install'. If it is not needed, could it be removed? Regards, Philip