Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Weston DRM Compositor Support Proposed For NVIDIA's TK1

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

    Default Weston DRM Compositor Support Proposed For NVIDIA's TK1

    Phoronix: Weston DRM Compositor Support Proposed For NVIDIA's TK1

    Support for running Wayland's Weston compositor directly off the DRM kernel driver for the NVIDIA Tegra K1 SoC found within the Jetson TK1 development board has been proposed for mainline Weston...

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

  2. #2
    Join Date
    Dec 2009
    Posts
    353

    Default

    Does it all mean that we should expect tablets with TK1 and native Wayland running Plasma Active, Nemo, Sailfish and etc.?

  3. #3
    Join Date
    Mar 2012
    Posts
    29

    Default Weston DRM?

    I dont quite get it...
    Codethink rewrite Weston compositor, but instead of accessing KMS, it access DRM infrastructure?
    Whats that mean? Means that NVidia also can support Wayland in the same manner?
    Please, excuse my ignorance if Im saying too much non senses.

  4. #4
    Join Date
    Feb 2014
    Posts
    35

    Default

    Quote Originally Posted by rxonda View Post
    I dont quite get it...
    Codethink rewrite Weston compositor, but instead of accessing KMS, it access DRM infrastructure?
    Whats that mean? Means that NVidia also can support Wayland in the same manner?
    Please, excuse my ignorance if Im saying too much non senses.
    From having had a look at the patches, it seems they slightly modify the Weston DRM/KMS backend to support the mentioned device, which has to be handled in a different way than usual GPUs. I'm also not sure here, but I remember hearing that, while the GPU was under Nouveau territory, the display had to be handled with a different DRM driver - the Tegra. That may be the reason.

    As for the NVIDIA question, I believe not. NVIDIA's official driver does not use DRM nor KMS. Another backend for Weston would have to be developed to support whatever-NVIDIA-uses.

  5. #5
    Join Date
    Mar 2012
    Posts
    29

    Default

    Quote Originally Posted by kalrish View Post
    From having had a look at the patches, it seems they slightly modify the Weston DRM/KMS backend to support the mentioned device, which has to be handled in a different way than usual GPUs. I'm also not sure here, but I remember hearing that, while the GPU was under Nouveau territory, the display had to be handled with a different DRM driver - the Tegra. That may be the reason.

    As for the NVIDIA question, I believe not. NVIDIA's official driver does not use DRM nor KMS. Another backend for Weston would have to be developed to support whatever-NVIDIA-uses.
    thanks for the answer Kalrish.
    I googled for linux graphics stack and found out that NVidia cant implement a libdrm, unless they open sourced their code.

  6. #6
    Join Date
    May 2013
    Posts
    16

    Default

    is it about the nouveau driver? how much slower is this driver than the official nv driver? I hope if the official get weston support.

  7. #7
    Join Date
    Oct 2011
    Posts
    42

    Default

    How about MPG or H.264 acceleration on this box? E.g. VDPAU

  8. #8
    Join Date
    Oct 2011
    Posts
    42

    Default

    How about enclosures for this board?

  9. #9
    Join Date
    Oct 2008
    Posts
    3,176

    Default

    Quote Originally Posted by rxonda View Post
    thanks for the answer Kalrish.
    I googled for linux graphics stack and found out that NVidia cant implement a libdrm, unless they open sourced their code.
    NVidia (and fglrx) already have their own proprietary versions of libdrm/kms - so they just need to write a Wayland backend which can access it and then ship that with their drivers. It should all be fairly simple at this point, they just have to do it and then do all the regression testing necessary to make them feel comfortable supporting it.

  10. #10
    Join Date
    Mar 2012
    Posts
    29

    Default

    Quote Originally Posted by smitty3268 View Post
    NVidia (and fglrx) already have their own proprietary versions of libdrm/kms - so they just need to write a Wayland backend which can access it and then ship that with their drivers. It should all be fairly simple at this point, they just have to do it and then do all the regression testing necessary to make them feel comfortable supporting it.
    Thanks for the answer Smitty.
    But, when you mean "Wayland backend" you mean the compositor, right?
    If so, NVidia would have to provide the nvidia-mutter-wayland, nvidia-efl-compositor, nvidia-kwin-compositor and so on?
    And what about the optimus systems? It's up to the wayland client to choose the kms compositor or the nvidia compositor?
    Im a bit confuse...

Posting Permissions

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