On Fri, Jan 17, 2014 at 3:19 AM, Christian König
deathsim...@vodafone.de wrote:
Am 17.01.2014 04:19, schrieb Ilia Mirkin:
It's a bit unreasonable to rely on applications doing the queries and
then obeying their results.
Apart from a minor style comment (see below) the patch looks good to
Am 17.01.2014 09:37, schrieb Ilia Mirkin:
On Fri, Jan 17, 2014 at 3:19 AM, Christian König
deathsim...@vodafone.de wrote:
Am 17.01.2014 04:19, schrieb Ilia Mirkin:
It's a bit unreasonable to rely on applications doing the queries and
then obeying their results.
Apart from a minor style
On Fri, Jan 17, 2014 at 9:22 AM, Christian König
deathsim...@vodafone.de wrote:
But as a general note on writing patches: Please limit the subject line to a
sane length! Something between 60 and 80 chars should be ok.
Indeed. The regex patterns are nice to have. But please, put them in
the
Use same names as the kernel, makes it easier to identify
connectors in the common case.
Signed-off-by: Lucas Stach l.st...@pengutronix.de
---
tests/modeprint/modeprint.c | 28 +++-
1 file changed, 27 insertions(+), 1 deletion(-)
diff --git a/tests/modeprint/modeprint.c
Remove/update related comments and rename MESA_FORMAT_XBGR A Type formats
to match naming spec as follows:
s/\bMESA_FORMAT_XBGR_SNORM\b/MESA_FORMAT_RGBX_SNORM8/g
s/\bMESA_FORMAT_XBGR_SRGB\b/MESA_FORMAT_SRGBX_UNORM8/g
s/\bMESA_FORMAT_XBGR_UINT\b/MESA_FORMAT_RGBX_UINT8/g
On Fri, Jan 17, 2014 at 2:43 AM, Erik Faye-Lund kusmab...@gmail.com wrote:
On Fri, Jan 17, 2014 at 9:22 AM, Christian König
deathsim...@vodafone.de wrote:
But as a general note on writing patches: Please limit the subject line
to a
sane length! Something between 60 and 80 chars should be
- Original Message -
Fixes regression since 9baa45f78b8ca7d66280e36009b6a685055d7cd6
but some of the piglit fbo-drawbuffers-none tests still don't
pass.
---
src/gallium/drivers/svga/svga_pipe_clear.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git
On Fri, Jan 10, 2014 at 02:29:04PM -0800, Matt Turner wrote:
On Wed, Dec 25, 2013 at 2:11 AM, Pohjolainen, Topi
topi.pohjolai...@intel.com wrote:
On Thu, Dec 19, 2013 at 01:40:23PM -0800, Matt Turner wrote:
Previously we simply considered two registers whose live ranges
overlapped to
On Thu, Jan 16, 2014 at 6:55 PM, Emil Velikov emil.l.veli...@gmail.com wrote:
On 16/01/14 23:29, Kristian Høgsberg wrote:
On Sat, Jan 11, 2014 at 04:51:42PM -0500, Rob Clark wrote:
On Sat, Jan 11, 2014 at 11:54 AM, Emil Velikov emil.l.veli...@gmail.com
wrote:
This is an updated series of
From: José Fonseca jfons...@vmware.com
I was the sole author, as Tungsten Graphics employee, which was since
then acquired by VMware Inc.
---
src/gallium/drivers/trace/trace.xsl | 36 ++--
1 file changed, 22 insertions(+), 14 deletions(-)
diff --git
On 01/17/2014 08:33 AM, jfons...@vmware.com wrote:
From: José Fonseca jfons...@vmware.com
I was the sole author, as Tungsten Graphics employee, which was since
then acquired by VMware Inc.
---
src/gallium/drivers/trace/trace.xsl | 36 ++--
1 file changed, 22
https://bugs.freedesktop.org/show_bug.cgi?id=73746
Priority: medium
Bug ID: 73746
Assignee: mesa-dev@lists.freedesktop.org
Summary: Gallum HUD not always visible with Rust
Severity: normal
Classification: Unclassified
OS:
On 16 January 2014 05:37, Tapani Pälli tapani.pa...@intel.com wrote:
On 01/15/2014 06:13 PM, Paul Berry wrote:
On 2 January 2014 03:58, Tapani Pälli tapani.pa...@intel.com wrote:
Signed-off-by: Tapani Pälli tapani.pa...@intel.com
---
src/mesa/main/shaderapi.c | 44
On 01/16/2014 10:13 PM, Mark Mueller wrote:
This series encompases the much discussed specification and renaming of
MESA_FORMATs,
which now is packed into 8 patches
Signed-off-by: Mark Mueller markkmuel...@gmail.com
---
Well, our other enum typedefs (and structs) all use the gl_ prefix. But
On 15 January 2014 02:46, Tapani tapani.pa...@intel.com wrote:
On 01/14/2014 07:53 PM, Paul Berry wrote:
On 2 January 2014 03:58, Tapani Pälli tapani.pa...@intel.com wrote:
+static void
+serialize_uniform_storage(gl_uniform_storage *uni, memory_writer blob)
I don't think this is
On 01/17/2014 03:45 AM, Mark Mueller wrote:
Change all 4 color component unsigned byte formats to meet spec:
s/MESA_FORMAT_RGBA\b/MESA_FORMAT_ABGR_UNORM8/g
s/MESA_FORMAT_RGBA_REV\b/MESA_FORMAT_RGBA_UNORM8/g
s/MESA_FORMAT_ARGB\b/MESA_FORMAT_BGRA_UNORM8/g
On 14 January 2014 02:35, Tapani Pälli tapani.pa...@intel.com wrote:
On 01/13/2014 08:27 PM, Paul Berry wrote:
On 2 January 2014 03:58, Tapani Pälli tapani.pa...@intel.com wrote:
Class will be used by the shader binary cache implementation.
Signed-off-by: Tapani Pälli
On 14 January 2014 03:35, Tapani Pälli tapani.pa...@intel.com wrote:
On 01/14/2014 01:24 AM, Paul Berry wrote:
On 2 January 2014 03:58, Tapani Pälli tapani.pa...@intel.com wrote:
+ var-state_slots = NULL;
+
+ if (var-num_state_slots 0) {
+ var-state_slots = ralloc_array(var,
https://bugs.freedesktop.org/show_bug.cgi?id=73746
--- Comment #1 from Marek Olšák mar...@gmail.com ---
Did you compile Mesa with --enable-gallium-egl?
--
You are receiving this mail because:
You are the assignee for the bug.
___
mesa-dev mailing list
From: Roland Scheidegger srol...@vmware.com
Instead of skipping x/y clipping completely if there's point_tri_clip points
use guard band clipping. This should be easier (previously we could not disable
generating the x/y bits in the clip mask for llvm path, hence requiring custom
clip path), and
https://bugs.freedesktop.org/show_bug.cgi?id=73746
--- Comment #2 from Thomas Rohloff v10la...@myway.de ---
(In reply to comment #1)
Did you compile Mesa with --enable-gallium-egl?
Yes. Also with other games (for example: Left 4 Dead 2) it works.
--
You are receiving this mail because:
You
On Thu, Dec 19, 2013 at 1:40 PM, Matt Turner matts...@gmail.com wrote:
total instructions in shared programs: 1520829 - 1511991 (-0.58%)
instructions in affected programs: 559725 - 550887 (-1.58%)
GAINED:6
LOST: 9
---
On 01/13/2014 10:28 PM, Eric Anholt wrote:
The original intent was that we'd keep a driver-private copy, and there
would be the normal copy for swrast to make use of without the tuning (or
anything more invasive we might do) specific to i965. Only, we don't
generate swrast code any more,
On Fri, Jan 17, 2014 at 8:58 AM, Brian Paul bri...@vmware.com wrote:
On 01/17/2014 03:45 AM, Mark Mueller wrote:
Change all 4 color component unsigned byte formats to meet spec:
s/MESA_FORMAT_RGBA\b/MESA_FORMAT_ABGR_UNORM8/g
s/MESA_FORMAT_RGBA_REV\b/MESA_FORMAT_RGBA_UNORM8/g
This will be useful in my next patch which depends on a functionality
of _mesa_get_min_invocations_per_fragment() to ignore the sample
qualifier (prog-IsSample) based on a flag passed to it.
Signed-off-by: Anuj Phogat anuj.pho...@gmail.com
Cc: Chris Forbes chr...@ijw.co.nz
Cc:
On 01/17/2014 08:33 AM, jfons...@vmware.com wrote:
diff --git a/src/mesa/drivers/dri/r200/r200_context.c
b/src/mesa/drivers/dri/r200/r200_context.c
index f82424b..f613e56 100644
--- a/src/mesa/drivers/dri/r200/r200_context.c
+++ b/src/mesa/drivers/dri/r200/r200_context.c
@@ -29,7 +29,7 @@
On 01/17/2014 12:56 PM, Ian Romanick wrote:
On 01/17/2014 08:33 AM, jfons...@vmware.com wrote:
diff --git a/src/mesa/drivers/dri/r200/r200_context.c
b/src/mesa/drivers/dri/r200/r200_context.c
index f82424b..f613e56 100644
--- a/src/mesa/drivers/dri/r200/r200_context.c
+++
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/16/2014 10:42 PM, scarp wrote:
Hi,
I originally posted this to dri-users and got no response. I
thought about it further and decided it's really a bug and deserves
to be posted to dri-devel, after all it is a crash and crashes are
On Thu, Dec 19, 2013 at 1:40 PM, Matt Turner matts...@gmail.com wrote:
Could you add some commit message text?
Maybe with a small example.
total instructions in shared programs: 1520829 - 1511991 (-0.58%)
instructions in affected programs: 559725 - 550887 (-1.58%)
GAINED:
The test seems to work correctly with 32 textures per stage. It tests
that all textures return the correct color, but the sampler state is
always the same.
Marek
On Thu, Jan 16, 2014 at 1:28 AM, Kenneth Graunke kenn...@whitecape.org wrote:
On 01/15/2014 12:56 PM, Chris Forbes wrote:
Does this
With Kristian's comment about keeping the original copyright notices
intact addressed, patches 1, 2, 3, 4, 7, 8, and 10 are
Reviewed-by: Ian Romanick ian.d.roman...@intel.com
On 12/14/2013 11:28 AM, Rob Clark wrote:
From: Rob Clark robcl...@freedesktop.org
It seems that over time, code
On 01/17/2014 01:08 PM, Marek Olšák wrote:
The test seems to work correctly with 32 textures per stage. It tests
that all textures return the correct color, but the sampler state is
always the same.
Which is the problem. The method we're using to access samplers works
fine for up to 16, but
Incorrect. You have to manually check if the pack and unpack functions
access the components using bitwise operations or arrays.
Consider char pix[]. The array formats use arrays for accessing, for example:
char *p = pix[(y*width+x)*4];
p[0] = r;
p[1] = g;
p[2] = b;
p[3] = a;
Packed formats use
On 01/17/2014 12:41 PM, Mark Mueller wrote:
On Fri, Jan 17, 2014 at 8:58 AM, Brian Paul bri...@vmware.com
mailto:bri...@vmware.com wrote:
On 01/17/2014 03:45 AM, Mark Mueller wrote:
Change all 4 color component unsigned byte formats to meet spec:
Ken,
Assuming the caches don't completely derail things, you ought to be
able to make this work with pretty minimal impact:
- Keep the low four bits of the sampler index where they are
- If the 5th bit is set:
- Force message header on
- Add 16*sizeof(sampler_state) to the copy of r0.3
On Thu, Dec 19, 2013 at 1:40 PM, Matt Turner matts...@gmail.com wrote:
Transforms, for example,
mul vgrf3, vgrf2, vgrf1
mov.sat vgrf4, vgrf3
into
mul.sat vgrf3, vgrf2, vgrf1
mov vgrf4, vgrf3
which gives register_coalescing an opportunity to remove the MOV
instruction.
total
- Original Message -
On 01/17/2014 12:56 PM, Ian Romanick wrote:
On 01/17/2014 08:33 AM, jfons...@vmware.com wrote:
diff --git a/src/mesa/drivers/dri/r200/r200_context.c
b/src/mesa/drivers/dri/r200/r200_context.c
index f82424b..f613e56 100644
---
https://bugs.freedesktop.org/show_bug.cgi?id=73631
--- Comment #1 from Ian Romanick i...@freedesktop.org ---
It sounds like the shader is broken. Probably just add
precision mediump float;
at global scope before any float (or vec, or mat) types are used.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=73631
--- Comment #2 from Emil Velikov emil.l.veli...@gmail.com ---
Nice one Ian, adding precision mediump float; before the vec4 variable
declaration in the fragment shader did the job.
Running nouveau on a nv96, in case it matters.
--
You are
From: Tom Stellard thomas.stell...@amd.com
This enables piglit to run and interpret the results from OpenCV's
gtest based opencv_test_ocl program.
This patch adds two new CMake configuration variables:
OPENCL_OpenCVTestOCL_BINDIR: You can use this variable to enable
the OpenCV tests by setting
Reviewed-by: Matt Turner matts...@gmail.com
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
On 01/17/2014 02:14 PM, Paul Berry wrote:
These messages are in code that is shared between the VS and GS
back-ends, so use the terminology vec4 to avoid confusion.
Reviewed-by: Ian Romanick ian.d.roman...@intel.com
---
src/mesa/drivers/dri/i965/brw_vec4_generator.cpp | 8
Previously, time spent in geometry shaders would be counted as part of
the vertex shader time.
---
src/mesa/drivers/dri/i965/brw_context.h | 3 +++
src/mesa/drivers/dri/i965/brw_program.c | 10 +-
src/mesa/drivers/dri/i965/brw_vec4.cpp
https://bugs.freedesktop.org/show_bug.cgi?id=73100
Michał Górny mgo...@gentoo.org changed:
What|Removed |Added
Status|NEW |RESOLVED
On Fri, Jan 17, 2014 at 1:24 PM, Marek Olšák mar...@gmail.com wrote:
Incorrect. You have to manually check if the pack and unpack functions
access the components using bitwise operations or arrays.
Consider char pix[]. The array formats use arrays for accessing, for
example:
char *p =
On Sat, Jan 18, 2014 at 12:45 AM, Mark Mueller markkmuel...@gmail.com wrote:
On Fri, Jan 17, 2014 at 1:24 PM, Marek Olšák mar...@gmail.com wrote:
Incorrect. You have to manually check if the pack and unpack functions
access the components using bitwise operations or arrays.
Consider char
This is the overall v2 of the GL_ARB_viewport_array series. It is
mostly the same as the previous series, but there are some differences
worth noting.
Patch i965: Consider all scissor rectangles in noop_scissor in the
original series was replaced by i965: Consider only the scissor
rectangle for
From: Courtney Goeltzenleuchter court...@lunarg.com
v2 (idr): Split these changes out from the original patch. Only
advertise GL_ARB_viewport_array in a core profile because it requires
geometry shaders.
Signed-off-by: Courtney Goeltzenleuchter court...@lunarg.com
Signed-off-by: Ian Romanick
From: Courtney Goeltzenleuchter court...@lunarg.com
This will be used when the viewport near and far plane are stored as
doubles instead of as floats.
v4 (idr): Split out from a single megapatch. Suggested by Ken. Also
drop value_double_4. It's never used anywhere in the patch series.
From: Courtney Goeltzenleuchter court...@lunarg.com
Update Mesa and drivers to access updated gl_scissor_attrib.
Now have an enable bitfield and array of gl_scissor_rects.
Drivers have been updated to the new scissor enable state
attribute (gl_context.scissor.EnableFlags) but still treat it
as a
From: Courtney Goeltzenleuchter court...@lunarg.com
v4: Split out from a single megapatch. Suggested by Ken.
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
---
src/mesa/main/get.c | 5 +
src/mesa/main/get_hash_params.py | 2 +-
src/mesa/main/mtypes.h | 2 +-
From: Ian Romanick ian.d.roman...@intel.com
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/main/attrib.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/src/mesa/main/attrib.c
From: Courtney Goeltzenleuchter court...@lunarg.com
Now that the scissor enable state is a bitfield need a custom function
to extract the correct value from gl_context. Modeled
Scissor.EnableFlags after Color.BlendEnabled.
Signed-off-by: Courtney Goeltzenleuchter court...@lunarg.com
From: Ian Romanick ian.d.roman...@intel.com
Create an internal function that just writes data into the scissor
rectangle. In future patches this will see more use because we only
want to call dd_function_table::Scissor once after setting all of the
scissor rectangles instead of once per scissor
From: Ian Romanick ian.d.roman...@intel.com
Previously the restore code would enable all scissor rectangles if any
scissor rectangles were enabled on entry to meta. When there is only
one scissor rectangle, this is fine. As soon as a driver supports
multiple viewports, this will be a problem.
From: Courtney Goeltzenleuchter court...@lunarg.com
v4: Split out from a single megapatch. Suggested by Ken. Also make
meta's save_state::ViewportX, ::ViewportY, ::ViewportW, and ::ViewportH
to match gl_viewport_attrib.
Signed-off-by: Courtney Goeltzenleuchter court...@lunarg.com
From: Ian Romanick ian.d.roman...@intel.com
At various stages the hardware clamps the gl_ViewportIndex to these
values. Setting them to zero effectively makes gl_ViewportIndex be
ignored. This is acutally useful in blorp (so that we don't have to
modify all of the viewport / scissor state).
From: Courtney Goeltzenleuchter court...@lunarg.com
Only element 0 of the array is used anywhere at this time, so there
should be no changes.
v4: Split out from a single megapatch. Suggested by Ken.
Signed-off-by: Courtney Goeltzenleuchter court...@lunarg.com
Signed-off-by: Ian Romanick
From: Ian Romanick ian.d.roman...@intel.com
Internal callers should do the right thing.
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/main/viewport.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
From: Ian Romanick ian.d.roman...@intel.com
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/drivers/common/meta.c | 14 +++---
src/mesa/main/context.c| 2 +-
src/mesa/main/viewport.c | 24
From: Ian Romanick ian.d.roman...@intel.com
Currently MaxViewports is still 1, so this won't affect any change.
v2: Minor code reformatting suggested by Ken.
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
From: Courtney Goeltzenleuchter court...@lunarg.com
v2 (idr): Use set_scissor_no_notify (and manually notify the driver)
instead of calling _mesa_set_scissori. Refactory bodies of
_mesa_ScissorIndexed and _mesa_ScissorIndexedv into a shared function.
Perform parameter validation in the same
From: Courtney Goeltzenleuchter court...@lunarg.com
v2 (idr): Fix several comparison between signed and unsigned integer
expressions warnings.
Signed-off-by: Courtney Goeltzenleuchter court...@lunarg.com
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke
From: Ian Romanick ian.d.roman...@intel.com
In _mesa_Viewport and _mesa_DepthRange, make sure that
ctx-Driver.Viewport is only called once instead of once per viewport or
depth range.
v2: Make _mesa_DepthRange actually set all of the depth ranges (instead
of just index 0). Noticed by Ken.
From: Courtney Goeltzenleuchter court...@lunarg.com
Define API connections to extension entry points added in previous
commits. Update entry points to use floating point arguments as
required by the extension.
Add get tokens for ARB_viewport_array state.
v2: Include review feedback.
v3 (idr):
From: Ian Romanick ian.d.roman...@intel.com
Create an internal function that just writes data into the viewport. In
future patches this will see more use because we only want to call
dd_function_table::Viewport once after setting all of the viewport
instead of once per viewport.
Signed-off-by:
From: Courtney Goeltzenleuchter court...@lunarg.com
v2 (idr): Fix copy-and-paste bug... s/LAYER/VIEWPORT/
Signed-off-by: Courtney Goeltzenleuchter court...@lunarg.com
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
From: Ian Romanick ian.d.roman...@intel.com
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/main/mtypes.h| 2 ++
src/mesa/program/prog_print.c | 10 ++
2 files changed, 8 insertions(+), 4 deletions(-)
diff
From: Ian Romanick ian.d.roman...@intel.com
These limits will be queryable by GL_MAX_VIEWPORTS,
GL_VIEWPORT_SUBPIXEL_BITS, and GL_VIEWPORT_BOUNDS_RANGE. Drivers that
actually implement the extension must set values for these constants
that comply with the minimum-maximums from the spec.
Most of
From: Ian Romanick ian.d.roman...@intel.com
Currently MaxViewports is still 1, so this won't affect any change.
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/drivers/dri/i965/brw_cc.c | 21 +
From: Courtney Goeltzenleuchter court...@lunarg.com
v2 (idr): Use set_viewport_no_notify / set_depth_range_no_notify (and
manually notify the driver) instead of calling _mesa_set_viewporti /
_mesa_set_depthrangei. Refactor bodies of _mesa_ViewportIndexed and
_mesa_ViewportIndexedv into a shared
From: Ian Romanick ian.d.roman...@intel.com
v2: Use MAX_VIEWPORTS instead of ctx-Const.MaxViewports because the
driver may not set ctx-Const.MaxViewports yet.
v3: Handle all viewport entries in update_viewport_matrix and
_mesa_copy_context too. This was previously in an earlier patch.
Having
From: Ian Romanick ian.d.roman...@intel.com
At least for GEN7+, anyway.
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
docs/GL3.txt| 2 +-
docs/relnotes/10.1.html | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
From: Ian Romanick ian.d.roman...@intel.com
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
src/glsl/glcpp/glcpp-parse.y| 3 +++
src/glsl/glsl_parser_extras.cpp | 1 +
src/glsl/glsl_parser_extras.h | 2 ++
From: Ian Romanick ian.d.roman...@intel.com
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/drivers/dri/i965/gen6_clip_state.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git
From: Ian Romanick ian.d.roman...@intel.com
This matches the expectations of GL_ARB_viewport_array and the storage
type where the values will land.
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/main/viewport.c | 13
From: Ian Romanick ian.d.roman...@intel.com
Drivers that currently use _Xmin and friends to set their scissor
rectangle will need to use this code directly once they are updated for
GL_ARB_viewport_array.
v2: Use different bit-test idiom and fix mixed tabs and spaces. Both
were suggested by
From: Ian Romanick ian.d.roman...@intel.com
In _mesa_Scissor, make sure that ctx-Driver.Scissor is only called once
instead of once per scissor rectangle.
v2: Use MAX_VIEWPORTS instead of ctx-Const.MaxViewports because the
driver may not set ctx-Const.MaxViewports yet.
Signed-off-by: Ian
From: Ian Romanick ian.d.roman...@intel.com
Create an internal function that just writes data into the depth range.
In future patches this will see more use because we only want to call
dd_function_table::DepthRange once after setting all of the depth ranges
instead of once per depth range.
From: Ian Romanick ian.d.roman...@intel.com
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/main/attrib.c | 2 +-
src/mesa/main/context.c | 2 +-
src/mesa/main/scissor.c | 6 +++---
src/mesa/main/scissor.h | 2 +-
4 files
From: Courtney Goeltzenleuchter court...@lunarg.com
v2 (idr): Only enable the extension on GEN7+ w/core profile because it
requires geometry shaders.
v3 (idr): Add some casting to fix setting of ViewportBounds.Min.
Negating an unsigned value, then casting to float doesn't do what you
might think
From: Ian Romanick ian.d.roman...@intel.com
This variable is handled in a fashion identical to gl_Layer.
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/drivers/dri/i965/brw_vec4_visitor.cpp | 4
From: Ian Romanick ian.d.roman...@intel.com
noop_scissor (correctly) only examines the scissor rectangle for
viewport 0. Therefore, it should only be called when that scissor
rectangle is enabled.
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
---
src/mesa/drivers/dri/i965/brw_clear.c
From: Ian Romanick ian.d.roman...@intel.com
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
Reviewed-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/main/attrib.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/src/mesa/main/attrib.c
We call intel_prepare_render() in intelMakeCurrent() to make sure we have
renderbuffers before calling _mesa_make_current(). The only reason we
do this is so that we can have valid defaults for width and height.
If we already have buffers for the drawable we're making current, we
don't need to do
On 01/17/2014 05:03 PM, Ian Romanick wrote:
From: Ian Romanick ian.d.roman...@intel.com
noop_scissor (correctly) only examines the scissor rectangle for
viewport 0. Therefore, it should only be called when that scissor
rectangle is enabled.
Signed-off-by: Ian Romanick
On Fri, Jan 17, 2014 at 5:21 PM, Kristian Høgsberg k...@bitplanet.net wrote:
We call intel_prepare_render() in intelMakeCurrent() to make sure we have
renderbuffers before calling _mesa_make_current(). The only reason we
do this is so that we can have valid defaults for width and height.
If
https://bugs.freedesktop.org/show_bug.cgi?id=73755
Priority: medium
Bug ID: 73755
Keywords: regression
CC: bri...@vmware.com, mar...@gmail.com
Assignee: mesa-dev@lists.freedesktop.org
Summary: [softpipe] piglit
https://bugs.freedesktop.org/show_bug.cgi?id=73757
Priority: medium
Bug ID: 73757
Assignee: mesa-dev@lists.freedesktop.org
Summary: [swrast] SIGSEGV swrast/s_renderbuffer.c:559
Severity: normal
Classification: Unclassified
diff --git a/src/glsl/glsl_parser_extras.cpp
b/src/glsl/glsl_parser_extras.cpp
index 21dc3ab..92076b5 100644
--- a/src/glsl/glsl_parser_extras.cpp
+++ b/src/glsl/glsl_parser_extras.cpp
@@ -484,6 +484,7 @@ struct _mesa_glsl_extension {
static const _mesa_glsl_extension
Signed-off-by: Ilia Mirkin imir...@alum.mit.edu
---
This seems like a function that should exist in gallium/util, but I didn't
find it. I guess the mesa/st does these checks far enough away from actual
resource creation.
src/gallium/state_trackers/vdpau/bitmap.c| 4
Signed-off-by: Ilia Mirkin imir...@alum.mit.edu
---
I can't say I'm happy about re-grabbing the mutex in the error path, but I
assume it must be taken to delete a sampler view. I could move the AddDataHTAB
thing inside the mutex, but I assumed it was like that for a reason -- could
be a perf
NV3x cards don't support NPOT textures. Technically this restriction
could be worked around, but since it also doesn't expose any video
decoding hw, just turn it off entirely.
Signed-off-by: Ilia Mirkin imir...@alum.mit.edu
Cc: 10.0 mesa-sta...@lists.freedesktop.org
---
On Fri, Jan 17, 2014 at 11:58 PM, Ilia Mirkin imir...@alum.mit.edu wrote:
Signed-off-by: Ilia Mirkin imir...@alum.mit.edu
---
This seems like a function that should exist in gallium/util, but I didn't
find it. I guess the mesa/st does these checks far enough away from actual
resource
---
src/glsl/glsl_parser_extras.cpp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/glsl/glsl_parser_extras.cpp b/src/glsl/glsl_parser_extras.cpp
index 21dc3ab..e67988f 100644
--- a/src/glsl/glsl_parser_extras.cpp
+++ b/src/glsl/glsl_parser_extras.cpp
@@ -50,7 +50,7 @@
From: Anuj Phogat anuj.pho...@gmail.com
OpenGL with ARB_ES2_compatibility allows shaders that specify #version
100.
This fixes the Khronos OpenGL test(Texture_Rectangle_Samplers_frag.test)
failure.
Cc: mesa-sta...@lists.freedesktop.org
Reviewed-by: Matt Turner matts...@gmail.com
Signed-off-by:
Instead of defining preprocessor macros in glcpp_parser_create based on
the GL API, wait until the shader version has been resolved. Doing this
allows us to correctly set (and not set) preprocessor macros for
extensions allowed by the API but not the shader, as in the case of
---
src/glsl/glcpp/glcpp-parse.y | 1 -
src/glsl/glcpp/glcpp.c | 1 -
2 files changed, 2 deletions(-)
diff --git a/src/glsl/glcpp/glcpp-parse.y b/src/glsl/glcpp/glcpp-parse.y
index c774662..427fdec 100644
--- a/src/glsl/glcpp/glcpp-parse.y
+++ b/src/glsl/glcpp/glcpp-parse.y
@@ -30,7 +30,6
Cc: mesa-sta...@lists.freedesktop.org
---
src/glsl/glcpp/glcpp-parse.y | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/src/glsl/glcpp/glcpp-parse.y b/src/glsl/glcpp/glcpp-parse.y
index 427fdec..995427a 100644
--- a/src/glsl/glcpp/glcpp-parse.y
+++
On Mon, Dec 9, 2013 at 6:00 PM, Anuj Phogat anuj.pho...@gmail.com wrote:
OpenGL with ARB_ES2_compatibility extension allows shaders that specify
#version 100 and the shader is treated as targeting version 100 of the
GLSL ES.
state-es_shader flag might change during parsing based on the
100 matches
Mail list logo
