From: Roland Scheidegger
Maybe upon a time it wasn't always true.
---
src/gallium/drivers/r600/r600_shader.c | 18 --
1 file changed, 18 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_shader.c
b/src/gallium/drivers/r600/r600_shader.c
index 06d7ca02e9..6cdbfd3063 100644
From: Roland Scheidegger
piglit doesn't care, but I'm quite confident that the size actually bound
as range should be reported and not the base size of the resource.
Also, the array in the constant buffer looks overallocated by a factor of 4.
For eg, also decrease the size by another factor of 2
https://bugs.freedesktop.org/show_bug.cgi?id=100430
freeb...@hoot.tech changed:
What|Removed |Added
CC||freeb...@hoot.tech
--
You are rece
https://bugs.freedesktop.org/show_bug.cgi?id=103852
freeb...@hoot.tech changed:
What|Removed |Added
CC||freeb...@hoot.tech
--
You are rece
DCC was disabled when the image format is !!supported, which is one ! too many.
Ironically the commit that introduced it was supposed to lead to more DCC use
...
Fixes: 969537d9358 "radv: Add support for more DCC compression with
VK_KHR_image_format_list."
---
src/amd/vulkan/radv_image.c | 2 +
Boris Brezillon writes:
> The V3D engine provides several perf counters.
> Implement ->get_driver_query_[group_]info() so that these counters are
> exposed through the GL_AMD_performance_monitor extension.
Thanks for working on this! I've successfully used it to inform some
work I'm doing on 3D
Mesa 17.2.8 is now available.
In this release we have:
The SPIR-V compiler has seen corrected a possible SEGFAULT.
The Intel i965 driver includes a correction for Haswell involving
doubles management.
The AMD drivers have also received some fixes. A couple have gone for
radv and radeon's VCE w
https://bugs.freedesktop.org/show_bug.cgi?id=104251
--- Comment #1 from Andreas Schultes ---
I did an apitrace and I have some gdb output:
p ctx->Texture.Unit[0]
$6 = {Enabled = 0, EnvMode = 8448, EnvColor = {0, 0, 0, 0},
EnvColorUnclamped = {0, 0, 0, 0}, GenS = {Mode = 9216, _ModeBit = 4,
I can confirm this fixes the 2000+ failures.
Tested-by: Rafael Antognolli
On Fri, Dec 22, 2017 at 01:54:08PM -0800, Anuj Phogat wrote:
> This reverts commit 9cd60fce9c22737000a8f8dc711141f8a523fe75.
> Above commit caused 2000+ piglit tests to assert fail. Disabling
> the align1 mode on gen10 for
This reverts commit 9cd60fce9c22737000a8f8dc711141f8a523fe75.
Above commit caused 2000+ piglit tests to assert fail. Disabling
the align1 mode on gen10 for now to avoid failures.
Cc: Matt Turner
Cc: Rafael Antognolli
Signed-off-by: Anuj Phogat
---
---
src/intel/compiler/brw_fs_generator.cpp |
On 2017-12-22 10:56 AM, Roland Scheidegger wrote:
Am 22.12.2017 um 01:41 schrieb Andres Rodriguez:
Calling this function will emit a semaphore signal operation into the
GPU's command stream.
Signed-off-by: Andres Rodriguez
---
src/gallium/docs/source/context.rst | 31 +
On Thu, Dec 21, 2017 at 6:21 AM, Ville Syrjälä
wrote:
> Here's a quick proof of concept implementation of HDR support
> for Wayland/Weston/Mesa.
>
> I'm not posting this as patches right now because I'm not sure
> that would do much good given how rough this is. But here are
> all the repos/branch
Hi
No I'm not using ICC however that section prevents you using Clang, it
basically says if not GCC then assumes Intel's compiler
Cheers
Mike
On Fri, 22 Dec 2017, 3:04 pm Mao, David, wrote:
> Hi Lothian,
> Thanks for testing out out driver!
> Officially we recommend you to stick to GCC5 for n
Am 22.12.2017 um 01:41 schrieb Andres Rodriguez:
> Calling this function will emit a semaphore signal operation into the
> GPU's command stream.
>
> Signed-off-by: Andres Rodriguez
> ---
> src/gallium/docs/source/context.rst | 31 +++
> src/gallium/include/pipe/p_con
https://bugs.freedesktop.org/show_bug.cgi?id=100613
--- Comment #48 from Emil Velikov ---
Stefan, we had a number of fixes in Mesa 17.2.1 and later that reference this
bug. Is it save to assume the original regression is resolved, should we close
this?
--
You are receiving this mail because:
Yo
Hi Lothian,
Thanks for testing out out driver!
Officially we recommend you to stick to GCC5 for now, however, we do have a fix
for the constexpr issue mentioned below that just didn’t make it to this first
release.
According to your diff, are you using ICC?
Could you let us know the compiler vers
https://bugs.freedesktop.org/show_bug.cgi?id=102904
Emil Velikov changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=103732
Emil Velikov changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=104351
--- Comment #3 from Emil Velikov ---
(In reply to Breno Souza from comment #2)
> Same error on fresh install. I have installed the following packages:
>
> base, base-devel, gnome, gnome-extra, freeglut, qt5-base, cower, pacaur,
> google-chrome
Congratulations on getting this out the door
It didn't compile for me without these changes:
In pal:
diff --git a/src/util/math.cpp b/src/util/math.cpp
index 46e9ede..3af4259 100644
--- a/src/util/math.cpp
+++ b/src/util/math.cpp
@@ -54,7 +54,7 @@ static uint32 Float32ToFloatN(float f, const
NBi
We are pleased to announce the initial release of AMD Open Source Driver for
Vulkan.
The AMD Open Source Driver for Vulkan is an open-source Vulkan driver for
Radeon graphics adapters on Linux. It is built on top of AMD's Platform
Abstraction Library (PAL), a shared component that is designed
On Fri, Dec 22, 2017 at 10:09 AM, Gurchetan Singh
wrote:
> So the plan is for alloc_handle_t to not be sub-classed by the
> implementations, but have all necessary information that an implementation
> would need?
>
> If so, how do we reconcile the implementation specific information that is
> ofte
On 21 December 2017 at 18:14, Rob Herring wrote:
> On Wed, Dec 13, 2017 at 5:02 PM, Gurchetan Singh
> wrote:
>> Hi Robert,
>>
>> Thanks for looking into this! We need to decide if we want:
>>
>> (1) A common struct that implementations can subclass, i.e:
>>
>> struct blah_gralloc_handle {
>>
Hi,
On 22.12.2017 11:42, Eero Tamminen wrote:
On 21.12.2017 22:19, Mark Janes wrote:
This patch doesn't apply to master as formatted.
It was against master. Could you try the attached patch instead?
Argh, I meant the patch attached to this mail. Sorry again.
- Eero
I assume I
Hi,
On 21.12.2017 22:19, Mark Janes wrote:
This patch doesn't apply to master as formatted.
It was against master. Could you try the attached patch instead?
I assume I had screwed something when I inlined it to my earlier mail. :-/
I've reverted the bisected commit, since it disables test
25 matches
Mail list logo
