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

Thread: Wayland Updated With KMS Page-Flipping Ioctl

  1. #1
    Join Date
    Jan 2007
    Posts
    14,627

    Default Wayland Updated With KMS Page-Flipping Ioctl

    Phoronix: Wayland Updated With KMS Page-Flipping Ioctl

    The Wayland Display Server hasn't received any new commits to its code repository since early October, but now it has received some new work. In particular, Wayland is now able to take advantage of the KMS page-flipping ioctl that was recently pushed into the Linux 2.6.33 kernel. The latest Wayland code now takes advantage of the latest revision to this API and is also now dependent upon libdrm 2.4.17, which was just released this week...

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

  2. #2
    Join Date
    May 2008
    Posts
    598

    Default

    I wonder what Red Hat's stands are on Wayland?

    What I think of is, if they would include it in Fedora for people to try just for fun?

  3. #3
    Join Date
    Dec 2009
    Posts
    12

    Default

    Can we expect a Qt Wayland backend, or is Cairo the primary (and only) goal for the moment? Given that Qt is fully open source now, some enthusiast could well try and hack up a backend. Or will Qt use Cairo (impossible, IMHO)?

  4. #4
    Join Date
    Sep 2007
    Location
    Edmonton, Alberta, Canada
    Posts
    117

    Default

    Quote Originally Posted by Louise View Post
    What I think of is, if they would include it in Fedora for people to try just for fun?
    If someone (you?) packages it, then I don't see why not

  5. #5
    Join Date
    May 2008
    Posts
    598

    Default

    Quote Originally Posted by hubick View Post
    If someone (you?) packages it, then I don't see why not
    hehe =)

  6. #6
    Join Date
    Nov 2009
    Posts
    91

    Default

    Quote Originally Posted by thorgt View Post
    Can we expect a Qt Wayland backend, or is Cairo the primary (and only) goal for the moment? Given that Qt is fully open source now, some enthusiast could well try and hack up a backend. Or will Qt use Cairo (impossible, IMHO)?
    From what I've read, I think the aim is for Qt and GTK and anything else useful to be able to run on Wayland, but it will take a lot of work and at the moment there just isn't anyone working on it. There was a Clutter backend developed, I'm not sure what the status of that is.

    This article says that a GTK backend is planned: http://www.phoronix.com/scan.php?pag...item&px=NzEzNQ

    Qt running on Wayland would be awesome though
    Last edited by ad_267; 12-21-2009 at 03:45 PM.

  7. #7
    Join Date
    Feb 2008
    Posts
    210

    Default

    So what about X11? I did read Gallium(3D or now's more than just 3D?) is going to implement X11 in it as well OpenGL, OpenVG and other undergoing implementations.

    Does this mean a giant buch of LOC (lines of code) aka Xorg can be replaced someday by a much tinier and compact codebase but equivalent in the important functionality (KISS principle)? So we don't need to wait for endless delays and tons of overbloated software, instead using just the kernel and OS resources for controlling and using the hardware.

    So Wayland will become part of a brilliant future of freedom and innovation in the FOSS graphics world or just a funny gimmick like Compiz?

    If Wayland implements Qt, GTK, WxWidgets and whatever is needed for end user... can be a real replacement of Xorg?

    Or maybe Wayland can became the next gen sucessor, and Xorg project adopting the codebase?
    Will we go to see a situation similar to Xfree vs Xorg, EGCS vs GCC, Beryl vs Compiz again?

  8. #8
    Join Date
    Jun 2007
    Location
    The intarwebs
    Posts
    385

    Default

    Quote Originally Posted by timofonic View Post
    So what about X11? I did read Gallium(3D or now's more than just 3D?) is going to implement X11 in it
    Please no please no please no pl..

    The X11 protocol is abysmal for desktop usage and should be retired at the earliest possible opportunity. Get the compiz devs and the gnome-globalmenu devs and the KDE and GNOME people and the folks at Google all in one place and start over.

  9. #9
    Join Date
    Apr 2008
    Location
    /dev/random
    Posts
    218

    Default

    Quote Originally Posted by timofonic View Post
    So what about X11? I did read Gallium(3D or now's more than just 3D?) is going to implement X11 in it as well OpenGL, OpenVG and other undergoing implementations.
    The xorg state tracker will provide EXA and Xv acceleration only.
    The is also a generic 2D driver being developed called xf86-video-modesetting which provides a DDX driver that uses KMS for modesetting and uses Gallium3D for acceleration

    Does this mean a giant buch of LOC (lines of code) aka Xorg can be replaced someday by a much tinier and compact codebase but equivalent in the important functionality (KISS principle)? So we don't need to wait for endless delays and tons of overbloated software, instead using just the kernel and OS resources for controlling and using the hardware.
    Wayland is not a drop-in replacement for X. It doesn't use the same protocol, so all window managers need to be re-written. All toolkits need to be able to use Wayland. All applications that use X libraries need to switch. However, with Wayland, it is possible to run an X-server inside of Wayland for backwards compatibility.

    So Wayland will become part of a brilliant future of freedom and innovation in the FOSS graphics world or just a funny gimmick like Compiz?

    If Wayland implements Qt, GTK, WxWidgets and whatever is needed for end user... can be a real replacement of Xorg?

    Or maybe Wayland can became the next gen sucessor, and Xorg project adopting the codebase?
    Wayland is entirely independent of Xorg, and does not use the X protocol, Xorg will never 'adopt' Wayland, but we may eventually see Wayland become the display server, and X only be developed for backwards compatibility with older applications.

    Will we go to see a situation similar to Xfree vs Xorg, EGCS vs GCC, Beryl vs Compiz again?
    These are entirely different things.
    Xorg was a fork off of Xfree86, and became widely used.
    Egcs was a fork off of gcc and gcc-derived projects, and became the official gcc.
    Beryl was a fork off Compiz, and it merged back together with Compiz.

    Wayland is not a fork off of Xorg, it is something different that can run Xorg inside of it.

  10. #10
    Join Date
    Feb 2008
    Posts
    210

    Default

    Quote Originally Posted by ethana2 View Post
    Please no please no please no pl..

    The X11 protocol is abysmal for desktop usage and should be retired at the earliest possible opportunity. Get the compiz devs and the gnome-globalmenu devs and the KDE and GNOME people and the folks at Google all in one place and start over.
    Well, it's OK. But what about remote desktop? I agree local access must use a lot less bloated way, but what protocol to use for remote graphical access?

    Of course, the successor must be as flexible or more like X11 and add features like Xaudio. If the protocol can be more efficient for slow internet connections and avoid the use of NX/FreeNX even better.

    Don't forget OpenGL, MPX-like stuff (multitouch)...

Posting Permissions

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