Page 5 of 6 FirstFirst ... 3456 LastLast
Results 41 to 50 of 54

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

  1. #41
    Join Date
    Jan 2011
    Posts
    1,287

    Default

    Quote Originally Posted by RussianNeuroMancer View Post
    They doesn't have reasons to flip us off because all needed stuff is already written, they just need to port it from embedded drivers to desktop drivers.
    They do have reasons, the main one would be they must pay for that porting, and it's not focused to their main target.

  2. #42

    Default

    Quote Originally Posted by mrugiero View Post
    They do have reasons, the main one would be they must pay for that porting, and it's not focused to their main target.
    Laptops with hybrid graphics is not main target for AMD, but they support it in fglrx, HTPC is not main target for nVidia, but they support HDMI audio bitstreaming. They already pay for support this and other features, even less important. Since Wayland is more important they will support it anyway.

  3. #43
    Join Date
    Jul 2008
    Location
    Germany
    Posts
    619

    Default

    Quote Originally Posted by RussianNeuroMancer View Post
    they just need to port it from embedded drivers to desktop drivers.
    In case of AMD the have an egl Implementation in the fglrx driver.

  4. #44

    Default

    Quote Originally Posted by Nille View Post
    In case of AMD the have an egl Implementation in the fglrx driver.
    Really? Bridgman say some time ago there is packaging problems with EGL in desktop driver. You mean desktop driver or embedded driver? Embedded driver have EGL, yes.

  5. #45
    Join Date
    Oct 2010
    Posts
    301

    Default

    5 pages of comments and nobody read/understood the article, the usual for Phoronix. Anyway, if anybody is interested in the real problem here is a summary:

    1. When building GTK+ with Wayland support memory usage will increase when running on regular X11, so it has nothing to do with nVidia supporting Wayland.

    2. This is because nVidia builds their drivers with position dependant code, which is slightly faster but can not be shared between different programs (so it gets duplicated for each program running that uses GTK+)

    3. It only happens for 32 bit applications, because the AMD64 architecture doesn't support shared libraries built with position dependant code so nVidia was forced to fix their 64 bit driver.

  6. #46
    Join Date
    Jul 2008
    Location
    Germany
    Posts
    619

    Default

    Quote Originally Posted by RussianNeuroMancer View Post
    Really? Bridgman say some time ago there is packaging problems with EGL in desktop driver. You mean desktop driver or embedded driver? Embedded driver have EGL, yes.
    I mean the desktop driver. since some time ago its in the fglrx.

  7. #47
    Join Date
    Oct 2008
    Posts
    3,012

    Default

    Quote Originally Posted by Ansla View Post
    3. It only happens for 32 bit applications, because the AMD64 architecture doesn't support shared libraries built with position dependant code so nVidia was forced to fix their 64 bit driver.
    I didn't realize point 3, that's an important note there. Who cares about 32 bit distros these days?

  8. #48
    Join Date
    Oct 2010
    Posts
    301

    Default

    Quote Originally Posted by smitty3268 View Post
    I didn't realize point 3, that's an important note there. Who cares about 32 bit distros these days?
    Well, since Ubuntu promoted the 32 bit version as the preferred one even on 64 bit hardware until now it's to be expected that a lot of Ubuntu users will continue using the 32 bit version for the next several releases. For the rest of the distros, indeed, 32 bit is a rarity. So maybe a better title for this article would have been "Whoops, There's A Big Problem For Ubuntu"

  9. #49
    Join Date
    Jun 2008
    Posts
    20

    Default

    My hope is that nVidia has a private branch where they hack on porting their drivers to all of the Linux techs it doesn't support, including Wayland, KMS, Gallium, et al and that this major reworking will also bring Optimus support &c. As this branch would currently be experimental, nVidia refuses to acknowledge any plans to support these officially since doing so may be considered binding.

    Also, hasn't there been a job opening for a Linux driver engineer on nvnews.net for like three or four years? Someone qualified should apply and fill that, maybe you can help get the support we need.

  10. #50
    Join Date
    Jul 2010
    Posts
    61

    Default

    Quote Originally Posted by scionicspectre View Post
    ....we may simply maintain X11 versions of everything until the situation changes, and allow users with other hardware to use Wayland and cairo-gl.
    That's the problem, it can't be done. cairo-gl cannot be packaged in a way that is usable for people using open source video drivers, without breaking X for everybody using the Nvidia proprietary drivers. At least using Debian packages, I don't know about others.

    So, to avoid breaking X for the people using Nvidia proprietary drivers, Ubuntu, for example, has disabled cairo-gl for everyone. After putting what looks like a lot of work into trying to find a better solution, and failing. And this is one of the things preventing GTK+ applications from being usable with wayland in Ubuntu 12.04 Precise (the other is a clipboard problem with multiple simultaneously enabled backends).

    I explained this in the post the article is based on. One of the possible solutions is adding flexibility to the way Debian packaging works. A Debian bug that's been open for 15 years.

Posting Permissions

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