Announcement

Collapse
No announcement yet.

Another Linus Rant About Linux DRM; Rejects Pull

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

  • Another Linus Rant About Linux DRM; Rejects Pull

    Phoronix: Another Linus Rant About Linux DRM; Rejects Pull

    Linus Torvalds is known to make a few colorful remarks from time to time. Today he's become frustrated once again with the Linux DRM layer and has rejected a pull request for the Linux 3.2 kernel...

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

  • #2
    I mean, this is pure gossip.

    Comment


    • #3
      Originally posted by bulletxt View Post
      I mean, this is pure gossip.
      you have to admit however that linus's rants spice things up a bit

      Comment


      • #4
        Originally posted by 89c51 View Post
        you have to admit however that linus's rants spice things up a bit
        But when he reaches for the "masturbating monkeys" rant, shit gets real!

        Comment


        • #5
          Kind of sucks that the kernel has only one real release cycle that's effectively forced upon everybody , even those who don't run "debian stable" so to speak, and have such hardcore stability needs that they would rather delay applying a patch that fixes something known to be broken in order to avoid the much smaller possibility of a regression.

          I say "effectively" forced upon everyone because nobody has the time to maintain a branch for backporting DRM and legitimate, "lower risk" fixes which just happen to land in the middle of a release cycle. Now that zen-unstable is dead, and linux-next isn't in what I'd call a usable state for most people, there aren't a lot of alternatives to the vanilla kernel.

          Comment


          • #6
            It's not only for DRM

            Everything after -rc1 should be about regressions caused by -rc1 (the merge window). Linus has been clear about it, and DRM is not special in any way, it should follow the same rules.

            Comment


            • #7
              radeon kms fix?

              I have a question, any one know what that radeon kms fix was for?

              Comment


              • #8
                There are release schedules for a reason. If someone want to add new features or fixes for old bugs, there is a time for that. -rc4 isn't it. I am sure reasonable exceptions can be made, but it seems like Linus feels the DRM people are abusing the process and just outright ignoring the schedule, and I don't think that is okay. The whole point of an RC cycle is to test things, and you can't test things properly if they keep changing.

                Comment


                • #9
                  Hooray, more sensationalist tabloid crap...

                  Comment


                  • #10
                    Good for Linus. He's got standards for software quality. If you're going to push untested crap into tree when the window opens, don't expect to push large patches to said crap in later rc's.

                    Comment


                    • #11
                      Originally posted by TheBlackCat View Post
                      There are release schedules for a reason. If someone want to add new features or fixes for old bugs, there is a time for that. -rc4 isn't it. I am sure reasonable exceptions can be made, but it seems like Linus feels the DRM people are abusing the process and just outright ignoring the schedule, and I don't think that is okay. The whole point of an RC cycle is to test things, and you can't test things properly if they keep changing.
                      RCs are in fact the time and place for all sorts of bug fixes, not just those which concern code added by that particular merge window. However, in this case it seems the kexec fix was deemed inappropriate due to its size, risk of introducing other bugs or simply because it did not or would not get enough testing before the release.

                      Or at least that's my guess, since the LKML thread itself isn't particularly enlightening and might give the wrong impression. Have a look at the actual patch and Dave's 2nd reply after the merge request, where he says that approach might not be the best anyway.

                      Comment


                      • #12
                        Originally posted by sandy8925 View Post
                        I have a question, any one know what that radeon kms fix was for?
                        kexec. Which basically loads a new kernel into memory and executes it. The whole idea is so somewhat nutty as lots of devices have dma in progress. So the fix was to disable certain GPU features that use dma early in the driver init process so that any previously active operations from before kexec will hopefully be stopped before the driver gets a chance to set up the hardware again.

                        Comment

                        Working...
                        X