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

  • The Main DRM Pull Request For The Linux 2.6.37 Kernel

    Phoronix: The Main DRM Pull Request For The Linux 2.6.37 Kernel

    David Airlie has just called upon Linus Torvalds to pull in his DRM kernel tree for the Linux 2.6.37 kernel merge window. We have talked about many of these features before that are now entering the mainline Linux kernel code-base as new capabilities of the open-source Linux graphics stack, but here's the list of what made the cut for Linux 2.6.37 and details on some of the features we have yet to discuss...

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

  • agd5f
    replied
    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.

    Leave a comment:


  • bridgman
    replied
    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 ).

    Leave a comment:


  • curaga
    replied
    Display watermarks? Like the "unsupported" watermark of fglrx?

    Leave a comment:


  • Lynxeye
    replied
    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.

    Leave a comment:


  • korpenkraxar
    replied
    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?

    Leave a comment:


  • bridgman
    replied
    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.

    Leave a comment:


  • Ragas
    replied
    Originally posted by RealNC View Post
    I see. After the UMS->KMS thing, I thought with KMS most stuff happens in the kernel :P
    So, don't you think it's a good thing if most things are done in kernel now .... and all those things are already done?!

    Leave a comment:


  • nanonyme
    replied
    Originally posted by RealNC View Post
    I see. After the UMS->KMS thing, I thought with KMS most stuff happens in the kernel :P
    I think Linus would have had a few objections if it was like that.

    Leave a comment:


  • RealNC
    replied
    I see. After the UMS->KMS thing, I thought with KMS most stuff happens in the kernel :P

    Leave a comment:

Working...
X