Announcement

Collapse
No announcement yet.

Wayland, Weston 0.95 Pre-Release Is Available

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

  • Wayland, Weston 0.95 Pre-Release Is Available

    Phoronix: Wayland, Weston 0.95 Pre-Release Is Available

    In preparation for the Wayland/Weston 0.95 release in early July, a pre-release is now available (v0.94.90) that gets ready for this important milestone...

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

  • #2
    Does this means that when the v1.0 is out we can start using it instead of xorg ? (For the applications and DE that support it of course).

    One last question, does Wayland support natively a solution to make Optimus work ?

    Comment


    • #3
      Originally posted by aliasbody View Post
      Does this means that when the v1.0 is out we can start using it instead of xorg ? (For the applications and DE that support it of course).

      One last question, does Wayland support natively a solution to make Optimus work ?
      Wayland should make life easier for Bumblebee, no more. There is no such thing called native solution to support Nvidia Optimus in Linux unless Nvidia decides to open their drivers or alike. And in their latest response to Linus Trovald, they confirmed that they're not willing to open anything but have their own philosophy on how to support Linux. That's a petty.

      Comment


      • #4
        I run Rawhide so I have had wayland packages installed on my system for quite a while. But up to now we haven't had weston available. I just checked and I see it is now available as well. Though only at version 89-0.4. When I installed it it pulled in libxkbcommon so it looks like it has keyboard support. Good progress.

        My question now is how do I make the pieces work? In this first round does X still start and then kick off wayland? Do we start wayland and then it calls X as needed? Is there a startW? Can any one point me at some docs that will help me try and cobble this together? I know it is still a work in progress but dang I'm the kind of person that just needs to look, touch and feel. Thanks.

        Comment


        • #5
          Originally posted by Hanynwosky View Post
          Wayland should make life easier for Bumblebee, no more. There is no such thing called native solution to support Nvidia Optimus in Linux unless Nvidia decides to open their drivers or alike. And in their latest response to Linus Trovald, they confirmed that they're not willing to open anything but have their own philosophy on how to support Linux. That's a petty.
          It is not a bad news after all... I mean it can be worse... I prefer have direct access to my Nvidia using bumblebee, than doing that with virtualgl :S.. Correct me if I'm wrong.

          Comment


          • #6
            Weston still does not have --version or --help parameters. Nor does it have a manpage.

            You can try Weston in Ubuntu 12.10 alpha, but it only have one application, some terminal.
            Also, I just managed to run it under a window in X, not by itself.
            So not very useful yet.

            Also the mouse cursor lags while running Weston under a virtual machine.

            Comment


            • #7
              The Wayland mailing list is quiet the last few days, I wonder why.

              Comment


              • #8
                Originally posted by mark45 View Post
                The Wayland mailing list is quiet the last few days, I wonder why.
                I guess most of them are just testing the code or try to port the client libraries (like gtk, it doesn't use the new shm pool) and the likes.

                Comment


                • #9
                  multi-monitor support?

                  i am constantly disappointed by the multi-monitor support in gnome or kde. i am certain that most of the developers never see more than one monitor and definitely never more than two. what kind of support will wayland have for multi-monitor setups?

                  Comment


                  • #10
                    Originally posted by mtk0 View Post
                    i am constantly disappointed by the multi-monitor support in gnome or kde.
                    What exactly are you missing?

                    Comment


                    • #11
                      well, really X and KDE

                      i use four screens. i have an nvidia display adapter. thus i am forced to use the proprietary driver since nouveau only supports two. (i know that is not the nouveau developer's fault - they aren't given the specs by nvidia). nvidia's adapter is really two separate chips
                      bonded together on one card. hence, xinerama is necessary to tie them all together.
                      as a result, the notion of 'maximized window boundary' is screwed up. windows
                      maximize to *two* screens (because of twinview). and there is no option to maximize to all four screens. i'd prefer the options of maximizing to one, two, and four physical screens (or at least one and four). and, of course, there is no XRANDR because of the xinerama. KDE's (kwin's) support of multiple monitors is lacking, probably for similar under-the-cover reasons. panels can't span across the xinerama-linked displays. with four screens, i use the two outer screens to display various forms of monitoring/status info. i use the two inner screens as a work area for development/editing/other tasks. ideally i'd like the panel to stretch across the two inner panels, but that is impossible. and, of course, none of the whiz-bang transparent animated window stuff works at all. in fact, with this setup, setting input focus takes realtime *seconds* (i'm using click to focus). this is on a box with 16G of ram and an 8 core xeon chip. this *has* to be kwin's fault.

                      Comment


                      • #12
                        Originally posted by aliasbody View Post
                        Does this means that when the v1.0 is out we can start using it instead of xorg ? (For the applications and DE that support it of course).

                        One last question, does Wayland support natively a solution to make Optimus work ?
                        Whether you can use Weston instead of (or below) an X server depends on what you can live without. We will see what that is exactly.

                        Wayland 1.0 means that the core protocol and C library API are set in stone, and other software can rely on them. It does not mean anything about feature parity with X, nor how well compositors work, nor how well toolkits work. In fact, it does not mean much directly for an end user. However, it does mean, that Wayland will no longer be a running target, it will be more like a walking target. It becomes much more unlikely for changes in Wayland to break any existing software that was once made to work with it. That means that toolkit and desktop developers can concentrate their efforts in implementing more features, instead of continuously playing catch-up with Wayland.

                        Wayland is not a silver bullet to Optimus, and plays a tiny role there, if any. The hard part is in the drivers and the graphics infrastructure. Not having to re-architect huge chunks of the X server helps, though. Except people will probably do that anyway.

                        Comment


                        • #13
                          Originally posted by mark45 View Post
                          The Wayland mailing list is quiet the last few days, I wonder why.
                          The weekend was Midsummer's Eve, a national drinking holiday in most of the Nordics.

                          Comment


                          • #14
                            And probably some people noticed:
                            Code:
                             ~ % weston
                            Date: 2012-06-26 CEST
                            [22:37:31.714] weston 0.94.90
                                           http://wayland.freedesktop.org/
                                           Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=weston
                                           Build: 0.94.90 configure.ac: Bump version to 0.94.90 (2012-06-25 21:35:42 -0400)
                            [22:37:31.714] OS: Linux, 3.5.0-1-mainline, #1 SMP PREEMPT Tue Jun 26 08:17:19 UTC 2012, x86_64
                            [22:37:31.714] fatal: environment variable XDG_RUNTIME_DIR is not set.
                            Refer to your distribution on how to get it, or
                            http://www.freedesktop.org/wiki/Specifications/basedir-spec
                            on how to implement it.
                            Well, look, what the spec says.
                            Originally posted by http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
                            If $XDG_RUNTIME_DIR is not set applications should fall back to a replacement directory with similar capabilities and print a warning message.
                            A fatal error is not in the sense of that.


                            At least some minimal documentation would be really appreciated. How would you run xwayland? What do I do if my mouse pointer is invisible? How would I change the resolution of one screen or rotate one screen or change the mode from expanded desktop to clone or something other (i.e. an equivalent to xrandr)? What hotkeys are there? And with minimal I really mean minimal, e.g. in list form.

                            Comment


                            • #15
                              If any one is interested this is pretty good documentation.

                              http://wayland.freedesktop.org/docs/html/index.html

                              Comment

                              Working...
                              X