Announcement

Collapse
No announcement yet.

Linux 2.6.36-rc1 Kernel Released

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

  • Linux 2.6.36-rc1 Kernel Released

    Phoronix: Linux 2.6.36-rc1 Kernel Released

    While no release announcement has yet to work its way onto the Linux Kernel Mailing List, the Linux 2.6.36-rc1 kernel was tagged last night in Git by Linus Torvalds. As we have already shared in a number of articles, the Linux 2.6.36 kernel delivers on an exciting number of new features and other improvements...

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

  • #2
    What bout "The Linux Desktop Responsiveness Patches" ?

    Comment


    • #3
      Originally posted by zoomblab View Post
      What bout "The Linux Desktop Responsiveness Patches" ?
      They are applied, see commit e31f3698cd3499e676f6b0ea12e3528f569c4fa3 in ChangeLog.

      Comment


      • #4
        r700 tiling support here we come!!!!!! w00t!

        Comment


        • #5
          No R800 DRM for 2d/3d accel? Sad

          Comment


          • #6
            It was in 2.6.35. Why so sad ?

            Comment


            • #7
              How badly does an rc1 kernel usually hurt when it misbehaves? I crave those drm and responsiveness improvements...

              Comment


              • #8
                What's the deal with the Maverick kernels lately. It seems like a lot of them are failing to build.

                Comment


                • #9
                  Originally posted by bridgman View Post
                  It was in 2.6.35. Why so sad ?
                  The sad part is that it has been in the kernel for so long and nobody, but a few people at AMD can make use of it. So everybody else just ignores it and it's possible that the code has bitrotted in the meantime.

                  Comment


                  • #10
                    Didn't 2.6.35 just get released ? How could the code have possibly bitrotted ?

                    We always need a kernel driver before we can develop & test the userspace code -- the only difference is that this time we pushed out the kernel code early so people would be able to pick up the userspace code without having to build their own kernel.

                    Comment


                    • #11
                      For instance someone posts a patch to fix some problem in the drm for r600/r700, that patch could possibly also apply to Evergreen drm code, but the Evergreen drm code for some reason is not updated. Result: Bug fixed in r600/r700, bug still present in Evergreen.

                      Comment


                      • #12
                        Sure, I guess that could happen in theory, but nearly all of the 6xx/7xx drm patches came from agd5f, who is actively testing/fixing the Evergreen code as well.

                        Comment


                        • #13
                          Originally posted by korpenkraxar View Post
                          How badly does an rc1 kernel usually hurt when it misbehaves? I crave those drm and responsiveness improvements...
                          worst case was the corrupting of firmware for a specific network card, leaving the computer with no network.
                          http://lwn.net/Articles/300202/
                          there was a workaround fairly quickly, and the true cause was eventually found
                          http://lwn.net/Articles/303390/
                          and it was possible to re-upload the firmware in most cases. i think only a very small number of people were effected, you won't find more than a couple of angry rants (compared to hundreds when ubuntu moved the window buttons).

                          the odds of this kind of thing are very small. a more likely, but still rare possibility is filesystem corruption bug. as long as you have a backup you should be fine.

                          Comment


                          • #14
                            Anyone know if Ubuntu is going to switch from 2.6.35 to 2.6.36 with Maverick (10.10) or not?

                            Comment


                            • #15
                              Originally posted by monraaf View Post
                              For instance someone posts a patch to fix some problem in the drm for r600/r700, that patch could possibly also apply to Evergreen drm code, but the Evergreen drm code for some reason is not updated. Result: Bug fixed in r600/r700, bug still present in Evergreen.
                              For instance someone on a forum has no clue what they are talking about?

                              Dave.

                              Comment

                              Working...
                              X