Is this problem specific to the extension or is it a general problem? Would there not be the same issue if the session compositor wasn't using the extension but was creating textures from the client surfaces instead? Presumably if cards A and B don't share a tiling mode then it won't be possible for card B to make a texture out of buffers created on card A either.
My assumption was that if you have successfully created an EGLImage out of the client's surface then it is a valid buffer for that EGL context. Perhaps this situation should be detected in eglCreateImage rather than in eglCreateWaylandBufferFromImage. I apologise in advance if I've misunderstood the problem. Regards, - Neil Axel Davy <[email protected]> writes: > I think there is a problem with tiling handling in your patch. > > Thinks of a session compositor running on an other graphic card for example. > > > Main compositor: card A > session compositor: card B. buffer is shared between A and B and when > creating it, tiling was disabled (because A and B share no tiling mode) > clients in the session compositor: card B. buffer is created on B, when > creating it, tiling was enabled. > > In this configuration, your function should fail or do a copy (because A > won't recognize the tiling mode of B) > > Axel Davy --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
