ProcPutImage calls exaDoMoveOutPixmap, 4x slowdown

[Maarten Maathuis]

On Tue, Oct 14, 2008 at 6:00 PM, Clemens Eisserer <linuxhippy at gmail.com> wrote:
> Hi,
>
>> I think this is because intel does not provide an UploadToScreen hook
>> (because it has no vram). It hasn't made (visible) effort to
>> reintegrate UXA in EXA,
> Btw. I was using EXA without GEM.
> Has the UploadToScreen hook been removed when preparing the driver for
> UXA and/or GEM?
> One thing which puzzles me, if the intel-driver does not define
> UploadToScreen, how can pixmaps end in "vram" at all, or are there
> other, slower paths which take care of this in that case?
>
> Thanks a lot, Clemens
> _______________________________________________
> xorg mailing list
> xorg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xorg
>

There is ofcource a fallback system, which is pretty much a memcpy.
intel has never had an UploadToScreen hook. I'm just mentioning uxa,
because they did realize exa wasn't perfect for them (in it's current
form), they just haven't fixed exa yet to be a little more smart for
non-vram cards.