Announcement

Collapse
No announcement yet.

Linux 2.6.32 To Get R600 KMS Along With 3D

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Maarte
    replied
    Will Fedora 12 (Constantine) be 2.6.31 or 2.6.32? There seem to be conflicting opinions across both official sites and this forum. Thankyou for any clarification offered.

    Leave a comment:


  • LiquidAcid
    replied
    UUID?

    I'm just booting the kernel built from airlied's drm-next tree and once the login is available I modprobe radeon with the corresponding parameters. Is this the wrong approach?

    Leave a comment:


  • Kano
    replied
    Well you need it for booting from UUID. But when you don't have it then you can not recreate it of course.

    Leave a comment:


  • LiquidAcid
    replied
    Originally posted by Kano View Post
    @LiquidAcid

    Did you run

    update-initramfs -u

    to get the new radeon module into the initrd?
    I'm on gentoo linux and I have not init ramdisk.

    Leave a comment:


  • frische
    replied
    Originally posted by agd5f View Post
    Better power management is next on our list once r6xx/r7xx 3D support stabilizes a bit more.
    Great. At least for me, better power management is more important than 3d.

    Any estimate when there will be a new release of the driver?

    Leave a comment:


  • nanonyme
    replied
    Originally posted by bridgman View Post
    What you're seeing just indicates that there are no immediate plans to add KMS support to the radeonhd driver. Current thinking is that both radeon *and* radeonhd will eventually get replaced by a generic xorg driver running over KMS and Gallium3D.
    And as I've commented several times earlier, I consider each new modesetting feature added to KMS one step further to making radeonhd unnecessary for anything since it won't (probably, since it would be real-life effort duplication) be getting KMS. :3 True, radeon will follow suit eventually but in the meantime until Gallium3D matures, we'll probably be moving from radeonhd to radeon...

    Leave a comment:


  • smitty3268
    replied
    Edit: Hmm, Bridgman explained this better than I - don't know how i missed his post as it looks older than mine...

    Leave a comment:


  • bridgman
    replied
    Originally posted by V!NCENT View Post
    Because on the Gallium3D matrix the HDR600 (HD Radeon?) core is not scheduled to get KMS (N/N)
    Ahh, now I understand. R700 (RHD) in that context refers to r7xx parts running with the radeonhd driver (aka xf86-video-radeonhd), while R700 refers to the same parts running with the radeon driver (aka xf86-video-ati).

    What you're seeing just indicates that there are no immediate plans to add KMS support to the radeonhd driver. Current thinking is that both radeon *and* radeonhd will eventually get replaced by a generic xorg driver running over KMS and Gallium3D.

    Leave a comment:


  • agd5f
    replied
    Originally posted by V!NCENT View Post
    Because on the Gallium3D matrix the HDR600 (HD Radeon?) core is not scheduled to get KMS (N/N)
    Both r6xx and r7xx chips already have KMS support. KMS only works with the radeon driver.

    Leave a comment:


  • Kano
    replied
    @LiquidAcid

    Did you run

    update-initramfs -u

    to get the new radeon module into the initrd?

    Leave a comment:

Working...
X