Discussion: the ati/radeon open source drivers & radeon repository

Cdh · 2010-11-26 07:42:35

This is my try:
http://dl.dropbox.com/u/13721560/lib32- … m/PKGBUILD

I think I am building too much only to remove it later but it worked. Maybe someone can improve it by not building things already provided by other packages. I have also enabled some options that I didn't understand why they were disabled.

Use like

LIBGL_DRIVERS_PATH=/usr/lib32/xorg/modules/dri_g/ wine Frozen\ Throne.exe -opengl

I think it works best if you have built lib32-mesa-full to the same version. (http://dl.dropbox.com/u/13721560/lib32- … l/PKGBUILD)

Last edited by Cdh (2010-11-26 07:46:24)

glsg · 2010-11-29 23:53:29

Hi all!
I got my Radeon HD 5670 (Evergreen) working with the stock kernel (2.6.36) and opensource drivers.
I've built from AUR the following packages.

dri2proto-git
glproto-git
libdrm-git
libgl-git
mesa-git
ati-dri-git
xf86-video-ati-git

Blur still not working. So if you have it enabled (in kwin or compiz) make sure you turn it off.
Any news about this feature?

EDIT: I'm using it without xorg.conf and kms enabled at early stage (default conf)

Last edited by glsg (2010-11-29 23:59:09)

Perry3D · 2010-11-30 23:01:34

For me this feature only works with gallium:

With classic mesa i get weird artifacts.

handy · 2010-12-01 04:38:29

So has development stopped on the non-gallium FOSS driver stack?

I've had exactly the same speed in the not a benchmark glxgears for well over a couple of months on my R600 GPU.

Cdh · 2010-12-01 09:28:37

Anyone else having no mouse pointer in the Warcraft3 menu in wine with r600g (and 64 bit)? It's a bit annoying because r600c is really slower. I tested it with vblank_mode=0 and I think it was better with r600c. Have to investigate further...

I use lib32-mesa-full and lib32-mesa-full-gallium from the PKGBUILDS I posted earlier. ( https://bbs.archlinux.org/viewtopic.php … 02#p857902 ). Is there something wrong?

ijanos · 2010-12-01 11:32:36

Guys, is google earth working for you with the open drivers?

lgomes · 2010-12-01 16:04:00

ijanos wrote:

Guys, is google earth working for you with the open drivers?

For me with my custom kernel 2.6.36-rc7, xorg-server-1.9.2-1, dri2proto-git-20101030-1, glproto-git-20101030-1, libdrm-git-20101107-1, mesa-full-gallium-20101107-1, xf86-video-ati-git-20101107-1:

And the aur package bin32-google-earth-5.2.1.1547-1.

With this packages the google earth work using the r600g (LIBGL_DRIVERS_PATH=/usr/lib/xorg/modules/dri_g/). Is usable without "anisotropic filter".

With preempt-rt kernel, the performance is better, no much, but better.

The fusion-icon work with some effects with r600g(LIBGL_DRIVERS_PATH=/usr/lib/xorg/modules/dri_g/).

xheyther · 2010-12-01 17:03:13

Perry3D:
I've installed dri2proto-git, glproto-git, libdrm-git, mesa-full-gallium, xf86-video-ati-git and I can't log into KDE. The desktop loading stop half way and send me back to kdm. What did I miss to use Galium ? (Everything work fine with the classic stack)

glsg · 2010-12-01 22:23:21

Perry3D wrote:

For me this feature only works with gallium

I've tried to install Gallium, but blur still not working

Here is my glxinfo | grep -i opengl output

OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD
OpenGL version string: 2.1 Mesa 7.10-devel
OpenGL shading language version string: 1.20

but this is the result
http://glsg.altervista.org/immagini/sshot.jpg

venky80 · 2010-12-02 01:43:03

what is the XvMC status for r600g gallium driver? Today flash was released with linux hardware acceleration

ijanos · 2010-12-02 07:15:10

venky80 wrote:

what is the XvMC status for r600g gallium driver? Today flash was released with linux hardware acceleration

The new beta flashplayer supports VDPAU which is nvidia only at the moment. Also the flash player only supports it in its 32bit version.

xheyther · 2010-12-02 08:42:20

venky80 wrote:

what is the XvMC status for r600g gallium driver? Today flash was released with linux hardware acceleration

And I believe that XvMC isn't merged yet in mainline. It might happen in time for Mesa 7.10 (currently planned for early January), but I don't now exactly when.

(you can follow the progress here : http://cgit.freedesktop.org/~deathsimpl … ipe-video)

Last edited by xheyther (2010-12-02 08:46:27)

Nokogiri · 2010-12-02 10:18:39

Im using radeon from your repo with my HD3650 and it works almost fine but if i try to run something with gallium i get often a GPU lockup

dmesg output of lockup

------------[ cut here ]------------
WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:244 radeon_fence_wait+0x239/0x290 [radeon]()
Hardware name:  
GPU lockup (waiting for 0x000012B0 last fence id 0x000012AF)
Modules linked in: ext3 jbd ext4 jbd2 crc16 ext2 mbcache snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq usbhid hid snd_pcm_oss snd_mixer_oss snd_emu10k1 uhci_hcd ohci_hcd snd_rawmidi snd_ac97_codec ac97_bus snd_pcm snd_seq_device snd_timer snd_page_alloc snd_util_mem snd_hwdep ehci_hcd snd soundcore usbcore shpchp processor emu10k1_gp thermal button fan i2c_sis96x pci_hotplug sg sis900 gameport evdev mii p4_clockmod freq_table speedstep_lib rtc_cmos rtc_core rtc_lib jfs sd_mod pata_sis pata_acpi libata scsi_mod floppy radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core sis_agp agpgart
Pid: 3690, comm: X Tainted: G        W   2.6.37-rc3-32326-g1040cc0-dirty #1
Call Trace:
 [<c1044b2d>] warn_slowpath_common+0x6d/0xa0
 [<f820fe19>] ? radeon_fence_wait+0x239/0x290 [radeon]
 [<f820fe19>] ? radeon_fence_wait+0x239/0x290 [radeon]
 [<c1044bde>] warn_slowpath_fmt+0x2e/0x30
 [<f820fe19>] radeon_fence_wait+0x239/0x290 [radeon]
 [<c1061c50>] ? autoremove_wake_function+0x0/0x40
 [<f82274de>] radeon_ib_get+0xfe/0x1c0 [radeon]
 [<c12f73bb>] ? __mutex_lock_slowpath+0x1eb/0x2b0
 [<f8228c7e>] radeon_cs_ioctl+0x5e/0x180 [radeon]
 [<c12f73bb>] ? __mutex_lock_slowpath+0x1eb/0x2b0
 [<f8072e21>] drm_ioctl+0x1e1/0x470 [drm]
 [<f8228c20>] ? radeon_cs_ioctl+0x0/0x180 [radeon]
 [<c103d7ba>] ? task_tick_fair+0x5a/0x110
 [<c104007b>] ? scheduler_tick+0xab/0x270
 [<c101eb46>] ? lapic_next_event+0x16/0x20
 [<c10700f3>] ? clockevents_program_event+0x83/0x140
 [<f8072c40>] ? drm_ioctl+0x0/0x470 [drm]
 [<c110c6ea>] do_vfs_ioctl+0x7a/0x590
 [<c1071381>] ? tick_program_event+0x21/0x30
 [<c10664f7>] ? hrtimer_interrupt+0x137/0x250
 [<c1049484>] ? do_setitimer+0x154/0x200
 [<c110cc5f>] sys_ioctl+0x5f/0x80
 [<c101f136>] ? smp_apic_timer_interrupt+0x56/0x90
 [<c10038df>] sysenter_do_call+0x12/0x28
---[ end trace 8de33fc5481dcfa3 ]---
[drm] Disabling audio support
radeon 0000:01:00.0: f5f74c00 unpin not necessary
radeon 0000:01:00.0: GPU softreset 
radeon 0000:01:00.0:   R_008010_GRBM_STATUS=0xA23334E0
radeon 0000:01:00.0:   R_008014_GRBM_STATUS2=0x00000003
radeon 0000:01:00.0:   R_000E50_SRBM_STATUS=0x200000C0
radeon 0000:01:00.0:   R_008020_GRBM_SOFT_RESET=0x00007FEE
radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001
radeon 0000:01:00.0:   R_008010_GRBM_STATUS=0xA0003030
radeon 0000:01:00.0:   R_008014_GRBM_STATUS2=0x00000003
radeon 0000:01:00.0:   R_000E50_SRBM_STATUS=0x200080C0
radeon 0000:01:00.0: GPU reset succeed
radeon 0000:01:00.0: WB disabled

output of dmesg grep drm

Kernel command line: BOOT_IMAGE=/vmlinuz26-drm-radeon-testing root=/dev/disk/by-uuid/4e0756e5-4583-46f4-a250-9f71ab972057 ro quiet video=1280x1024 resume=/dev/sda2 nohz=no
[drm] Initialized drm 1.1.0 20060810
[drm] radeon defaulting to kernel modesetting.
[drm] radeon kernel modesetting enabled.
[drm] initializing kernel modesetting (RV635 0x1002:0x9598).
[drm] register mmio base: 0xD8020000
[drm] register mmio size: 65536
[drm] Detected VRAM RAM=512M, BAR=128M
[drm] RAM width 128bits DDR
[drm] radeon: 512M of VRAM memory ready
[drm] radeon: 256M of GTT memory ready.
[drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[drm] Driver supports precise vblank timestamp query.
[drm] radeon: irq initialized.
[drm] GART: num cpu pages 65536, num gpu pages 65536
[drm] Loading RV635 Microcode
[drm] ring test succeeded in 1 usecs
[drm] radeon: ib pool ready.
[drm] ib test succeeded in 0 usecs
[drm] Enabling audio support
[drm] Radeon Display Connectors
[drm] Connector 0:
[drm]   DVI-I
[drm]   HPD1
[drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[drm]   Encoders:
[drm]     DFP1: INTERNAL_UNIPHY
[drm]     CRT2: INTERNAL_KLDSCP_DAC2
[drm] Connector 1:
[drm]   DIN
[drm]   Encoders:
[drm]     TV1: INTERNAL_KLDSCP_DAC2
[drm] Connector 2:
[drm]   DVI-I
[drm]   HPD2
[drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[drm]   Encoders:
[drm]     CRT1: INTERNAL_KLDSCP_DAC1
[drm]     DFP2: INTERNAL_KLDSCP_LVTMA
[drm] Internal thermal controller with fan control
[drm] radeon: power management initialized
[drm] fb mappable at 0xD00C1000
[drm] vram apper at 0xD0000000
[drm] size 5242880
[drm] fb depth is 24
[drm]    pitch is 5120
fb0: radeondrmfb frame buffer device
drm: registered panic notifier
[drm] Initialized radeon 2.8.0 20080528 for 0000:01:00.0 on minor 0
WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:244 radeon_fence_wait+0x239/0x290 [radeon]()
Modules linked in: ext3 jbd ext4 jbd2 crc16 ext2 mbcache snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq usbhid hid snd_pcm_oss snd_mixer_oss snd_emu10k1 uhci_hcd ohci_hcd snd_rawmidi snd_ac97_codec ac97_bus snd_pcm snd_seq_device snd_timer snd_page_alloc snd_util_mem snd_hwdep ehci_hcd snd soundcore usbcore shpchp processor emu10k1_gp thermal button fan i2c_sis96x pci_hotplug sg sis900 gameport evdev mii p4_clockmod freq_table speedstep_lib rtc_cmos rtc_core rtc_lib jfs sd_mod pata_sis pata_acpi libata scsi_mod floppy radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core sis_agp agpgart
 [<f8072e21>] drm_ioctl+0x1e1/0x470 [drm]
 [<f8072c40>] ? drm_ioctl+0x0/0x470 [drm]
[drm] Disabling audio support
[drm] ring test succeeded in 1 usecs
[drm] ib test succeeded in 1 usecs
[drm] Enabling audio support
WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:244 radeon_fence_wait+0x239/0x290 [radeon]()
Modules linked in: ext3 jbd ext4 jbd2 crc16 ext2 mbcache snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq usbhid hid snd_pcm_oss snd_mixer_oss snd_emu10k1 uhci_hcd ohci_hcd snd_rawmidi snd_ac97_codec ac97_bus snd_pcm snd_seq_device snd_timer snd_page_alloc snd_util_mem snd_hwdep ehci_hcd snd soundcore usbcore shpchp processor emu10k1_gp thermal button fan i2c_sis96x pci_hotplug sg sis900 gameport evdev mii p4_clockmod freq_table speedstep_lib rtc_cmos rtc_core rtc_lib jfs sd_mod pata_sis pata_acpi libata scsi_mod floppy radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core sis_agp agpgart
 [<f8072e21>] drm_ioctl+0x1e1/0x470 [drm]
 [<f8072c40>] ? drm_ioctl+0x0/0x470 [drm]
[drm] Disabling audio support
[drm] ring test succeeded in 1 usecs
[drm] ib test succeeded in 1 usecs
[drm] Enabling audio support

And finally glxinfo | grep -i opengl
r600c

OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Mesa DRI R600 (RV635 9598) 20090101 x86/MMX/SSE2 TCL DRI2
OpenGL version string: 2.1 Mesa 7.10-devel
OpenGL shading language version string: 1.20

r600g

OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV635
OpenGL version string: 2.1 Mesa 7.10-devel
OpenGL shading language version string: 1.20

Don't remember when but I know gallium worked some time ago with my card.

Last edited by Nokogiri (2010-12-02 10:28:33)

Perry3D · 2010-12-02 22:50:03

xheyther wrote:

Perry3D:
I've installed dri2proto-git, glproto-git, libdrm-git, mesa-full-gallium, xf86-video-ati-git and I can't log into KDE. The desktop loading stop half way and send me back to kdm. What did I miss to use Galium ? (Everything work fine with the classic stack)

Install mesa-full and mesa-full gallium at the same time. Now you can switch to gallium by changing an environment variable. For example, starting glxinfo with gallium.

LIBGL_DRIVERS_PATH=/usr/lib/xorg/modules/dri_g/ glxinfo

To do this system wide, create a file (gallium.sh for example) in /etc/profile.d/ with this content (dont forget chmod +x gallium.sh):

export LIBGL_DRIVERS_PATH=/usr/lib/xorg/modules/dri_g/

/edit: Maybe there is already a lib32-dri.sh in /etc/profile that export the variable.

Last edited by Perry3D (2010-12-02 23:04:58)

venky80 · 2010-12-03 01:21:52

xheyther wrote:

venky80 wrote:
what is the XvMC status for r600g gallium driver? Today flash was released with linux hardware acceleration
And I believe that XvMC isn't merged yet in mainline. It might happen in time for Mesa 7.10 (currently planned for early January), but I don't now exactly when.
(you can follow the progress here : http://cgit.freedesktop.org/~deathsimpl … ipe-video)

Thanks xheyther

but seems XvMC is not as good as VA-API or VADPU, seems myth tv is dropping it

thestinger · 2010-12-03 01:28:22

venky80 wrote:

xheyther wrote:
venky80 wrote:
what is the XvMC status for r600g gallium driver? Today flash was released with linux hardware acceleration
And I believe that XvMC isn't merged yet in mainline. It might happen in time for Mesa 7.10 (currently planned for early January), but I don't now exactly when.
(you can follow the progress here : http://cgit.freedesktop.org/~deathsimpl … ipe-video)
Thanks xheyther
but seems XvMC is not as good as VA-API or VADPU, seems myth tv is dropping it

the flash video accel uses vdpau only

http://www.phoronix.com/scan.php?page=n … &px=ODg1NQ

Last edited by thestinger (2010-12-03 01:36:38)

xheyther · 2010-12-07 13:33:03

Perry3D wrote:

xheyther wrote:
Perry3D:
I've installed dri2proto-git, glproto-git, libdrm-git, mesa-full-gallium, xf86-video-ati-git and I can't log into KDE. The desktop loading stop half way and send me back to kdm. What did I miss to use Galium ? (Everything work fine with the classic stack)
Install mesa-full and mesa-full gallium at the same time. Now you can switch to gallium by changing an environment variable. For example, starting glxinfo with gallium.
LIBGL_DRIVERS_PATH=/usr/lib/xorg/modules/dri_g/ glxinfo
To do this system wide, create a file (gallium.sh for example) in /etc/profile.d/ with this content (dont forget chmod +x gallium.sh):
export LIBGL_DRIVERS_PATH=/usr/lib/xorg/modules/dri_g/ 
/edit: Maybe there is already a lib32-dri.sh in /etc/profile that export the variable.

Thx for the explanations

Just a side note on XvMC, VA-API or VADPU :
VA-API was originally designed to fully replace XvMC some day. VADPU is a competing API designed by Nvidia and thus I don't expect to see it supported by any other GPU brand in a near future.

Regarding the state of XvMC and VA-API, nearly no OSS driver support them. The current work started on XvMC since, as far I understand, it's easier to implement, on top of gallium. It's likely that VA-API will be implemented on top of Gallium at some point (it's a wild guess here). I'm not deeply into those things but I believe that some work onXvMC could be used for VA-API (motion compensation and discrete cosine transform I think).

Perry3D · 2010-12-07 15:48:10

You are right. At the moment no OSS driver is supporting no video decoding (differentiate from hardware acceleration, XV for example).
But there are some guys working on the VD-PAU API with gallium: Phoronix: There's A Gallium3D State Tracker For VDPAU.
But i don't expect to see it in the near future.

Belitsky.A · 2010-12-07 16:34:30

Perry, maybe you should add mesa-full to mesa-full-gallium's depends in PKGBUILD?

Perry3D · 2010-12-07 16:40:57

Hmm...i didn't try it, but i think you can use mesa-full-gallium without mesa-full if you change the environment variable.

yimm · 2010-12-10 18:27:38

Just tried kernel 2.6.37-rc5 (git version), GPU voltage doesn't work yet...

# echo high > /sys/class/drm/card0/device/power_profile
# cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 500000 kHz
current engine clock: 500000 kHz
default memory clock: 850000 kHz
current memory clock: 850000 kHz
voltage: 1050 mV
PCIE lanes: 16

# echo low > /sys/class/drm/card0/device/power_profile
# cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 500000 kHz
current engine clock: 300000 kHz
default memory clock: 850000 kHz
current memory clock: 250000 kHz
voltage: 1050 mV
PCIE lanes: 16

Back to catalyst again.

Last edited by yimm (2010-12-10 18:28:17)

agapito · 2010-12-11 14:24:51

I am using an Evergreen card and my xserver is restarted randomly, anyone in this situation?

hoschi · 2010-12-11 16:56:15

Success report for Evergreen R800 (Mobile) with Gallium!

Performance:
118 FPS in IOQuake3. //Gallium and vblank_mode=0 (VSYNC OFF)
106 FPS in IOQuake3 // Classic and vlbank_mode=0 (VSYNC OFF)

Hardware:

Acer Timeline X 3820

Intel Core i5 CPU M 430  @ 2.27GHz
Main-Memory 4096 MB
Graphic-Card Radeon 5650
INTEL Postville SSD 80GB

I have no problems with Suspend-To-RAM (S3), indeed I am able to suspend my system while playing IOQuake3.
This is quite fancy

The performance with VSYNC ON is simply worse. Don't even try it!
I never see any tearing with VSYNC OFF, also the only true solution is OpenGL-Tripple-Buffering. I really don't understand the developers, vblank_mode=0 should be standard in all cases. Nobody wants VSYNC in the current situation. Instead VSYNC with OpenGL-Tripple-Buffering can be usefull in future.
I also recognize very often stuttering with VSYNC ON on other machines (as example my desktop with a R700 and Fedora14).

HowTo
Add this to pacman.conf

[radeon]
Server = [url]http://spiralinear.org/perry3d/x86_64[/url]

Execute as root this commands

# pacman -Syu
# pacman -S dri2proto-git glproto-git libdrm-git mesa-full mesa-demos-git mesa-full-gallium xf86-video-ati-git // write down the replaced packages for security

Create /etc/profile.d/radeon.sh

export LIBGL_DRIVERS_PATH=/usr/lib/xorg/modules/dri_g/
export vblank_mode=0 // don't put this in rc.local, will not work

Make radeon.sh executable with

# chmod +x radeon.sh

If you want the new power-management (only for laptop computers), add this to /etc/rc.local

# Set radeon to dynamic power-managment
echo -n dynpm > /sys/class/drm/card0/device/power_method

A note at the end.
If you use the power-management wait a little time before benchmarking. The system needs some time to recognize the situation and will ramp up the GPU.
Same thing after a Suspend-To-RAM, play and wait some time. Maybe the power-managment should react faster. If you have problems with power-management, deactivte it, it is not necessary.

I use Gallium now, because I got higher performance and there are no glitches.
Big Thanks to Perry3D and the developers from Xorg, AMD and the Kernel!

Last edited by hoschi (2010-12-11 17:27:55)

ijanos · 2010-12-11 17:07:15

hoschi wrote:

The performance with VSYNC ON is simply worse. Don't even try it!

Of course performance "worse". vsync will cap your FPS at the monitor refresh rate which I guess is 60Hz, so you will see max 60FPS. That's a feature not a bug.

hoschi · 2010-12-11 17:20:32

Nice try, but failed
Of course I know that. I talked about Tripple-Buffering *hint*
But stuttering and an average FPS rate around 30 is really worse. Especially if I got an average rate around 120 FPS without VSYNC.

Last edited by hoschi (2010-12-11 17:24:42)

Arch Linux

#1801 2010-11-26 07:42:35

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1802 2010-11-29 23:53:29

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1803 2010-11-30 23:01:34

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1804 2010-12-01 04:38:29

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1805 2010-12-01 09:28:37

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1806 2010-12-01 11:32:36

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1807 2010-12-01 16:04:00

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1808 2010-12-01 17:03:13

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1809 2010-12-01 22:23:21

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1810 2010-12-02 01:43:03

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1811 2010-12-02 07:15:10

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1812 2010-12-02 08:42:20

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1813 2010-12-02 10:18:39

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1814 2010-12-02 22:50:03

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1815 2010-12-03 01:21:52

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1816 2010-12-03 01:28:22

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1817 2010-12-07 13:33:03

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1818 2010-12-07 15:48:10

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1819 2010-12-07 16:34:30

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1820 2010-12-07 16:40:57

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1821 2010-12-10 18:27:38

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1822 2010-12-11 14:24:51

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1823 2010-12-11 16:56:15

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1824 2010-12-11 17:07:15

Re: Discussion: the ati/radeon open source drivers & radeon repository

#1825 2010-12-11 17:20:32

Re: Discussion: the ati/radeon open source drivers & radeon repository

Board footer