Page 2 of 6 FirstFirst 1234 ... LastLast
Results 11 to 20 of 54

Thread: Whoops, There's A Big Problem For Wayland GTK+

  1. #11
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,778

    Default

    Quote Originally Posted by Nille View Post
    And how old is this statement? One or two years?
    Somewhere around that. If Wayland ends up being adopted as the new standard for Linux, then I'm not sure what will happen to the binary drivers. Doesn't Wayland require DRI2 and/or Gallium3D? If yes, Catalyst also doesn't support it.

  2. #12
    Join Date
    Jul 2008
    Location
    Germany
    Posts
    623

    Default

    Quote Originally Posted by RealNC View Post
    Doesn't Wayland require DRI2 and/or Gallium3D? If yes, Catalyst also doesn't support it.
    My last information is that wayland need only egl and something similar to KMS.

  3. #13
    Join Date
    Dec 2011
    Posts
    144

    Default

    Quote Originally Posted by RealNC View Post
    Somewhere around that. If Wayland ends up being adopted as the new standard for Linux, then I'm not sure what will happen to the binary drivers. Doesn't Wayland require DRI2 and/or Gallium3D? If yes, Catalyst also doesn't support it.
    AFAIK Gallium isn't a requirement, KMS and EGL however are. This means Wayland is a big no-no on binary blobs. KMS won't be easy for nvidia to implement in their binary blob (anyone remember the mess when OSS drivers became KMS enabled?). Another hard requirement for Wayland is EGL support, which I don't know if the binary blobs support. AMD has the upper hand here with their OSS driver.
    Quote Originally Posted by 85c51 View Post
    they will probably support it once it gets more traction
    That is vey wishful thinking. Both companies have repeatedly said that their binary blobs target mainly Workstations. Wayland is meant for desktops/embedded. If OSS drivers die, so does the Linux desktop.

  4. #14
    Join Date
    Jun 2010
    Location
    ฿ 16LDJ6Hrd1oN3nCoFL7BypHSEYL84ca1JR
    Posts
    1,020

    Default

    That's a problem?

    Does that mean that gtk 3.4 will actually compile against wayland git libraries? And does that mean that cairo gl actually works with wayland now?

  5. #15
    Join Date
    Jun 2010
    Location
    ฿ 16LDJ6Hrd1oN3nCoFL7BypHSEYL84ca1JR
    Posts
    1,020

    Default

    Right now wayland + weston with mesa git and stable cairo without gl and egl is very broken. Wayland-terminal crashes after inputting some characters or selecting something with the mouse, weston will crash after about 2 minutes of usage..

  6. #16
    Join Date
    Jan 2009
    Posts
    1,591

    Default

    Quote Originally Posted by Serafean View Post
    That is vey wishful thinking. Both companies have repeatedly said that their binary blobs target mainly Workstations. Wayland is meant for desktops/embedded. If OSS drivers die, so does the Linux desktop.

    what stops wayland from being used in workstations.

    ubuntu will switch to wayland at some point and i am pretty sure the blob people will support it (at least i hope amd will )

  7. #17
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,778

    Default

    There's also the question of licensing. If the kernel does not provide non-GPL symbols for the KMS interface, then it effectively disallows the blobs to do KMS. But that's an "if", I don't actually know.

    In general, KMS in the blobs doesn't sound impossible. They would need glue in form of a kernel module with the actual functionality being provided by the blob.

  8. #18
    Join Date
    Jan 2009
    Posts
    1,591

    Default

    Quote Originally Posted by RealNC View Post
    There's also the question of licensing. If the kernel does not provide non-GPL symbols for the KMS interface, then it effectively disallows the blobs to do KMS. But that's an "if", I don't actually know.

    In general, KMS in the blobs doesn't sound impossible. They would need glue in form of a kernel module with the actual functionality being provided by the blob.
    wayland can work with openWF which i think is something similar to KMS and can be implemented without licensing concerns

    might be wrong though

  9. #19
    Join Date
    Apr 2010
    Posts
    1,946

    Default

    Quote Originally Posted by kraftman View Post
    I don't see how this is a problem for Wayland gtk+. It's problem for buggy nvidia blob. I hope nobody will wait for nvidia to support Wayland. It will be another reason to use AMD (if Catalyst won't have any problems).
    Masterpiece of sarcasm

  10. #20
    Join Date
    Nov 2008
    Location
    Germany
    Posts
    5,411

    Default

    Quote Originally Posted by crazycheese View Post
    Masterpiece of sarcasm
    only because you buy a nvidia card?

Posting Permissions

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