This partially reverts commit 356ec7a21960d77db282f67af577dcdb46966b5a.
There are missing symbols needed by libglsl, so we might as well skip the
entire library (which should be present in the mesa stat tracker).
Signed-off-by: Jan Vesely
---
Hi Timur, Vinson,
this patch is enough to get clove
On Sat, Apr 6, 2019 at 10:18 AM Alyssa Rosenzweig wrote:
>
> Hi,
>
> NIR system values are the preferred method of transferring state like
> this around; the shared transformation pass should be agnostic to the
> underlying uniforms / state tracker / etc. Is there any reason we can't
> share the t
See my other email implementing sysvals. That avoids changing the state
tracker in uncomfortable ways or having special uniforms introduced.
Lima should implement sysvals too, not just for viewport but also for
emulating certain desktop functionality. See what vc4/v3d/freedreno do
with sysvals for
Hi,
NIR system values are the preferred method of transferring state like
this around; the shared transformation pass should be agnostic to the
underlying uniforms / state tracker / etc. Is there any reason we can't
share the transform as I implement it here? (Which makes no assumptions
about unif
So you prefer to use the nir sysval method and implement a per driver version
of viewport transform? As I sended out a patch series for a shared version of
this transform, any feedback on it?
https://patchwork.freedesktop.org/series/58618/
Regards,
Qiang
On Wed, Apr 3, 2019 at 9:50 AM Alyssa Rose
Hello James,
sorry that I have to report that the mentioned commit sigfault with
'mplayer -vo vdpau xxx' for radeonsi on my Polaris 20.
BISECTED
0f416b85fbb2a3988ddc2c81540e9aadfd63d6ae is the first bad commit
commit 0f416b85fbb2a3988ddc2c81540e9aadfd63d6ae
Author: James Zhu
Date: Fri Mar
https://bugs.freedesktop.org/show_bug.cgi?id=110261
--- Comment #5 from Jason Ekstrand ---
Can you reproduce with a full debug build in gdb and run "bt all"?
--
You are receiving this mail because:
You are the assignee for the bug.___
mesa-dev mailing
Quoting Khaled Emara (2019-04-05 11:28:28)
> Upgraded meson's minimum version from 0.45 to 0.47
> Version 0.47 is required to use build_always_stale
> ---
> meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index 2c98e9e18a9..454928e2
Hi Trevor,
From: Trevor Woerner
>On Mon 2019-04-01 @ 08:55:56 PM, Jean Hertel wrote:
>> - What about GSOC? On the X.Org [page][2] there is still a driconf
>> replacement idea. If we move, can we replace this with some adriconf
>> improvement ideas?
>>
>> [2]: https://www.x.org/wiki/SummerOfCodeI
I'm proposing this for LLVM.
Thanks
On 06/04/19 2:05 AM, Trevor Woerner wrote:
Hi Praveen,
On Tue 2019-04-02 @ 12:51:12 AM, preejackie wrote:
I'm proposing this project for GSoC 2019. It would be helpful to know how
this new features are effective to Mesa library, so that I include your
comme
Hi Praveen,
On Tue 2019-04-02 @ 12:51:12 AM, preejackie wrote:
> I'm proposing this project for GSoC 2019. It would be helpful to know how
> this new features are effective to Mesa library, so that I include your
> comments in "View from Clients" proposal section.
Are you proposing this for X.Org
On Mon 2019-04-01 @ 08:55:56 PM, Jean Hertel wrote:
> - What about GSOC? On the X.Org [page][2] there is still a driconf
> replacement idea. If we move, can we replace this with some adriconf
> improvement ideas?
> [2]: https://www.x.org/wiki/SummerOfCodeIdeas/
Are you interested in doing this as
Upgraded meson's minimum version from 0.45 to 0.47
Version 0.47 is required to use build_always_stale
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index 2c98e9e18a9..454928e244a 100644
--- a/meson.build
+++ b/meson.build
@@ -25,7 +25
build_always is deprecate in meson.
The recommended equivalent is build_by_default and build_always_stale.
---
src/meson.build | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/meson.build b/src/meson.build
index 6d04b5fc3b2..61fcb86deeb 100644
--- a/src/meson.build
+++ b/s
Mesa 18.3.6 is now available.
Note: this is the final anticipated release in the 18.3 series. Users are
encouraged to migrate to the 19.0 series in order to obtain future fixes.
The current release consists mainly of GLSL improvements. We also have a few
UUID fixes in for both GL and Vulkan driv
https://bugs.freedesktop.org/show_bug.cgi?id=110335
Marek Olšák changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110337
Michel Dänzer changed:
What|Removed |Added
Assignee|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop
https://bugs.freedesktop.org/show_bug.cgi?id=110337
--- Comment #1 from Berg ---
A propos!
Kernel version does not matter - it was tested on kernels from 4.18 to 5.0.5
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=110337
Berg changed:
What|Removed |Added
CC||b...@uralmail.com
--
You are receiving this mai
https://bugs.freedesktop.org/show_bug.cgi?id=110337
Bug ID: 110337
Summary: Mesa 19.0.0(1)
Product: Mesa
Version: 19.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priori
Hi Emil,
Now that I have been putting together a test case for the the actual use
I do see some issues with the pbuffer code path. Well - still investigating
if the test is wrong or the result.
In the mean time some small comments inline below ...
Mathias
On Thursday, 4 April 2019 17:25:28 CEST
On 4/5/19 2:59 PM, Eric Engestrom wrote:
On Friday, 2019-04-05 12:27:14 +0200, Samuel Pitoiset wrote:
In a multi-GPU scenario.
Signed-off-by: Samuel Pitoiset
FYI, crucible now uses merge requests on gitlab :)
https://gitlab.freedesktop.org/mesa/crucible/merge_requests
---
doc/crucible-ru
On Friday, 2019-04-05 12:27:14 +0200, Samuel Pitoiset wrote:
> In a multi-GPU scenario.
>
> Signed-off-by: Samuel Pitoiset
FYI, crucible now uses merge requests on gitlab :)
https://gitlab.freedesktop.org/mesa/crucible/merge_requests
> ---
> doc/crucible-run.1.txt | 4
> incl
In a multi-GPU scenario.
Signed-off-by: Samuel Pitoiset
---
doc/crucible-run.1.txt | 4
include/framework/runner/runner.h | 2 ++
include/framework/test/test.h | 1 +
misc/crucible-completion.bash | 1 +
src/cmd/bootstrap.c| 1 +
src/cmd/run.c
https://bugs.freedesktop.org/show_bug.cgi?id=110335
Fabio Pedretti changed:
What|Removed |Added
CC||t_arc...@yahoo.com.au
--
You are rece
https://bugs.freedesktop.org/show_bug.cgi?id=110335
Bug ID: 110335
Summary: tegra_context.c:591:4: error: too few arguments to
function ‘context->gpu->set_shader_buffers’
Product: Mesa
Version: git
Hardware: ARM
Reviewed-by: Timothy Arceri
On 5/4/19 8:26 pm, Samuel Pitoiset wrote:
The current algorithm only supports packing 32-bit types.
If a shader uses both 16-bit and 32-bit varyings, we shouldn't
compact them together.
v2 - fix regressions spotted by Intel CI
Cc: Timothy Arceri
Signed-off-by: Sam
The current algorithm only supports packing 32-bit types.
If a shader uses both 16-bit and 32-bit varyings, we shouldn't
compact them together.
v2 - fix regressions spotted by Intel CI
Cc: Timothy Arceri
Signed-off-by: Samuel Pitoiset
---
src/compiler/nir/nir_linking_helpers.c | 13 +++
https://bugs.freedesktop.org/show_bug.cgi?id=110261
--- Comment #4 from Denis ---
looks like I made a bisect for this issue. Jason, could you please take a look
to it? It shows your commit.
[manjaro@manjaro-pc mesa]$ git bisect good
68df93ecbcee6215ac49e0c6f62ae818d2bc9962 is the first bad co
29 matches
Mail list logo
