Linux 2.6.32 To Get R600 KMS Along With 3D

[phoronix]

Phoronix: Linux 2.6.32 To Get R600 KMS Along With 3D

David Airlie has pushed a horde of new code into his drm-next Git tree, which is what will get pulled into the Linux 2.6.32 kernel once the merge window is open. Most prominently, this new DRM code brings support for kernel mode-setting with R600 class hardware as well as 3D support...

http://www.phoronix.com/vr.php?view=NzUxNg

[JeanPaul145]

Phoronix: Linux 2.6.32 To Get R600 KMS Along With 3D

David Airlie has pushed a horde of new code into his drm-next Git tree, which is what will get pulled into the Linux 2.6.32 kernel once the merge window is open. Most prominently, this new DRM code brings support for kernel mode-setting with R600 class hardware as well as 3D support...

http://www.phoronix.com/vr.php?view=NzUxNg

Why is the article only naming the R600 hardware? Everything I've read so far suggests that the support is for both R600 and R700 hardware, even the source blog post implicates this

[rbmorse]

And what about R800? When do they come on-line?

[lbcoder]

Why is the article only naming the R600 hardware? Everything I've read so far suggests that the support is for both R600 and R700 hardware, even the source blog post implicates this

It is pretty much redundant to mention R700 specifically since everything that applies to R600 also applies to R700. So the reason is that it saves 5 characters {space}"R700", at every point of mention.

[lbcoder]

Fedora rawhide users, just wait for a day and it should all be available.

*** nice
So tomorrow all I gotta do is an easy "yum update" and 3D should start working...

[m4rgin4l]

Phoronix: Linux 2.6.32 To Get R600 KMS Along With 3D

David Airlie has pushed a horde of new code into his drm-next Git tree, which is what will get pulled into the Linux 2.6.32 kernel once the merge window is open. Most prominently, this new DRM code brings support for kernel mode-setting with R600 class hardware as well as 3D support...

http://www.phoronix.com/vr.php?view=NzUxNg

pretty f******g sweet

[JeanPaul145]

It is pretty much redundant to mention R700 specifically since everything that applies to R600 also applies to R700. So the reason is that it saves 5 characters {space}"R700", at every point of mention.

Not if (almost?) every article up until now has spoken of R600/R700 (note the forward slash and the R700). Omitting it now is a breeding ground for confusion because it isn't consistent.

[glisse]

*** nice
So tomorrow all I gotta do is an easy "yum update" and 3D should start working...

Only if you are on f12

[bridgman]

The naming convention is (generally) to have the folder name indicate the oldest generation supported, eg r300 supports 3xx, 4xx, 5xx and rs6xx while r600 supports 6xx, 7xx and possibly future generations.

rbmorse, our focus right now is getting the 6xx/7xx code base solid so that we have a good starting point for future GPUs.

[lbcoder]

Only if you are on f12

...That would be the reason I said all *I* gotta do