On Thu, Mar 31, 2016 at 10:35:11AM +0100, Daniel Stone wrote: > Well, it has to be one or the other: mixing explicit and implicit, > defeats the purpose of using explicit fencing. So, when explicit > fencing is in use, implicit fences must be ignored. You can mix it, if you're careful. CrOS wants that to better mesh android with Ozone, and we'll be discussing what needs to be added to be able to make it work implicit and explicit fencing work together, in both directions. Of course this should only be used for shared buffers, e.g. explicit syncing in an android client running on top of implicitly synced ozone/kms. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
