EXA/mixed: Don't clear deferred status of pixmaps if migration is limited.
* With optimized migration, only the pending damage region is synchronized for destination pixmaps. * Migration of source pixmaps can be limited to a bounding region. Signed-off-by: Michel Dänzer <daenzer@vmware.com> Acked-by: Maarten Maathuis <madman2003@gmail.com> Signed-off-by: Keith Packard <keithp@keithp.com>
This commit is contained in:
		
							parent
							
								
									90e6d93cf9
								
							
						
					
					
						commit
						661630f909
					
				| 
						 | 
				
			
			@ -112,7 +112,8 @@ exaDoMigration_mixed(ExaMigrationPtr pixmaps, int npixmaps, Bool can_accel)
 | 
			
		|||
	    pPixmap->devKind = pExaPixmap->fb_pitch;
 | 
			
		||||
	    exaCopyDirtyToFb(pixmaps + i);
 | 
			
		||||
 | 
			
		||||
	    if (pExaScr->deferred_mixed_pixmap == pPixmap)
 | 
			
		||||
	    if (pExaScr->deferred_mixed_pixmap == pPixmap &&
 | 
			
		||||
		!pixmaps[i].as_dst && !pixmaps[i].pReg)
 | 
			
		||||
		pExaScr->deferred_mixed_pixmap = NULL;
 | 
			
		||||
	}
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
		Reference in New Issue