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 Linux Hardware Reviews
  1. ASRock X99 Extreme3 Is An Affordable Choice For Linux Users
  2. A Walkthrough Of The New 32 System Open-Source Linux Benchmarking Test Farm
  3. Habey MITX-6771: Mini-ITX Board With Quad-Core J1900 Bay Trail
  4. OCZ Vector 150 SSD On Linux
Latest Linux Articles
  1. 2014 Year-End NVIDIA Linux Benchmark Comparison
  2. 2014 Catalyst Linux Graphics Benchmarks Year-In-Review
  3. 17-Way Linux Graphics Card Comparison With Civilization Beyond Earth
  4. AMD Kaveri: Open-Source Radeon Gallium3D vs. Catalyst 14.12 Omega Driver
Latest Linux News
  1. Biggest Linux Kernel Features & Work Of 2014
  2. Valve Optimizations, D3D9 & GL4 Topped Mesa This Year
  3. Minetest 0.4.11 Released As Open-Source Alternative To Minecraft
  4. SPI Hasn't Yet Voted On X.Org As An Associated Project
  5. The Most Controversial Systemd Stories This Year
  6. Mode-Setting Driver Now Supports VBlanks With Present
  7. Marvell Releases New Open-Source 802.11ac WiFi Driver
  8. The Most Popular Ubuntu News Of 2014
  9. GNU Binutils 2.25 Released With Port To Andes NDS32
  10. Merry Christmas & Happy Holidays 2014
Latest Forum Discussions
  1. Why is it that Radeon cannot run good old (ancient) Doom 3 engine games?
  2. MONITORed values : possible to force the time interval between two measurements ?
  3. Debian init discussion in Phoenix Wright format
  4. Need some hand holding with upgrading xserver
  5. Aliens vs predator for Linux
  6. FPS capped on Linux (AMD fglrx drivers)
  7. Speeding up systemd networking service
  8. Storm Engine 2 (Doom 3 BFG GPL fork) got entry on IndieDb