Add the the same restriction as in the previous try_emit_sat when trying
to optimize clamp. Fixes an infinite loop in swrast where the lowering
pass unpacks saturate into clamp but the opt_algebraic pass tries to do
the opposite.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=83463
Nine code to match vertex declaration to vs inputs was limiting
the number of possible combinations.
Some sm3 games have issues with that, because arbitrary (usage/index)
can be used.
This patch does the following changes to fix the problem:
. Change the numbers given to (usage/index)
With sm3, you can declare an input/output with an usage and an usage index.
Nine code hardcodes the translation usage/index to a corresponding TGSI code.
The translation was limited to a few usage/index combinations that were
corresponding
to most of the needs of games, but some games did not
This addresses the potential issue I was worried about when I worked on
my patch series for expanding get_range that I sent a while back.
With the the the in the commit message fixed:
Reviewed-by: Thomas Helland thomashellan...@gmail.com
This conflicts with my series, but I'll need to do some
Tegra K1 and later use a GPU that can be driven by the Nouveau driver.
But the GPU is a pure render node and has no display engine, hence the
scanout needs to happen on the Tegra display hardware. The GPU and the
display engine each have a separate DRM device node exposed by the
kernel.
To make
On Thu, Nov 27, 2014 at 11:39 AM, Thierry Reding
thierry.red...@gmail.com wrote:
Tegra K1 and later use a GPU that can be driven by the Nouveau driver.
But the GPU is a pure render node and has no display engine, hence the
scanout needs to happen on the Tegra display hardware. The GPU and the
Sorry for that. Someone (== me) didn't realize he needs to push it :-).
Done that now.
Roland
Am 27.11.2014 um 01:53 schrieb Romain Failliot:
Hi!
I'm not familiar with the patch and merge process, I just wonder if
it is normal that my patch isn't merged yet (it's been more than 20
days).
The Mesa a patch and the piglit patch are both
Reviewed-by: Ian Romanick ian.d.roman...@intel.com
On November 26, 2014 3:08:38 PM Neil Roberts n...@linux.intel.com wrote:
According to the GLSL spec float literals like ‘1f’ shouldn't be allowed
without adding a decimal point or an exponent.
Cool! Thanks a lot!
Le 27 nov. 2014 12:05, Roland Scheidegger srol...@vmware.com a écrit :
Sorry for that. Someone (== me) didn't realize he needs to push it :-).
Done that now.
Roland
Am 27.11.2014 um 01:53 schrieb Romain Failliot:
Hi!
I'm not familiar with the patch and merge
On Thu, Nov 27, 2014 at 12:45 AM, Abdiel Janulgue
abdiel.janul...@linux.intel.com wrote:
Add the the same restriction as in the previous try_emit_sat when trying
to optimize clamp. Fixes an infinite loop in swrast where the lowering
pass unpacks saturate into clamp but the opt_algebraic pass
This patch adds support for following GLES2 Texture Float extensions:
1)GL_OES_texture_float,
2)GL_OES_texture_half_float,
3)GL_OES_texture_float_linear,
4)GL_OES_texture_half_float_linear.
Support for these extensions need to be explicitly enabled per driver
and this patch enables support for
Where is 'type' changed? I'm not sure I understand this logic, but IIRC GL
ES does have some weird language about format/type/internalformat
combinations.
type, hasn't changed. I fixed the comments now.
Br,
Kalyan
On Wed, Nov 26, 2014 at 8:21 AM, Brian Paul bri...@vmware.com wrote:
The
On Thu, Nov 27, 2014 at 10:56 AM, Kalyan Kondapally
kondapallykalyancontrib...@gmail.com wrote:
This patch adds support for following GLES2 Texture Float extensions:
1)GL_OES_texture_float,
2)GL_OES_texture_half_float,
3)GL_OES_texture_float_linear,
4)GL_OES_texture_half_float_linear.
On Thursday 27 November 2014, Kalyan Kondapally wrote:
This patch adds support for following GLES2 Texture Float extensions:
1)GL_OES_texture_float,
2)GL_OES_texture_half_float,
3)GL_OES_texture_float_linear,
4)GL_OES_texture_half_float_linear.
Support for these extensions need to be
Any driver that can support ARB_texture_float should also be able to
support these extensions, so I think you can reuse the ARB_texture_float
enable flag here.
As per discussion here,
http://lists.freedesktop.org/archives/mesa-dev/2014-May/059679.html,
drivers should be able to advertise support
With this check we can avoid segmentation fault when invalid value used during
eglCreateContext.
Cc: mesa-sta...@lists.freedesktop.org
Cc: mesa-dev@lists.freedesktop.org
Signed-off-by: Valentin Corfu valentinx.co...@intel.com
---
src/egl/drivers/dri2/egl_dri2.c | 5 +
1 file changed, 5
https://bugs.freedesktop.org/show_bug.cgi?id=86788
Michel Dänzer mic...@daenzer.net changed:
What|Removed |Added
CC||matts...@gmail.com,
https://bugs.freedesktop.org/show_bug.cgi?id=54805
Chris Forbes chr...@ijw.co.nz changed:
What|Removed |Added
Assignee|chr...@ijw.co.nz
From: Dave Airlie airl...@redhat.com
Since 73dd50acf6d244979c2a657906aa56d3ac60d550
glsl: implement switch flow control using a loop
The SB backend was falling over in an assert or crashing.
Tracked this down to the loops having no repeats, but requiring
a working break, initial code just
On 11/28/2014 01:39 AM, Thierry Reding wrote:
Tegra K1 and later use a GPU that can be driven by the Nouveau driver.
But the GPU is a pure render node and has no display engine, hence the
scanout needs to happen on the Tegra display hardware. The GPU and the
display engine each have a separate
On Thu, Nov 27, 2014 at 11:39 AM, Thierry Reding
thierry.red...@gmail.com wrote:
Tegra K1 and later use a GPU that can be driven by the Nouveau driver.
But the GPU is a pure render node and has no display engine, hence the
scanout needs to happen on the Tegra display hardware. The GPU and the
https://bugs.freedesktop.org/show_bug.cgi?id=86788
--- Comment #2 from smoki smoki00...@gmail.com ---
(In reply to Michel Dänzer from comment #1)
smoki, please get a backtrace of the crash.
Well there it is:
Program received signal SIGSEGV, Segmentation fault.
_mesa_uint_array_min_max
22 matches
Mail list logo
