Results 1 to 10 of 18

Thread: The Extraordinary DRM Pull Request For Linux 3.11

Hybrid View

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

    Default The Extraordinary DRM Pull Request For Linux 3.11

    Phoronix: The Extraordinary DRM Pull Request For Linux 3.11

    David Airlie has submitted the DRM subsystem pull request for the Linux 3.11 kernel that is of monster size. The Radeon DRM kernel driver is now perhaps the single biggest Linux kernel driver by code size after the merging of its huge dynamic power management code addition...

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

  2. #2
    Join Date
    Jan 2011
    Posts
    2

    Default Very big to boot ?

    By the sounds of it .. how do you fit such as big driver with the kernel updates, boot disks and distributions. I would love to see them have a basic core driver that is simple and small to get the computer started and then allows the system to load or swap drivers to enable playing games and advanced features. If it's done right we have the convenience of a small driver that is included everywhere and the user can then load the fancy stuff after the initial boot. Otherwise we are left with big packages and updates even before you can boot.

  3. #3
    Join Date
    Jun 2011
    Posts
    1,057

    Default

    Quote Originally Posted by tygrus View Post
    By the sounds of it .. how do you fit such as big driver with the kernel updates, boot disks and distributions. I would love to see them have a basic core driver that is simple and small to get the computer started and then allows the system to load or swap drivers to enable playing games and advanced features. If it's done right we have the convenience of a small driver that is included everywhere and the user can then load the fancy stuff after the initial boot. Otherwise we are left with big packages and updates even before you can boot.
    That is not a real issue, and even if it was what you're proposing is not a good solution because videocards in particular need proper power and fan management that a generic VESA driver can't handle.

  4. #4
    Join Date
    Nov 2010
    Location
    Stockholm, Sweden
    Posts
    416

    Default

    It's going to be fun to see Linus' response to this =)

    Another interesting thing is to see if any extensive code review is done (many eyes on your code, right?) since that is one of the points of FOSS. I'm mainly thinking of the following words of wisdom:

    Ask a programmer to review 10 lines of code, he'll find 10 issues. Ask him to do 500 lines and he'll say it looks good.

  5. #5
    Join Date
    May 2007
    Posts
    319

    Default

    Quote Originally Posted by Azpegath View Post
    It's going to be fun to see Linus' response to this =)

    Another interesting thing is to see if any extensive code review is done (many eyes on your code, right?) since that is one of the points of FOSS. I'm mainly thinking of the following words of wisdom:
    Well I doubt Linus will really care, its the merge window, he merges stuff that has been tested, and this code has seen a lot of testing already,

    The code has been reviewed by a number of people, granted the number of people who can make sense of gpu power management code is limited :-P

    Dave.

  6. #6
    Join Date
    Nov 2010
    Location
    Stockholm, Sweden
    Posts
    416

    Default

    Quote Originally Posted by airlied View Post
    Well I doubt Linus will really care, its the merge window, he merges stuff that has been tested, and this code has seen a lot of testing already,
    The code has been reviewed by a number of people, granted the number of people who can make sense of gpu power management code is limited :-P
    Dave.
    I was just recollecting his previous responses to large merges, like the "What is this crap?!" that he's said before. But perhaps that's just from a testing viewpoint, and not code review. I guess he doesn't really have time to do code reviews of the things he merges.

  7. #7
    Join Date
    Apr 2010
    Posts
    777

    Default

    Quote Originally Posted by Azpegath View Post
    Another interesting thing is to see if any extensive code review is done (many eyes on your code, right?) since that is one of the points of FOSS. I'm mainly thinking of the following words of wisdom:
    Remember, this is just the pull into the main tree - it's not like someone has just made a single massive commit. The actual changes would have been a large number of small commits, which tends to be much easier to review.

  8. #8
    Join Date
    Dec 2011
    Posts
    123

    Default

    Considering the amount of work on 3.10 and 3.11 I hope to see a couple of benchmarks to see how the new kernel compares to the older ones in terms of performance and power usage.

  9. #9
    Join Date
    Sep 2011
    Posts
    707

    Default

    Quote Originally Posted by tygrus View Post
    By the sounds of it .. how do you fit such as big driver with the kernel updates, boot disks and distributions. I would love to see them have a basic core driver that is simple and small to get the computer started and then allows the system to load or swap drivers to enable playing games and advanced features. If it's done right we have the convenience of a small driver that is included everywhere and the user can then load the fancy stuff after the initial boot. Otherwise we are left with big packages and updates even before you can boot.
    All 3d stuff is in Mesa so in a way this is already the case. In any cases i can almost assure you that what you are loading with Linux is smaller then what you would load with catalyst (not that that automatically equals faster)

Posting Permissions

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