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

Wayland Looks To Do Multi-Monitor The Right Way

Wayland

Published on 09 February 2011 10:42 PM EST
Written by Michael Larabel in Wayland
37 Comments

Two weeks ago the hot discussion item being talked about by those interested in the Wayland Display Server was how to handle input with Wayland (e.g. using X Input, create a separate "Inland" input project, or designing something entirely different). The new subject now brought up on the Wayland mailing list is how to handle multiple monitor support. Fortunately, it looks like Kristian plans to implement multiple monitor/display support in a different -- and better -- way than how it's dealt with by the X.Org Server.

The multi-monitor topic was brought up by Marty Jack after he wrote a patch that allocates the CRTCs to avoid black screens on multiple monitors. Up to this point, Kristian Høgsberg, the creator of Wayland, hasn't really said how he would like support for multiple monitors to be implemented. That changed though this afternoon. In Marty's email, he mentions, "I don't know what Kristian's ultimate vision of this is. Do we allow windows to move like they do now on a virtual desktop where you can slide one to a RightOf monitor by dragging it and it appears part on one and part on the other? A lot of the data structure and processing change for multiple monitors would depend on whether it is possible to have one pair of big FBs added to both CRTCs at the same time, with different (x,y,w,h) if it is tiled and the same (x,y) if it is cloned or how he would want to handle this case [moving the rbo, fb_id, image up to drm_compositor]. With some philosophical guidance I could get the underpinnings in place."

AMD's Alex Deucher was the first to respond with his thoughts. "The sensible way to handle this is one surface per crtc otherwise we run into the same problems we hit with X where a multi-head desktop is too wide for the render/texture limits of the hardware."

Kristian then officially said, "As Alex says, the plan is to have one fb per crtc. The compositor will render the scenegraph into two framebuffers which we will then page flip to each crtc. Eventually we'll only rerender the parts that change so that typically we'll only update the fb where something changed."

For anyone dependent upon multiple displays on their desktop or other systems, this is great news and should be better than the support offered by the X.Org Server and its antiquated code. Only updating the portions of the screen where there's damage / changed contents is a win for performance/efficiency and as said by having one frame-buffer per CRTC will allow multiple displays to be powered without hitting any rendering limitations imposed by having a single frame-buffer spanning multiple CRTCs/displays.

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. Linux Compiler Benchmarks Of LLVM Clang 3.5 vs. LLVM Clang 3.6-rc1
  2. Intel Broadwell HD Graphics 5500: Windows 8.1 vs. Linux
  3. Linux Benchmarks Of NVIDIA's Early 2015 GeForce Line-Up
  4. NVIDIA GeForce GTX 960: A Great $200 GPU For Linux Gamers
  5. Disk Encryption Tests On Fedora 21
  6. Xonotic 0.8 Performance With The Open-Source AMD/NVIDIA Gallium3D Drivers
Latest Linux News
  1. Linux 3.19-rc6 Kernel Released: LInux 3.19 Final In Two Weeks
  2. Ubuntu's Mir Gains Server-Side Platform Probing
  3. Broadwell Linux Ultrabook Running MUCH Cooler Than Haswell
  4. LZHAM 1.0 Lossless Data Compression Codec Released
  5. LibreOffice 4.4 Is Coming Soon With New Features
  6. Linux Users Upset By Chromium's Busted HiDPI Support
  7. BPF Backend Merged Into LLVM To Make Use Of New Kernel Functionality
  8. Dying Light Is Headed To Linux, SteamOS
  9. Wayland 1.6.1 & Weston 1.6.1 Released
  10. Mesa 10.4.3 Brings A Bunch Of Fixes For The Direct3D "Nine" Support
Most Viewed News This Week
  1. Windows 10 To Be A Free Upgrade: What Linux Users Need To Know
  2. Google Admin Encourages Trying Btrfs, Not ZFS On Linux
  3. TraceFS: The Newest Linux File-System
  4. My Initial Intel Broadwell Linux Experience With The ThinkPad X1 Carbon
  5. Mozilla's Servo Still On Track For 2015 Alpha Release
  6. Fedora 23 Likely To Pursue Wayland By Default
  7. Keith Packard Leaves Intel's Linux Graphics Work
  8. A Proposal To Go 64-bit Only With Fedora 23