Lines Matching refs:PrepareAccess

18593     create and destroy a damage in PrepareAccess. The destroy path can then
98368     exa: Only call driver FinishAccess hook if PrepareAccess hook succeeded.
117228     Turns out this is still necessary if the driver PrepareAccess hook succeeds.
121114     but use pPixmap->devPrivate.ptr after PrepareAccess instead.
121204     EXA: Extend mixed pixmaps scheme to allow driver PrepareAccess hook to fail.
121206     If the PrepareAccess hook fails, use the DownloadFromScreen hook to retrieve
121214     CPU, this can be handled between the PrepareAccess and
121217     * Radeon KMS on big endian machines can fail PrepareAccess if the pixmap
121220       Here the driver PrepareAccess hook will always fail and leave all transfers
121223     Drivers which can handle all pixmaps in the PrepareAccess hook should notice
122645     Otherwise we may incorrectly clobber it to NULL on repeated PrepareAccess
125283     Also update the Doxygen documentation for the PrepareAccess driver hook to
132544     pixmaps at PrepareAccess time.
143704     - I guess failing PrepareAccess is rare, since this a 3 year old bug.
178510         after the drawing is done. Previously, a failed PrepareAccess could
178538     Document the restriction on PrepareAccess() failure, from discussion with
181765     Add a pair of hooks, PrepareAccess() and FinishAccess(), which get called