On Oct 28, 2016 3:30 AM, "Michel Dänzer" <<a href="mailto:michel@daenzer.net">michel@daenzer.net</a>> wrote: > > On 28/10/16 03:08 AM, Marek Olšák wrote: > > On Thu, Oct 27, 2016 at 5:23 PM, Emil Velikov <<a href="mailto:emil.l.velikov@gmail.com">emil.l.velikov@gmail.com</a>> wrote: > >> On 17 October 2016 at 10:37, Marek Olšák <<a href="mailto:maraeo@gmail.com">maraeo@gmail.com</a>> wrote: > >>> Reverting the whole commit is too much. You can just remove the PIPE BIND > >>> SHARED usage if you need to. > >>> > >> I'd imagine that one wants to check if radeon(s) behave OK with the > >> flag dropped ? Thus it might be better for someone with radeon HW to > >> give it a bash. > >> Can we have a volunteer please :-) > > > > r600-radeonsi ignore PIPE_BIND_SHARED on textures. > > That doesn't mean the state tracker can just drop PIPE_BIND_SHARED. Actually, the flag should be removed from Gallium completely, because it serves no purpose. All textures can be shared. Always. Marek > > <a href="https://patchwork.freedesktop.org/patch/110569/">https://patchwork.freedesktop.org/patch/110569/</a> seems the best candidate > for resolving the nouveau issue, but I suspect as is it might break DRI3 > PRIME. Nayan, can you check this and fix it up as necessary? Basically, > PIPE_BIND_LINEAR is only really necessary for buffers which are sent to > the X server for presentation on a different GPU. > > > -- > Earthling Michel Dänzer | <a href="http://www.amd.com">http://www.amd.com</a> > Libre software enthusiast | Mesa and X developer