search for: rv280

...CI_VENDOR_ID_ATI, 0x4152, 0x1458, 0x4038, 4}, > - /* Intel 82865G/PE/P DRAM Controller/Host-Hub / Mobility 9800 Needs AGPMode 4 (deb #462590) */ > - { PCI_VENDOR_ID_INTEL, 0x2570, PCI_VENDOR_ID_ATI, 0x4a4e, PCI_VENDOR_ID_DELL, 0x5106, 4}, > - /* Intel 82865G/PE/P DRAM Controller/Host-Hub / RV280 [Radeon 9200 SE] Needs AGPMode 4 (lp #300304) */ > - { PCI_VENDOR_ID_INTEL, 0x2570, PCI_VENDOR_ID_ATI, 0x5964, > - 0x148c, 0x2073, 4}, > - /* Intel 82855PM Processor to I/O Controller / Mobility M6 LY Needs AGPMode 1 (deb #467235) */ > - { PCI_VENDOR_ID_INTEL, 0x3340, PCI_VENDOR_ID_ATI...

...NTEL, 0x2550, PCI_VENDOR_ID_ATI, 0x4152, 0x1458, 0x4038, 4}, - /* Intel 82865G/PE/P DRAM Controller/Host-Hub / Mobility 9800 Needs AGPMode 4 (deb #462590) */ - { PCI_VENDOR_ID_INTEL, 0x2570, PCI_VENDOR_ID_ATI, 0x4a4e, PCI_VENDOR_ID_DELL, 0x5106, 4}, - /* Intel 82865G/PE/P DRAM Controller/Host-Hub / RV280 [Radeon 9200 SE] Needs AGPMode 4 (lp #300304) */ - { PCI_VENDOR_ID_INTEL, 0x2570, PCI_VENDOR_ID_ATI, 0x5964, - 0x148c, 0x2073, 4}, - /* Intel 82855PM Processor to I/O Controller / Mobility M6 LY Needs AGPMode 1 (deb #467235) */ - { PCI_VENDOR_ID_INTEL, 0x3340, PCI_VENDOR_ID_ATI, 0x4c59, - PCI_VEN...

Hi I try to install compiz in to my FC5 machine. I have ATI Inc RV280 [Radeon 9200 SE] card. when I try to switch to compiz I get the following error message ============================= compiz --replace gconf compiz: SmcOpenConnection failed: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authenticatio...

...0x4152, 0x1458, 0x4038, 4}, > - /* Intel 82865G/PE/P DRAM Controller/Host-Hub / Mobility 9800 Needs AGPMode 4 (deb #462590) */ > - { PCI_VENDOR_ID_INTEL, 0x2570, PCI_VENDOR_ID_ATI, 0x4a4e, PCI_VENDOR_ID_DELL, 0x5106, 4}, > - /* Intel 82865G/PE/P DRAM Controller/Host-Hub / RV280 [Radeon 9200 SE] Needs AGPMode 4 (lp #300304) */ > - { PCI_VENDOR_ID_INTEL, 0x2570, PCI_VENDOR_ID_ATI, 0x5964, > - 0x148c, 0x2073, 4}, > - /* Intel 82855PM Processor to I/O Controller / Mobility M6 LY Needs AGPMode 1 (deb #467235) */ > - { PCI_VENDOR_ID_I...

...er specific PCI GART. >> >> For now just deprecate the code and don't enable the AGP GART in TTM >> even when general AGP support is available. > > So I've used an ancient system (32bit) to setup a test box for this. > > > The first GPU I could test is an RV280 (Radeon 9200 PRO) which is easily > 15 years old. > > What happens in AGP mode is that glxgears shows artifacts during > rendering on this system. > > In PCI mode those rendering artifacts are gone and glxgears seems to > draw everything correctly now. > > Performance...

...o the driver specific PCI GART. > > > > For now just deprecate the code and don't enable the AGP GART in TTM even when general AGP support is available. > > So I've used an ancient system (32bit) to setup a test box for this. > > > The first GPU I could test is an RV280 (Radeon 9200 PRO) which is easily > 15 years old. > > What happens in AGP mode is that glxgears shows artifacts during > rendering on this system. > > In PCI mode those rendering artifacts are gone and glxgears seems to > draw everything correctly now. > > Performance is...

Hi guys, Well let's face it AGP is a total headache to maintain and dead for at least 10+ years. We have a lot of x86 specific stuff in the architecture independent graphics memory management to get the caching right, abusing the DMA API on multiple occasions, need to distinct between AGP and driver specific page tables etc etc... So the idea here is to just go ahead and remove the support

Unfortunately AGP is still to widely used as we could just drop support for using its GART. Not using the AGP GART also doesn't mean a loss in functionality since drivers will just fallback to the driver specific PCI GART. For now just deprecate the code and don't enable the AGP GART in TTM even when general AGP support is available. Please comment, Christian.

...nce drivers will just fallback to the driver specific PCI GART. > > For now just deprecate the code and don't enable the AGP GART in TTM even when general AGP support is available. So I've used an ancient system (32bit) to setup a test box for this. The first GPU I could test is an RV280 (Radeon 9200 PRO) which is easily 15 years old. What happens in AGP mode is that glxgears shows artifacts during rendering on this system. In PCI mode those rendering artifacts are gone and glxgears seems to draw everything correctly now. Performance is obviously not comparable, cause in AGP...

.... >>> >>> For now just deprecate the code and don't enable the AGP GART in TTM >>> even when general AGP support is available. >> So I've used an ancient system (32bit) to setup a test box for this. >> >> >> The first GPU I could test is an RV280 (Radeon 9200 PRO) which is easily >> 15 years old. >> >> What happens in AGP mode is that glxgears shows artifacts during >> rendering on this system. >> >> In PCI mode those rendering artifacts are gone and glxgears seems to >> draw everything correctly no...

...ied with and without: Option "AddARGBGLXVisuals" "True" ..defined in the Screen section of xorg.conf, but with no difference. To my understanding, this option is only for nvidia cards using proprietary drivers. I see nothing noteworthy in the xorg log. I have a Radeon 9250 (rv280) card and I run with the DRI drivers, ati, xf86-video-ati-6.8.191. I run Mesa-7.0.3 and xorg-server-1.4.2 on GNU/Linux-2.6.26-rc8. I'm running all the compiz packages from the 0.7.6 directory. Any pointers as to what I can try?. -- Esben Stien is b0ef at e s a...

Trying to run compiz on xorg-7.1 (aiglx), but getting the message: compiz: Root visual is not a double buffered GL visual compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 I'm on GNU/Linux with kernel 2.6.18 using DRI on ATI Radeon 9250 (rv280). I have mesa-6.5. Direct rendering is working fine. I've seen numerous people mention this problem, but they seem to be using proprietary drivers. My xorg log shows: (**) Option "AIGLX" "on" (**) Extension "Composite" is enabled Any pointers as to what may ca...

...ific PCI GART. >>> >>> For now just deprecate the code and don't enable the AGP GART in TTM even when general AGP support is available. >> So I've used an ancient system (32bit) to setup a test box for this. >> >> >> The first GPU I could test is an RV280 (Radeon 9200 PRO) which is easily >> 15 years old. >> >> What happens in AGP mode is that glxgears shows artifacts during >> rendering on this system. >> >> In PCI mode those rendering artifacts are gone and glxgears seems to >> draw everything correctly no...

...support of UtahGLX and Direct Rendering Infrastructure (DRI) and releasing of the R100 series (Radeon 7500-8000) and R200 (Radeon 8500-9000) series. These 3D implementations were add-ons to the stock MIT drivers. Unfortunately, the lag time between release and lack of variant endless support (e.g., RV280/Radeon 9200, etc...) often caused major headaches and issues -- let alone performance sucked. Worse yet was the fact that nVidia had established itself as _the_ video card/ driver combo for production GLX. So as of the R300 (Radeon 9500+) series, ATI has _withheld_ 3D specifications. In reality,...