xorg Digest, Vol 25, Issue 89

[Michel Dänzer]

On Fri, 2007-08-24 at 12:50 +0300, Jarno Manninen wrote:
> Quoting Michel Dänzer <michel at tungstengraphics.com>:
> 
> > Hmm, I guess the only thing preventing that is that EXA calculates
> > pExaPixmap->fb_size assuming the bpp is the same as in system RAM...
> 
> That one is easy to fix, but real solution might require some  
> additional field in the ExaPixmap struct to track the sys/fb  
> depths/formats. Also any migration between sys and fb should take care  
> of the correct transformation.

The driver can handle all that.


> > Hmm, I think it might be possible to get at least some of the same
> > benefits by just tracking damage for FB and SYS separately and only
> > transferring regions between them that are actually needed for the
> > operation at hand... interesting food for thought.
> 
> Obvious benefit over using only one damage area is that for off-screen  
> pixmaps the drawing operations could be accumulated until the blit to  
> visible area. Uploading after every operation (like I'm doing now)  
> might cause unnecessary uploads.

Right.


-- 
Earthling Michel Dänzer           |          http://tungstengraphics.com
Libre software enthusiast         |          Debian, X and DRI developer