[PATCH 1/5] wined3d: Don't bother about client storage in wined3d_surface_set_mem.

Stefan Dösinger stefandoesinger at gmail.com
Fri Oct 4 10:37:47 CDT 2013

Am 04.10.2013 um 17:15 schrieb Henri Verbeet <hverbeet at gmail.com>:
> I guess that makes it ok in practice, but I'd still feel happier about
> this kind of patch if we actually enforced resource access flags
> first. (At which point you could also just check the access flags
> instead of the pool.)
My plan is to enforce this in resource_load_location similar to how it's currently done for volumes. That'd be at the end of my surface cleanup patchset though, and it'll need some additional work (downloading a texture to a bigger sysmem surface to handle get_front_buffer_data).

I think my surface patches should work ok without the assumption that client storage and user memory are mutually exclusive, so feel free to skip this patch for now. The other 4 patches in this series should work ok. Some later patches in the big patchset need minor adjustments though.

More information about the wine-devel mailing list