On 05/04/2018 05:59 PM, Nanley Chery wrote:
On Fri, May 04, 2018 at 09:03:32AM +0300, Tapani Pälli wrote:
Hi Nanley;
Hey Tapani,
On 05/03/2018 10:03 PM, Nanley Chery wrote:
Before this patch, if we failed to initialize an MCS buffer, we'd
end up in a state in which the miptree thinks it h
From: Mathias Fröhlich
Instead of playing with Array._DrawArrays, make the feedback draw
path use Array._DrawVAO. Also st_RasterPos needs to use the VAO then.
v2: Use helper methods to get the offset values for array and binding.
Update comments.
Signed-off-by: Mathias Fröhlich
---
src/me
From: Mathias Fröhlich
Was meant to be temporary in gallium.
Signed-off-by: Mathias Fröhlich
---
src/mesa/state_tracker/st_cb_feedback.c | 32 ++--
src/mesa/state_tracker/st_context.c | 3 ---
src/mesa/state_tracker/st_context.h | 3 ---
src/mesa/state_tra
From: Mathias Fröhlich
Signed-off-by: Mathias Fröhlich
---
src/mesa/state_tracker/st_atom.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/src/mesa/state_tracker/st_atom.c b/src/mesa/state_tracker/st_atom.c
index 45a45960a3..df1a94e831 100644
--- a/src/mesa/stat
From: Mathias Fröhlich
Only tnl based drivers still use this array. So remove it
from core mesa and use Array._DrawVAO instead.
Signed-off-by: Mathias Fröhlich
---
src/mesa/drivers/dri/nouveau/nouveau_vbo_t.c | 4 ++--
src/mesa/main/arrayobj.c | 1 -
src/mesa/main/attrib.
From: Mathias Fröhlich
Compute VAO buffer binding information past the position/generic0 mapping.
Scan for duplicate buffer bindings and collapse them into derived
effective buffer binding index and effective attribute mask variables.
Provide a set of helper functions to access the distilled
info
From: Mathias Fröhlich
Finally make use of the binding information in the VAO when
setting up arrays for draw.
v2: Emit less relocations also for interleaved userspace arrays.
Signed-off-by: Mathias Fröhlich
---
src/mesa/state_tracker/st_atom_array.c | 432 -
1
From: Mathias Fröhlich
The only remaining users of gl_vertex_array are tnl based
drivers. So move everything related to that into tnl and
rename it accordingly.
Signed-off-by: Mathias Fröhlich
---
src/mesa/drivers/dri/nouveau/nouveau_vbo_t.c | 38 +--
src/mesa/main/mtypes.h
From: Mathias Fröhlich
For now store binding and attrib in brw_vertex_element.
The i965 driver still provides lots of opportunity to make use
of the unique binding information in the VAO which is currently not
taken from the VAO.
Signed-off-by: Mathias Fröhlich
---
src/mesa/drivers/dri/i965/br
From: Mathias Fröhlich
Was meant to be temporary in i965.
Signed-off-by: Mathias Fröhlich
---
src/mesa/drivers/dri/i965/brw_context.h | 4
src/mesa/drivers/dri/i965/brw_draw.c| 7 ---
2 files changed, 11 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_context.h
b/src/mes
From: Mathias Fröhlich
Signed-off-by: Mathias Fröhlich
---
src/mesa/drivers/dri/i965/brw_draw.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_draw.c
b/src/mesa/drivers/dri/i965/brw_draw.c
index 25ba372c44..c5f04264fa 100644
From: Mathias Fröhlich
The input_to_index array is already available internally
when preparing vertex programs. Store the map in
struct st_vertex_program.
Also store the bitmask of mesa vertex processing inputs in
struct st_vp_variant.
Signed-off-by: Mathias Fröhlich
---
src/mesa/state_tracker
From: Mathias Fröhlich
Hi Brian,
The second version of 'we are getting there somehow'.
The series builds up unique binding information internal to a VAO.
This shall help drivers to get as few buffer objects as possible.
The first patch implements building up this unique binding information.
Then
On 05/06/2018 05:31 PM, Timothy Arceri wrote:
> On 05/05/18 07:28, Kenneth Graunke wrote:
>
>> On Thursday, April 26, 2018 2:28:41 PM PDT Ian Romanick wrote:
>>> From: Ian Romanick
>>>
>>> This code was clearly never tested. It's a good thing that no driver
>>> ever tried to enable this path.
>>
https://bugs.freedesktop.org/show_bug.cgi?id=106315
Matthew Scheirer changed:
What|Removed |Added
CC||matt.schei...@gmail.com
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=103852
--- Comment #18 from Ben Clapp ---
Bug still present on 18.0.2.
I noticed flickering back and forth between a black screen and the game screen
when resizing the window, so I made a short video demonstrating this:
https://www.youtube.com/watch?v=
On 05/05/18 07:28, Kenneth Graunke wrote:
On Thursday, April 26, 2018 2:28:41 PM PDT Ian Romanick wrote:
From: Ian Romanick
This code was clearly never tested. It's a good thing that no driver
ever tried to enable this path.
Signed-off-by: Ian Romanick
---
src/mesa/main/ffvertex_prog.c |
On May 4, 2018 5:44:25 PM PDT, Chad Versace wrote:
>Thanks for the patches. The code looks good. All my suggestions are
>merely nitpicks to make the patches follow Mesa conventions.
>
>In general, if you have questions about commit message style, examine
>the git log for previous patches that to
On Sun, May 6, 2018 at 1:51 PM, Tobias Klausmann
wrote:
> Hi,
>
> fyi: there is another bugreport #106372 [1], where i bisected the problem in
> the xserver and found a problematic commit, with code which can easily be
> reverted (patch in the bugreport), maybe you could check if that fixes the
>
https://bugs.freedesktop.org/show_bug.cgi?id=106420
--- Comment #1 from Axel Rohde ---
Additional system info:
libdrm 2.4.91
Linux debi2 4.16.0-1-amd64 #1 SMP Debian 4.16.5-1 (2018-04-29) x86_64 GNU/Linux
libva 2.1.0
--
You are receiving this mail because:
You are the QA Contact for the bug.
Yo
https://bugs.freedesktop.org/show_bug.cgi?id=106420
Bug ID: 106420
Summary: segfault in dri2_allocate_textures(), radeonsi_dri.so
18.1-rc3 using mpv
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Li
Oops, missed that v2. Still :
Reviewed-by: Lionel Landwerlin
On 05/05/18 19:11, Jason Ekstrand wrote:
In the prime case, our modifier is always DRM_FORMAT_MOD_LINEAR and we
would end up calling dri3_pixmap_from_buffers on an X server which does
not support it.
Bugzilla: https://bugs.freedeskt
Reviewed-by: Lionel Landwerlin
s/cal/call/ :)
On 05/05/18 19:08, Jason Ekstrand wrote:
In the prime case, our modifier is always DRM_FORMAT_MOD_LINEAR and we
would end up calling dri3_pixmap_from_buffers on an X server which does
not support it.
Bugzilla: https://bugs.freedesktop.org/show_bug
Reviewed-by: Lionel Landwerlin
On 05/05/18 19:39, Chris Wilson wrote:
A couple of typos found by inspecting field.end - field.start, revealed
a few wide integers declared as bool and some that ended before they
started.
Cc: Lionel Landwerlin
-
-
-
-
-
-
+
Rb
On May 5, 2018 06:35:46 Bas Nieuwenhuizen wrote:
This was setting the LINEAR modifier if neither the
X server nor the driver supported modifiers.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106180
Fixes: c80c08e226 "vulkan/wsi/x11: Add support for DRI3 v1.2"
CC: 18.1
CC: Abel G
On May 6, 2018 05:58:52 Daniel Stone wrote:
Hi,
On 5 May 2018 at 19:07, Jason Ekstrand wrote:
On Sat, May 5, 2018 at 6:34 AM, Bas Nieuwenhuizen
wrote:
@@ -1043,7 +1043,8 @@ x11_image_init(VkDevice device_h, struct
x11_swapchain *chain,
uint32_t bpp = 32;
if (chain->base.use_prime_blit)
Hi,
On 5 May 2018 at 19:07, Jason Ekstrand wrote:
> On Sat, May 5, 2018 at 6:34 AM, Bas Nieuwenhuizen
> wrote:
>> @@ -1043,7 +1043,8 @@ x11_image_init(VkDevice device_h, struct
>> x11_swapchain *chain,
>> uint32_t bpp = 32;
>>
>> if (chain->base.use_prime_blit) {
>> - result = wsi_
Hi,
fyi: there is another bugreport #106372 [1], where i bisected the
problem in the xserver and found a problematic commit, with code which
can easily be reverted (patch in the bugreport), maybe you could check
if that fixes the issue as well!
PS: I looked into bugzilla last weekend where i
is_resource_supported returns if the combination of
target/internalformat is supported in at least one operation. Online
compression is only mandatory for glTexImage2D. Some formats doesn't
support online compression, but can be used in any case, with
glCompressed*D methods.
Without this commit, E
Dear Ilia,
it took me a while but I think I understand now, thanks for all your
explanations.
Am Freitag, den 04.05.2018, 18:11 -0400 schrieb Ilia Mirkin:
>
> Rasterizer state doesn't affect the gallium clear callback. clear
> just clears -- it's a memset. However rasterizer state affects
> g
30 matches
Mail list logo
