1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

Defining Wayland & Its Input System Are Discussed

Wayland

Published on 28 January 2011 12:49 AM EST
Written by Michael Larabel in Wayland
2 Comments

If you have any interest at all in the technical side of the Wayland Display Server, there's been two mailing list threads in particular worth paying attention to this week. One is about proposals for Wayland's input system an the other is in terms of defining a Wayland implementation.

The most recent input discussion for Wayland was initiated by Canonical's Chase Douglas by proposing (in this message) to design an input system that is backwards compatible with previous input systems, can be developed to work along with X, and can be integrated into the same display server source code. Chase expressed interest in separating the input system entirely from the display system via what would be a new project called "Inland" or the like. But that separation was quickly shut down by some, like Intel's Jesse Barnes, for overly complicating the matter and causing other engineering headaches. This matter is still being discussed.

The other thread worth reading was started by Tiago Vignatti and is entitled wayland implementation conformance. This thread was born out of Kristian making the following comment:
Once of the things that X got right was the extension model. Wayland takes it one step further by making everything an extension: the only thing that's fixed in the Wayland protocol is an interface for discovering other interfaces. If it turns out that we need to update the input model, we have versioning built in for incremental updates, and we can add an entire new model if we need to start from scratch.

So what exactly defines a Wayland implementation? Kristian's answer is below, but this thread is still being discussed with various thoughts being expressed among interested contributors.
That's a good question. My intention is to have wayland.xml be the official interfaces, but you're right that the drm interface is specific to the Linux drm driver model and maybe that should be split out into its own file. Additionally, it would make sense to abstract out the wl_buffer creation into a library that server and client can link to so that not every toolkit and application that use the wayland protocol directly will have to know about every driver specific interface for creating and sharing buffers.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Articles & Reviews
  1. Ubuntu vs. Fedora Linux On Lenovo's X1 Carbon With Core i7 Broadwell
  2. Ubuntu 15.04 Is The Easy Path To Better Performance On Intel Broadwell
  3. NVIDIA's Latest Maxwell Line-Up Against AMD With Catalyst On Linux
  4. Preliminary Tests Of Intel Sandy Bridge & Ivy Bridge vs. Broadwell
  5. AMD FX-8320E Performance On Linux
  6. Linux Compiler Benchmarks Of LLVM Clang 3.5 vs. LLVM Clang 3.6-rc1
Latest Linux News
  1. Free Software Foundation Endorses Another (Outdated) Laptop
  2. DNF Plugins Extend The Functionality Of Fedora's Yum Successor
  3. LibreOffice 4.4 Released With Better OOXML Support, UI Improvements
  4. Inkscape 0.91 Goes Through C++ Code Conversion, New Cairo Rendering, OpenMP Filters
  5. New Mesa Patch To Improve CPU-Bound Applications
  6. LLVM Adds Options To Do Fuzz Testing
  7. Coreboot Now Supports Another Dual-Socket AMD Motherboard
  8. Atomic Mode-Setting/Display Support Progresses In Linux 3.20
  9. NVIDIA 340.76 Brings Three Stable Fixes
  10. Intel Broadwell-U P-State vs. ACPI CPUFreq Scaling Linux Performance
Most Viewed News This Week
  1. PlayStation 4 System Compiler Support Landing In LLVM
  2. LibreOffice 4.4 Is Coming Soon With New Features
  3. Linux "GHOST" Vulnerability Hits Glibc Systems
  4. My Initial Intel Broadwell Linux Experience With The ThinkPad X1 Carbon
  5. Broadwell Linux Ultrabook Running MUCH Cooler Than Haswell
  6. LZHAM 1.0 Lossless Data Compression Codec Released
  7. Linux Users Upset By Chromium's Busted HiDPI Support
  8. Interstellar Marines On Linux With Catalyst: Bull S*#@