[Mesa-dev] [PATCH] r600: fork and import gallium/radeon

[Grazvydas Ignotas]

Has anyone ran full piglit on these with r600? Copy-paste bugs are
very easy to introduce.

Gražvydas

On Mon, Sep 18, 2017 at 7:32 PM, Marek Olšák <maraeo at gmail.com> wrote:
> Latest version with an updated commit message:
> https://cgit.freedesktop.org/~mareko/mesa/commit/?h=master&id=8671613ed19586ac1eceda48eb067a416f9c93be
>
> Marek
>
> On Mon, Sep 18, 2017 at 6:18 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
>> On 18 September 2017 at 17:08, Marek Olšák <maraeo at gmail.com> wrote:
>>> On Thu, Sep 14, 2017 at 4:52 PM, Nicolai Hähnle <nhaehnle at gmail.com> wrote:
>>>> On 14.09.2017 16:19, Emil Velikov wrote:
>>>>>
>>>>> Hi Marek,
>>>>>
>>>>> On 14 September 2017 at 14:06, Marek Olšák <maraeo at gmail.com> wrote:
>>>>>>
>>>>>> From: Marek Olšák <marek.olsak at amd.com>
>>>>>>
>>>>>> This marks the end of code sharing between r600 and radeonsi.
>>>>>>
>>>>> It has the "what" but it's missing the "why". Can you please add some
>>>>> information.
>>>>
>>>>
>>>> Basically, it's getting difficult to work on radeonsi without breaking r600.
>>>>
>>>> It's not ideal, but (1) without a solid testing infrastructure that tests
>>>> all the way back to r600, this is a reasonable measure to reduce the
>>>> development risk, and (2) with some rare exceptions, our work on radeonsi
>>>> tends not to help r600, neither in performance nor in features (and least of
>>>> all bug fixes).
>>>>
>>>> I haven't looked at the patch itself yet, but I'm okay with the general
>>>> idea.
>>>
>>> Does it mean I can push this?
>>>
>> I've got a local implementation that I'm fuzzing as we speak.
>> Can you please give me a bit of time to check for explosions.
>>
>> Meanwhile if someone can provide something we could add in the commit
>> message ("why") that will be appreciated.
>>
>> -Emil
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev