Page 1 of 3 123 LastLast
Results 1 to 10 of 24

Thread: ATI's X.Org DDX Driver Gets KMS Ready

  1. #1
    Join Date
    Jan 2007
    Posts
    15,690

    Default ATI's X.Org DDX Driver Gets KMS Ready

    Phoronix: ATI's X.Org DDX Driver Gets KMS Ready

    With the forthcoming Linux 2.6.31 kernel there is finally Radeon kernel mode-setting support so that those running ATI graphics cards on Linux will be able to experience a cleaner boot process, faster VT switching, improved security, and other overdue features for Linux. Using kernel mode-setting with ATI Radeon hardware will require a supported kernel that is built with the appropriate kernel configuration options. In addition, an updated DDX driver is also necessary so it realizes the kernel is handling the mode-setting process...

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

  2. #2
    Join Date
    May 2008
    Posts
    598

    Default

    So this is a vital patch before KMS for R600 and R700 can be implemented?

  3. #3
    Join Date
    Oct 2008
    Posts
    3,248

    Default

    Quote Originally Posted by Louise View Post
    So this is a vital patch before KMS for R600 and R700 can be implemented?
    This was required before ANY radeon card could use KMS, both R600+ and the older generations. I believe the stuff that isn't working just for the newer cards is in the kernel and Mesa codebases. Not sure about DRM.

  4. #4
    Join Date
    Jul 2007
    Posts
    265

    Default

    The transition to KMS should be quite straight-forward, as it has been enabled in Fedora for a year now, providing a pretty long testing time frame.

  5. #5
    Join Date
    May 2008
    Posts
    598

    Default

    Quote Originally Posted by smitty3268 View Post
    This was required before ANY radeon card could use KMS, both R600+ and the older generations. I believe the stuff that isn't working just for the newer cards is in the kernel and Mesa codebases. Not sure about DRM.
    I see

    It would be nice with a dependency tree. E.g.

    Code:
    KMS -> 3D -> Power Management
    ... and all the other stuff at
    http://www.x.org/wiki/RadeonFeature


  6. #6
    Join Date
    Feb 2009
    Location
    France
    Posts
    309

    Default

    I've just tried this out and it didn't work well !
    I didn't take the time to figure out why, just wanted to say recompiling was not sufficient for me.

    I've fall back on the kms branch that kind of "works".

  7. #7
    Join Date
    Oct 2008
    Posts
    3,248

    Default

    Quote Originally Posted by Louise View Post
    It would be nice with a dependency tree.
    As I understand it:

    possible to work on now:
    r600+ 3D (OpenGL1.4)
    video acceleration (shader, not UVD2)
    power management (already in master branch)

    memory manager -> KMS
    memory manager -> DRI2
    memory manager -> Gallium

    Gallium -> more advanced 3D (OpenGL2.0+)
    Gallium -> generic video acceleration framework

    KMS -> more advanced power management

  8. #8
    Join Date
    Oct 2007
    Location
    Toronto-ish
    Posts
    7,578

    Default

    AFAICS this patch merges some of the existing KMS support into master. Kernel and mesa support have already been merged (2.6.31 for the kernel, radeon-rewrite merge for mesa), so once this merge is done all the big pieces for KMS support will be in their respective master trees.

    I don't think this does anything specific for 6xx/7xx but it does mean that work can now be based on master rather than on another branch, which is really nice.

    Smitty3268, I made a few minor changes, see below. Otherwise your list looks good.

    memory manager -> KMS
    memory manager -> DRI2 / RDR (RDR is what everyone really wants)
    memory manager -> Gallium3D
    memory manager -> more advanced 3D (OpenGL 1.5+) via chip-specific code

    Gallium3D -> more advanced 3D (OpenGL 1.5+) via generic code
    Gallium3D -> generic video acceleration framework

    KMS -> more advanced power management (dynamic control of clocks etc..)
    Last edited by bridgman; 07-01-2009 at 12:38 AM.

  9. #9
    Join Date
    May 2008
    Posts
    343

    Default

    Quote Originally Posted by MPF View Post
    I've just tried this out and it didn't work well !
    I didn't take the time to figure out why, just wanted to say recompiling was not sufficient for me.

    I've fall back on the kms branch that kind of "works".
    The commit in question, which was applied to master, does not provide KMS support. It is just some preparations for the final KMS patch to land later. So you will still have to use the kms-support branch for a while.

  10. #10
    Join Date
    May 2008
    Posts
    598

    Default

    If I combine the brances on the dependency tree, it becomes
    Code:
    memory manager -+-> KMS -> more advanced power management (dynamic control of clocks etc..)
                    |
                    +-> DRI2 / RDR (RDR is what everyone really wants)
                    |
                    +-> more advanced 3D (OpenGL 1.5+) via chip-specific code
                    |
                    +-> Gallium3D -+-> more advanced 3D (OpenGL 1.5+) via generic code
                                   |
                                   +-> generic video acceleration framework
    Edit: branch 1 and 3 are not the same My bad

    But can I ask where these go on the tree?:

    * OpenCL
    * TV-out
    * GLSL
    * Display Port
    Last edited by Louise; 07-01-2009 at 10:29 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •