>I was planning to change platform_wayland.c not to use _DRI_IMAGE_USE_SHARE
>when self sharing. But after looking more closely, it seems that
>PIPE_BIND_SHARED
>would be necessary for gallium drivers for self-sharing too.
>
>Since we want to enable tiling when we use self-sharing, my patch isn
> On Mon, Aug 12, 2013 at 3:05 PM, Marek Olšák wrote:
>> On Mon, Aug 12, 2013 at 11:36 PM, Stéphane Marchesin
>> wrote:
Other than hybrid systems (of which
there are none with i915 graphics), is there any case where
__DRI_IMAGE_USE_SHARE can occur?
>>>
>>> You could do interesti
> On 08/11/2013 03:50 AM, davya...@free.fr wrote:
>>> This looks good to me, but commit messages should have a prefix
>>> indicating which component is changed. In your case it's "gallium:"
>>> and "intel:", respectively.
>>>
>>> Marek
>>
>>
>> Ok, I've suppressed some trailing spaces and changed
>This looks good to me, but commit messages should have a prefix
>indicating which component is changed. In your case it's "gallium:"
>and "intel:", respectively.
>
>Marek
Ok, I've suppressed some trailing spaces and changed the commit message.
>From f48fdb44d638ae850c7f3df36211b33788088927 Mon
Hello,
To enable using prime on Wayland, we need to have a way to create shareable
textures.
That's the purpose of __DRI_IMAGE_USE_SHARE and PIPE_BIND_SHARED, but these
flags don't
disable tiling. This patch change the behaviour of these flags so that they
disable tiling.
Disabling tiling is n
