<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Apr 4, 2018 at 10:30 AM, Roland Scheidegger <span dir="ltr"><<a href="mailto:sroland@vmware.com" target="_blank">sroland@vmware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">Am 04.04.2018 um 05:42 schrieb Timothy Arceri:<br>
> On 04/04/18 13:22, Roland Scheidegger wrote:<br>
>> Am 04.04.2018 um 05:03 schrieb Timothy Arceri:<br>
>>> On 04/04/18 12:44, Roland Scheidegger wrote:<br>
>>>> Am 04.04.2018 um 04:32 schrieb Timothy Arceri:<br>
>>>>> On 04/04/18 11:58, Roland Scheidegger wrote:<br>
>>>>>> AFAIK these filters (and I've never looked into them) should be<br>
>>>>>> transparent to hw drivers. Hence a cap bit doesn't make sense, and if<br>
>>>>>> it's broken we shouldn't just paper over this.<br>
>>>>><br>
>>>>> I created a CAP because the AMD devs have no interest in supporting<br>
>>>>> this<br>
>>>>> feature [1]. Even if they are transparent to drivers I don't see why<br>
>>>>> drivers should be forced to enable them if they don't want to. CCing<br>
>>>>> Marek for his opinion.<br>
>>>><br>
>>>> I still don't see why using cap bits for bugs is a good idea.<br>
>>><br>
>>> Well I see it as a CAP for an unwanted feature that just happens to not<br>
>>> work currently.<br>
>>><br>
>>>> (Even more so if the bug actually would be in the postprocess, but I've<br>
>>>> no idea there really.)<br>
>>><br>
>>> It's crashing in src/gallium/drivers/radeonsi/<wbr>si_state_draw.c<br>
>><br>
>> Doesn't necessarily mean the bug is in the driver.<br>
>> Not sure it's really worth fixing it this way neither - people are<br>
>> probably just as confused why pp won't work than they are if it's<br>
>> crashing...<br>
><br>
> Well I can either update the webpage to say its disabled for radeonsi or<br>
> I can close the bugs as won't fix and let people wonder why its crashing<br>
> potentially filling another bug report. The first bug was filed a year<br>
> ago and nobody seems to want to fix it. Either way I don't care to much<br>
> but disabling the feature seems like a better way to go than just<br>
> letting it crash forever.<br>
<br>
</div></div>Alright, if the bug is that old I suppose there's really no interest in<br>
actually fixing it...<br>
So I suppose that would be an improvement...<br></blockquote><div><br></div></div>I've just fixed it. The patches are on the ML.<br><br></div><div class="gmail_extra">Marek<br></div></div>