On 17-01-31 13:03:52, Jason Ekstrand wrote:
On Wed, Jan 25, 2017 at 10:36 AM, Pohjolainen, Topi <
topi.pohjolai...@gmail.com> wrote:
On Mon, Jan 23, 2017 at 10:21:46PM -0800, Ben Widawsky wrote:
> This patch provides the support (and comments) for allocating the BO
> with space for the CCS
This patch shouldn't actually do anything because the libdrm function
should already do this alignment. However, it preps us for a future
patch where we add in the CCS AUX size, and in the process it serves as
a good place to find bisectable issues if libdrm or kernel does
something incorrectly.
On 06/02/17 03:48 PM, Yu, Qiang wrote:
>
> Dose this mean if the amdgpu_dri.so is compatible with GBM DRI backend,
> it will also compatible with libGL.so and xserver libglx.so (do these use
> same loader/DRI-ABI as GBM DRI backend)?
Yes, they do.
--
Earthling Michel Dänzer |
Dose this mean if the amdgpu_dri.so is compatible with GBM DRI backend,
it will also compatible with libGL.so and xserver libglx.so (do these use
same loader/DRI-ABI as GBM DRI backend)?
Regards,
Qiang
From: Michel Dänzer
Sent:
On 17-01-25 20:53:44, Topi Pohjolainen Topi Pohjolainen wrote:
On Mon, Jan 23, 2017 at 10:21:43PM -0800, Ben Widawsky wrote:
Make the code only disable CCS when it has to, unlike before where it
disabled CCS and enabled it when it could. This is much more inline with
how it should work in a few
On 06/02/17 02:58 PM, Yu, Qiang wrote:
>
>> * The ImgTec guys were able to tweak their binary which combined with
>> a bit of mesa glue produces a DRI module.
>> This in itself lead of a number of nice improvements and fixes that
>> landed in Mesa. Have you/others considered that option ?
> [yuq]
+ David
Hi Emil,
> * With the discussion(s) about liballoc/libgbm2 in motion wouldn't it
> be better to focus/target it ?
[yuq] I think this small improvement won't conflict with libgbm2 work
which is not my current focus. My purpose is getting current mesa co-exist
with amdgpu-pro. BTW. will
Thanks Nicolai, I'll address the gbmint.h and ABI version next version.
Regards,
Qiang
From: Nicolai Hähnle
Sent: Tuesday, January 24, 2017 6:12:06 PM
To: Yu, Qiang; mesa-dev@lists.freedesktop.org
Subject: Re: [Mesa-dev] [PATCH] gbm:
On 17-01-31 12:54:33, Jason Ekstrand wrote:
On Wed, Jan 25, 2017 at 10:58 AM, Pohjolainen, Topi <
topi.pohjolai...@gmail.com> wrote:
On Mon, Jan 23, 2017 at 10:21:41PM -0800, Ben Widawsky wrote:
> This provides a common function or creating miptrees when there is an
> existing DRIimage to use.
https://bugs.freedesktop.org/show_bug.cgi?id=99591
Petr Cervinka changed:
What|Removed |Added
CC||p...@cervinka.net
--
On 17-01-31 13:01:11, Jason Ekstrand wrote:
On Mon, Jan 23, 2017 at 10:21 PM, Ben Widawsky wrote:
Since the code doesn't support modifiers yet, this patch should do
nothing other than prepare for more patches.
Signed-off-by: Ben Widawsky
Acked-by:
On 17-01-31 12:10:11, Jason Ekstrand wrote:
On Mon, Jan 23, 2017 at 10:21 PM, Ben Widawsky wrote:
This patch begins introducing how we'll actually handle the potentially
many modifiers coming in from the API, how we'll store them, and the
structure in the code to support
The idea behind modifiers like this is that the user of GBM will have
some mechanism to query what properties the hardware supports for its BO
or surface. This information is directly passed in (and stored) so that
the DRI implementation can create an image with the appropriate
attributes.
A
On 17-01-31 11:52:38, Jason Ekstrand wrote:
On Mon, Jan 23, 2017 at 10:21 PM, Ben Widawsky wrote:
The idea behind modifiers like this is that the user of GBM will have
some mechanism to query what properties the hardware supports for its BO
or surface. This information is
Unlike stride, there was no previous offset getter, so it can be right
on the first try.
v2: Return EINVAL when plane is greater than total planes to make it
match the similar APIs.
Avoid leak after fromPlanar (Daniel)
Make sure when getting offsets we consider dumb images (Daniel)
v3: Use
v2: Preserve legacy behavior when plane is 0 (Jason Ekstrand)
EINVAL when input plane is greater than total planes (Jason Ekstrand)
Don't leak the image after fromPlanar (Daniel)
Move bo->image check below plane count preventing bad index succeeding (Daniel)
v3: Fix DRIimage leak (using Jason's
From: Dave Airlie
This fixes the vulkan samples deferredmultisampling test.
Cc: "17.0"
Signed-off-by: Dave Airlie
---
src/amd/common/ac_nir_to_llvm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
Reviewed-by: Edward O'Callaghan
On 02/06/2017 05:53 AM, Andres Gomez wrote:
> The binding point is a valid layout qualifier for Uniform Blocks,
> Shader Storage Blocks and Opaque-Uniforms.
>
> From page 60 (page 66 of the PDF) of the GLSL 4.20 spec, v11:
>
> " A
Thanks Rob for your inputs. Yes, you are looking at the right place. But
the HiKey which takes same pbuffer path and it working with Mali is the
reference now. I'm trying to write a simple egl app that uses pbuffer to
confirm the support with Mesa. Does it sounds correct or you have any
One more point is westeros always return null window for offscreen target,
that why WPE falls back to pbuffer on HiKey and DB410c cases.
On 3 February 2017 at 11:30, Sivasubramanian Patchaiperumal <
sivasubramanian.patchaiperu...@linaro.org> wrote:
> Thanks Rob for your inputs. Yes, you are
Hi,
Back in 2012-2013, then-Intel employees Eric Anholt and Paul Berry
wrote this threaded GL dispatch where GL calls are queued and executed
in a different thread. It was supposed to deal with high CPU overhead
of Mesa, but at the time most games used the compatibility profile and
Steam didn't
https://bugs.freedesktop.org/show_bug.cgi?id=97967
--- Comment #11 from Timothy Arceri ---
FRom the gentoo bug:
"This only happens with ABI_X86=32, the test passes for native abi."
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA
On 17-01-31 12:38:44, Jason Ekstrand wrote:
On Mon, Jan 23, 2017 at 10:21 PM, Ben Widawsky wrote:
Replace the naive, 'save all the modifiers' with a proper query for just
the modifier that was selected. To accomplish this, two new query tokens
are added to the extension:
https://bugs.freedesktop.org/show_bug.cgi?id=99591
--- Comment #3 from Petr Cervinka ---
(In reply to Vedran Miletić from comment #1)
> Can you try newer vulkaninfo? Some segfaults were fixed recently.
I tested it on openSUSE with vulkan info 1.0.39.1, but the results are the
The binding point is a valid layout qualifier for Uniform Blocks,
Shader Storage Blocks and Opaque-Uniforms.
From page 60 (page 66 of the PDF) of the GLSL 4.20 spec, v11:
" A link error will result if two compilation units in a program
specify different integer-constant bindings for the
Everything should be ready to go on maxwell as well, but the sched code
calculator ends up causing a lot of failures with the generated code.
Since this is a fringe feature, leave it out until the sched code logic
is improved.
Signed-off-by: Ilia Mirkin
---
Unfortunately there is no SHF.L/SHF.R instruction pre-SM35. So we have
to do a bit more work to get the job done.
Signed-off-by: Ilia Mirkin
---
.../nouveau/codegen/nv50_ir_lowering_nvc0.cpp | 68 --
1 file changed, 62 insertions(+), 6 deletions(-)
Note that this is not available for SM20/SM30.
Signed-off-by: Ilia Mirkin
---
src/gallium/drivers/nouveau/codegen/nv50_ir.h | 1 +
.../drivers/nouveau/codegen/nv50_ir_emit_gk110.cpp | 24 +-
.../drivers/nouveau/codegen/nv50_ir_emit_gm107.cpp | 52
Signed-off-by: Ilia Mirkin
---
.../drivers/nouveau/codegen/nv50_ir_from_tgsi.cpp | 222 -
.../nouveau/codegen/nv50_ir_lowering_nvc0.cpp | 67 ++-
.../nouveau/codegen/nv50_ir_lowering_nvc0.h| 2 +
From: Pierre Moreau
Hardware does not support 64-bit integers MAD and MUL operations, so we need
to transform them in 32-bit operations.
Signed-off-by: Pierre Moreau
---
.../drivers/nouveau/codegen/nv50_ir_peephole.cpp | 116
We were never emitting a .X flag for consuming condition code on SET,
and weren't emitting a signed type for SLCT comparison. Discovered while
working on int64 logic.
Signed-off-by: Ilia Mirkin
---
src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gk110.cpp | 4
These operations allow you to compute min/max on arbitrary-width
integers, 32 bits at a time.
Note that the low/med ops implicitly set the condition code, and the
med/high ops implicitly consume it.
Signed-off-by: Ilia Mirkin
---
Nouveau does not currently have logic to implement this as a library
function. Even though such a library could be written, there's no big
advantage to do it that way for now given that int64 is a very uncommon
use-case. Allow a driver to expose INT64 without supporting division and
modulo
https://bugs.freedesktop.org/show_bug.cgi?id=97879
andrei.demin1...@gmail.com changed:
What|Removed |Added
CC||andrei.demin1...@gmail.com
Hi,
On 4 February 2017 at 05:29, Ben Widawsky wrote:
> On 17-01-31 11:33:39, Jason Ekstrand wrote:
>> On Mon, Jan 23, 2017 at 10:19 PM, Ben Widawsky wrote:
>>> + /* Preserve legacy behavior if plane is 0 */
>>> + if (plane == 0)
>>> + return
On 02/03/2017 07:48 PM, Bas Nieuwenhuizen wrote:
On Fri, Feb 3, 2017, at 19:24, Jason Ekstrand wrote:
On Fri, Feb 3, 2017 at 9:23 AM, Samuel Pitoiset
> wrote:
This is similar to the MESA_GLSL_VERSION_OVERRIDE envvar (mainly
On 02/03/2017 07:24 PM, Jason Ekstrand wrote:
On Fri, Feb 3, 2017 at 9:23 AM, Samuel Pitoiset
> wrote:
This is similar to the MESA_GLSL_VERSION_OVERRIDE envvar (mainly
for developers). But this one has the advantage to be
From what I understand this series is,
Reviewed-by: Edward O'Callaghan
A few rather trivial style bits to be fixed pertaining of
space before '(', e.g., 'if(..)' -> 'if ('.
On 02/05/2017 10:43 PM, Bas Nieuwenhuizen wrote:
> This implements the sparseBinding feature
Per the Vulkan spec, memory objects may be deleted before the buffers
and images using them are deleted, although those resources then
cannot be used except for deletion themselves.
For the virtual buffers, we need to access them on resource destruction
to unmap the regions, so this results in a
Signed-off-by: Bas Nieuwenhuizen
---
src/amd/vulkan/radv_device.c | 75 +---
1 file changed, 71 insertions(+), 4 deletions(-)
diff --git a/src/amd/vulkan/radv_device.c b/src/amd/vulkan/radv_device.c
index 1e92046d62c..d501be3793f 100644
Signed-off-by: Bas Nieuwenhuizen
---
src/amd/vulkan/radv_image.c | 23 +--
src/amd/vulkan/radv_private.h | 1 +
2 files changed, 22 insertions(+), 2 deletions(-)
diff --git a/src/amd/vulkan/radv_image.c b/src/amd/vulkan/radv_image.c
index
Signed-off-by: Bas Nieuwenhuizen
---
src/amd/vulkan/radv_device.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/src/amd/vulkan/radv_device.c b/src/amd/vulkan/radv_device.c
index d501be3793f..4db58929a42 100644
---
Signed-off-by: Bas Nieuwenhuizen
---
src/amd/vulkan/radv_device.c | 7 +--
src/amd/vulkan/radv_radeon_winsys.h | 1 +
src/amd/vulkan/radv_wsi.c | 3 ++-
src/amd/vulkan/winsys/amdgpu/radv_amdgpu_cs.c | 12
4
Signed-off-by: Bas Nieuwenhuizen
---
src/amd/vulkan/radv_radeon_winsys.h | 5 +
src/amd/vulkan/winsys/amdgpu/radv_amdgpu_bo.c | 218 +++---
src/amd/vulkan/winsys/amdgpu/radv_amdgpu_bo.h | 35 -
src/amd/vulkan/winsys/amdgpu/radv_amdgpu_cs.c |
If we had submitCount >0, but each submit had zero command buffers,
then we still wouldn't signal the fence.
Signed-off-by: Bas Nieuwenhuizen
---
src/amd/vulkan/radv_device.c | 18 +-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git
Signed-off-by: Bas Nieuwenhuizen
---
src/amd/vulkan/radv_device.c | 22 --
src/amd/vulkan/radv_private.h | 1 +
2 files changed, 21 insertions(+), 2 deletions(-)
diff --git a/src/amd/vulkan/radv_device.c b/src/amd/vulkan/radv_device.c
index
This implements the sparseBinding feature radv. The feature name is a misnomer,
as all the resources still have to be completely backed by memore. However,
that can be done independently of descriptor generation, so we have to work
with blocks of address space already.
This feature does not need
https://bugs.freedesktop.org/show_bug.cgi?id=99517
Mark Janes changed:
What|Removed |Added
Depends on|96907 |
Referenced Bugs:
48 matches
Mail list logo