Results 1 to 10 of 10

Thread: DRM Change Continues To Cause Debate

  1. #1
    Join Date
    Jan 2007
    Posts
    14,904

    Default DRM Change Continues To Cause Debate

    Phoronix: DRM Change Continues To Cause Debate

    Kristian Høgsberg on the 6th of November had wrote a message on the DRI development list regarding the libdrm repository. With so much of the Direct Rendering Manager (DRM) work going straight into the Linux kernel -- thanks in large part to all of the work on memory management and kernel mode-setting -- Kristian proposed that the DRM driver code from the separate DRM Git tree...

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

  2. #2
    Join Date
    Jan 2009
    Posts
    80

    Default

    The most typo-infested news entry ever.

  3. #3
    Join Date
    Mar 2008
    Posts
    575

    Default

    And like Steve Ballmer says: developers, developers, developers, developers!

  4. #4
    Join Date
    Nov 2009
    Posts
    6

    Default

    I wouldn't really call that a debate. More like one disgruntled user repeating the same thing over-and-over, while everyone else seems to have accepted the decision and moved on.
    Last edited by Bluefang; 11-29-2009 at 11:08 PM.

  5. #5
    Join Date
    Aug 2009
    Posts
    2,264

    Default

    Would these changes require nVidia and ATI to support this architecture in their proprietary drivers?

  6. #6

    Default

    Quote Originally Posted by V!NCENT View Post
    Would these changes require nVidia and ATI to support this architecture in their proprietary drivers?
    Did you read the article? They're just changing how the code is organised, not any interfaces that the drivers actually have to use. It will make very little difference in the grand scheme of things, apart from hopefully making the code easier to maintain.

  7. #7
    Join Date
    Dec 2008
    Posts
    166

    Default MacOS and Windows DRM trees?

    Where are those trees?

  8. #8
    Join Date
    Aug 2009
    Posts
    2,264

    Default

    Quote Originally Posted by srg_13 View Post
    Did you read the article? They're just changing how the code is organised, not any interfaces that the drivers actually have to use. It will make very little difference in the grand scheme of things, apart from hopefully making the code easier to maintain.
    With so much of the Direct Rendering Manager (DRM) work going straight into the Linux kernel [...] With this message, Kristian created a new DRM repository that dropped all of the linux-core, bsd-core, and shared-core code.
    So what trees will end up in let's say Ubuntu and OpenSuSE? I wondered if this would conflict with proprietary drivers...

  9. #9
    Join Date
    Nov 2009
    Posts
    6

    Default

    No, it wont.

    The only thing that happened was that the kernel portions of libdrm were removed from the repository (because it's already being maintained elsewhere, in kernel). So now the libdrm repository is essentially just the userspace component.

  10. #10
    Join Date
    Sep 2006
    Posts
    714

    Default

    Nvidia proprietary drivers use their own proprietary kernel interface.

    So there is nothing the libdrm folks can really do to screw with Nvidia unless they go out of their way.

Posting Permissions

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