Announcement

Collapse
No announcement yet.

The Main DRM Pull Request For The Linux 2.6.37 Kernel

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

  • #11
    Originally posted by RealNC View Post
    I see. After the UMS->KMS thing, I thought with KMS most stuff happens in the kernel :P
    KMS only really moved modesetting and memory management. The 2D, 3D and video acceleration code all stayed in user space.

    Comment


    • #12
      I am quite impressed with all the DRM progress. It just a tad frustrating that only a few distros that either use a rolling release model like Arch or make it easy to compile your own kernel are able to provide users with some means of using an up-to-date kernel. I mean, F14 is not even out yet, but the kernel in it already seems dated in terms of graphics improvements, no?

      Comment


      • #13
        Originally posted by korpenkraxar View Post
        I am quite impressed with all the DRM progress. It just a tad frustrating that only a few distros that either use a rolling release model like Arch or make it easy to compile your own kernel are able to provide users with some means of using an up-to-date kernel. I mean, F14 is not even out yet, but the kernel in it already seems dated in terms of graphics improvements, no?
        You miss the point that Fedora ships a heavily patched kernel. Many of the upstream improvements in the mainline kernel are available in the Fedora kernel of older releases. And Fedora kernel gets rebased to upstream kernel in the lifecycle of one Fedora release.

        So you get the improments like in a rolling release, sometimes you have to wait a litte longer, but in many cases you get it actually earlier than with mainline kernel.

        Comment


        • #14
          Display watermarks? Like the "unsupported" watermark of fglrx?

          Comment


          • #15
            Watermarks are like DRM. There are good ones and bad ones.

            These watermarks are FIFO tuning parameters (imagine the FIFO being oriented vertically and your display data leaving stains on the side of the FIFO ).

            Comment


            • #16
              Originally posted by curaga View Post
              Display watermarks? Like the "unsupported" watermark of fglrx?
              not exactly

              Display watermarks control the display fifos and their priority in the memory controller. If it's not set up properly, you can get underflow to the display controller: the data from the memory controller doesn't arrive in time causing the fifo to run dry leading to flickering or other display artifacts.

              Comment

              Working...
              X