Lines Matching refs:UploadToScreen

113617     EXA: Check sys_ptr isn't NULL before passing it to the UploadToScreen hook.
118711     EXA: Don't use UploadToScreen for CopyNtoN with mixed pixmaps.
121105     EXA: Fix mixed pixmaps crash with missing / failing UploadToScreen hook.
121109     UploadToScreen hook or provides one which can fail: There can be a crash
121194     EXA: Try to minimize UploadToScreen calls for mixed pixmaps.
121208     and copy the results back using the UploadToScreen hook. Use the classic
121215     DownloadFrom/UploadToScreen hooks, e.g.:
121218       requires byte-swapping and swap bytes in DownloadFrom/UploadToScreen.
121221       between GPU / CPU storage to the Download/From/UploadToScreen hooks.
125307     EXA: Bail earlier from exaDoPutImage if the driver has no UploadToScreen hook.
143487     exa: remove useless cache{X,Y}off from UploadToScreen() arguments.
148753     Track damage after using UploadToScreen directly.
148761     EXA: Use UploadToScreen() for uploads to glyph cache
148763     When possible, use UploadToScreen() rather than CompositePicture()
160647     UploadToScreen hook.
168233     Mark sync when UploadToScreen succeeds in exaGlyphs().
169354     This affects drivers with no UploadToScreen or UploadToScreen failures.
177205         with the scratch pixmap when we are able to do UploadToScreen
177840     - PutImage's UploadToScreen failure fallback failed to Prepare.
177976     Add an UploadToScreen implementation, for testing PutImage support, and
181100     Mark the temporary pixmap dirty if UploadToScreen succeeds. Failure to do
181615     Break EXA ABI while we still can. Add coordinates to the UploadToScreen
181617         drivers to respect that. Use this support to directly UploadToScreen in
190610     - Add a new UploadToScreen kaa hook for doing the actual moving of data to
190613     - Add an UploadToScreen on ATI which is just memcpy, but which will be