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 Benchmarking Platform
Phoromatic Test Orchestration

Why Wayland & Weston Were Forked

Scott Moreau

Published on 29 March 2013
Written by Scott Moreau
Page 1 of 4 - Add A Comment

Last week, Wayland/Weston was forked by a long-time contributor, Scott Moreau. The fork of the Wayland/Weston display server ended up becoming known as Northfield/Norwood, following disagreements within the Wayland development camp. Scott Moreau was ultimately banned from the Wayland mailing list and IRC channel, so he's written an exclusive, independent article for Phoronix to explain his actions and why he felt a fork of the Wayland display server protocol and the reference Weston compositor were necessary.

Northfield/Wayland Split - Technical Aspects

Since there are many interested parties involved here, I spent some time assembling this writeup. I would like to change the tune to more positive notes that intend to introduce insight and reason into the picture. Since my actions inadvertently caused a significant disturbance, I feel that I owe it to everyone to explain the technical problems from my point of view. I would like other people to understand the problem as well and see how they might solve it, given the pertinent details. This an involving issue touching on many technical details. This is my attempt to fully explain the issues to all audiences.

It is noteworthy that these views are my own and may not be completely correct. I do not know everything nor do I claim to. There's nothing wrong with being wrong about a technical understanding. In fact, voicing ideas can be a good thing, because it encourages others with further insight, to share their knowledge and start a productive conversation. I will try to explain this in basic and technical terms as best I can.

First, we need to talk a bit about how wayland, weston and wayland clients work together to form a composited image.

Definitions:
- Wayland Display: wl_display: The core global object. A pointer to a wl_display. Used for internal wayland interfaces.
- Wayland Buffer: wl_buffer: The contents of a wl_surface.
- Wayland Surface: wl_surface: This is an image that is displayed on the screen. It has a location, size and pixel contents.
- Wayland: The term Wayland in this context implies two closely related things:
1) A wayland protocol
2) An implementation of this protocol in C
- Weston: The official wayland reference compositor. This is the program that represents the core compositing program
- surface: The term 'surface' is used here to denote 'an application window'

In order for clients to render their content into wayland composited surfaces, it needs to do a few things.

At a basic high level of abstraction these are:

1) Connect to the wayland wl_display - Using wl_display_connect().
2) Create a wl_buffer in which to render content - Buffer creation method varies by type.
3) Draw something - Typically using cairo or GL (though client rendering is not restricted to any specific method).
4) Tell the compositor to show the wl_surface - This is handled by the compositor and shell plugin.
5) Repaint the surface and notify the compositor that the rendering has finished - this can be done by calling wl_surface_damage(), wl_surface_attach() and finally wl_surface_commit() as the sync point. In the EGL case, eglSwapBuffers() uses these specific wayland calls from mesa internally to 'refresh' the surface.
6) Repeat step 5) as necessary for the life of the program.

The compositing program then takes all of these surfaces and paints them to a final buffer that is suitable for output.

The primary argument against the need for a fork is one that sounds reasonable at first:

Why not just fork the shell plugin alone?

This was a suggestion given by many. An example representation of such reasoning can be found in this wayland-devel mailing list post: "What you could aim instead is a new tree with your own shell plugin and stack over the core protocol another high level surface protocol."

Latest Linux News
  1. Phoronix Test Suite 5.8 Milestone 5 Brings Near Final "Belev" Experience
  2. For AMD Users, Linux 4.2 Will Bring The New AMDGPU Driver & VCE1 For Radeon
  3. Atomic Mode-Setting Still Baking For Samsung's Exynos DRM Driver
  4. Ubuntu Phone Update This Month Brings Many Improvements
  5. Fedora's "Fedup" To Be Replaced In Fedora 23
  6. Android M Should Bring Greater Performance & Efficiency
  7. AMD Teases Upcoming Radeon "Fiji" GPU Launch
  8. Dell Makes An Ubuntu Installation Guide, Suggests Users Try It Out
  9. Running Linux On The Intel Compute Stick
  10. AMD Launches The A10-7870K "Godavari" APU
Latest Articles & Reviews
  1. Opening The Gates To Our Daily Open-Source Linux Benchmark Results
  2. The Latest Features For Linux Performance Management + Benchmark Monitoring
  3. Noctua NH-U12DX i4 + NF-F12
  4. Btrfs RAID 0/1 Benchmarks On The Linux 4.1 Kernel
Most Viewed News This Week
  1. The Linux 4.0 EXT4 RAID Corruption Bug Has Been Uncovered
  2. NVIDIA's Proprietary Driver Is Moving Closer With Kernel Mode-Setting
  3. Systemd 220 Has Finally Been Released
  4. Zapcc Claims To Be A "Much Faster C++ Compiler"
  5. LibreOffice 5.0 Beta 1 Released
  6. OpenWRT 15.05 Preparing Improved Security & Better Networking
  7. Features Added To Mesa 10.6 For Open-Source GPU Drivers
  8. Ubuntu's LXD vs. KVM For The Linux Cloud