You really need double-buffering to let the app or desktop manager draw complete frames without ending up displaying a half-redrawn screen and allow whole frames to be flipped in when complete.
*IF* your app/DE never redraws the screen but just makes a series of changes to small parts while leaving the rest unchanged you can get away with limiting drawing operations to a small part of the vertical refresh period, but AFAIK apps & DE's are less likely to work like that every year.
Because not using a compositor in X works, right now.My point was that if you don't want to use a compositor, then why even bother with graphics at all. Forget using Wayland or X and just use the console.
With the scanline wait, there can still be a tearing effect between different parts of the screen which are updated separately.
Also, the scanline wait stalls the entire graphics pipeline. In extreme cases such as e.g. glxgears running fullscreen, this means the pipeline can effectively only run during the vertical blank interval, even for things not directly related to glxgears.
A sophisticated compositor such as Weston allows eliminating tearing completely while using the full graphics pipeline throughput.
Plus, with a compositor, you can pageflip which saves memory bandwidth over a blit.
Last edited by agd5f; 02-11-2013 at 11:16 AM.
No code for/discussion about Richland APU's (the successor to the current Trinity APU's)? Supposedly they will be launched on March 19th 2013 and apparently will be built with Piledriver cores and HD8000 graphics cores while maintaing the same TDP. Does anyone know if any of this is true?
Just noticed that the article links the just-released driver support for Oland to an HD 8800-series part, presumably based on September 2012 rumours which described Oland as a 3.4 billion transistor upper-midrange part.While AMD has yet to officially introduce their Radeon HD 8000 series, published today was the initial open-source Linux graphics driver support for handling the Radeon HD 8800 "Oland" graphics cards.
AMD's been planning for a second quarter release of the Radeon HD 8000 "Sea Islands" GPUs while the first to arrive hardware will be the HD 8800 "Oland" graphics processors. This hardware that succeeds the Radeon HD 7000 series isn't as radically different as going from the HD 6000 to HD 7000 series, which yielded a better turnaround time with the initial HD 8000 series support.
Oland is actually a 6 CU part (ie same ALU count as the GPU on Trinity, but GCN rather than VLIW4). See Anandtech description of Oland/Mars :
Oland : http://www.anandtech.com/show/6570/a...eries-for-oems
Mars : http://www.anandtech.com/show/6571/a...n-8000m-series
The "Oland" support we pushed recently was for the HD 85xx/86xx OEM and mobile parts announced in January, not for "HD 8800".
MrCooper, agd5f, thanks for the clarification.