On Thu, Apr 27, 2017 at 4:57 PM, Emil Velikov wrote:
> On 27 April 2017 at 11:52, Constantine Kharlamov wrote:
>> 27.04.2017, 13:26, "Emil Velikov" :
>>> Hi Constantine,
>>>
>>> I'm not familiar with r600, so mostly a drive-by idea/nit.
>>
>> I'm not familiar with graphics :P Well, perhaps a litt
On 27 April 2017 at 11:52, Constantine Kharlamov wrote:
> 27.04.2017, 13:26, "Emil Velikov" :
>> Hi Constantine,
>>
>> I'm not familiar with r600, so mostly a drive-by idea/nit.
>
> I'm not familiar with graphics :P Well, perhaps a little now.
>
>> On 25 April 2017 at 12:59, Constantine Kharlamov
27.04.2017, 13:26, "Emil Velikov" :
> Hi Constantine,
>
> I'm not familiar with r600, so mostly a drive-by idea/nit.
I'm not familiar with graphics :P Well, perhaps a little now.
> On 25 April 2017 at 12:59, Constantine Kharlamov wrote:
>
>> @@ -1746,45 +1747,47 @@ static void evergreen_emit_fr
Hi Constantine,
I'm not familiar with r600, so mostly a drive-by idea/nit.
On 25 April 2017 at 12:59, Constantine Kharlamov wrote:
> @@ -1746,45 +1747,47 @@ static void evergreen_emit_framebuffer_state(struct
> r600_context *rctx, struct r
> radeon_set_context_reg(cs, R_028E50_
Am Mittwoch, 26. April 2017, 19:48:46 CEST schrieb Constantine Kharlamov:
> On 26.04.2017 17:51, Marc Dietrich wrote:
> > Am Mittwoch, 26. April 2017, 16:36:39 CEST schrieb Constantine Kharlamov:
> >> HEAD recently have triggered a bug in sb compiler, so, just for the safe
> >> case, can you tell i
On 26.04.2017 17:51, Marc Dietrich wrote:
> Am Mittwoch, 26. April 2017, 16:36:39 CEST schrieb Constantine Kharlamov:
>> HEAD recently have triggered a bug in sb compiler, so, just for the safe
>> case, can you tell if reverting this commit
>>
>> git revert --no-commit eb8aa93c03ee89ffd3041d41b6293
Am Mittwoch, 26. April 2017, 16:36:39 CEST schrieb Constantine Kharlamov:
> HEAD recently have triggered a bug in sb compiler, so, just for the safe
> case, can you tell if reverting this commit
>
> git revert --no-commit eb8aa93c03ee89ffd3041d41b6293e4b282b6ce6
>
> but having my patch still appl
HEAD recently have triggered a bug in sb compiler, so, just for the safe case,
can you tell if reverting this commit
git revert --no-commit eb8aa93c03ee89ffd3041d41b6293e4b282b6ce6
but having my patch still applied changes anything or not?
(I have this commit reverted locally)
On 26.04.2017 17
Am Mittwoch, 26. April 2017, 16:16:35 CEST schrieb Constantine Kharlamov:
> Thank you for testing! What is "UH4" btw?
old GL3.3 benchmark Unigine Heaven 4.0
https://benchmark.unigine.com/heaven
Marc
>
> On 26.04.2017 17:03, Marc Dietrich wrote:
> > Am Dienstag, 25. April 2017, 13:59:44 CEST s
Thank you for testing! What is "UH4" btw?
On 26.04.2017 17:03, Marc Dietrich wrote:
> Am Dienstag, 25. April 2017, 13:59:44 CEST schrieb Constantine Kharlamov:
>> Split out of "avoid redundant CB register updates" for easier review.
>>
>> Signed-off-by: Constantine Kharlamov
>> Tested-by: Dieter
Am Dienstag, 25. April 2017, 13:59:44 CEST schrieb Constantine Kharlamov:
> Split out of "avoid redundant CB register updates" for easier review.
>
> Signed-off-by: Constantine Kharlamov
> Tested-by: Dieter Nützel
> ---
This one generates GPU crashes here (RS880) when running UH4:
radeon :
Split out of "avoid redundant CB register updates" for easier review.
Signed-off-by: Constantine Kharlamov
Tested-by: Dieter Nützel
---
src/gallium/drivers/r600/evergreen_state.c | 76 +++-
src/gallium/drivers/r600/r600_blit.c | 1 +
src/gallium/drivers/r600/r
12 matches
Mail list logo