On 02/14/2017 12:30 PM, Chad Versace wrote:
On Tue 14 Feb 2017, Matt Turner wrote:
Provides the ability to read the .note.gnu.build-id section of ELF
binaries, which is inserted by the --build-id=... flag to ld.
---
configure.ac | 2 +
src/util/Makefile.sources | 2 +
src/util/
On 08/22/2016 04:10 PM, Julien Cristau wrote:
On Mon, Aug 22, 2016 at 14:18:51 -0700, Jason Ekstrand wrote:
On Mon, Aug 22, 2016 at 2:06 PM, Julien Cristau wrote:
On Fri, Aug 19, 2016 at 09:04:14 -0700, Jason Ekstrand wrote:
Not providing a path allows the ICD to work on multi-arch systems
On 08/23/2016 02:07 AM, Emil Velikov wrote:
Skimmed through the discussion and I'm not sure the above will be enough.
Since the user is free to place json files in $HOME/.local ... this
implies that they may _not_ have access to /usr or /etc. Thus as they
install the file (to say $HOME/foo/lib)
On 08/23/2016 02:45 PM, Emil Velikov wrote:
On 23 August 2016 at 19:05, Nicholas Miell wrote:
On 08/23/2016 02:07 AM, Emil Velikov wrote:
Skimmed through the discussion and I'm not sure the above will be enough.
Since the user is free to place json files in $HOME/.local ... this
im
On 03/01/2013 03:14 PM, Ian Romanick wrote:
> New Procedures and Functions
>
> Bool glXQueryRendererIntegerMESA(Display *dpy, int screen,
> int renderer, int attribute,
> unsigned int *value);
> Bool glXQueryCurrentR
The pkg-config file is called xxf86vm.
Signed-off-by: Nicholas Miell
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index 33121600d0c..82c4d2ed12c 100644
--- a/meson.build
+++ b/meson.build
@@ -678,7 +678,7 @@ if with_platform_x11
On 10/17/2017 12:21 PM, Dylan Baker wrote:
+
+To see a description of your options you can run "meson configure". This will
+show your meson project configuration options as well as your local
+configuration options. One meson option to be aware of is that meson's default
+build type is "debug" (
Tested with AMD's Anvil OutOfOrderRasterization demo on a RX 560.
Signed-off-by: Nicholas Miell
---
src/amd/vulkan/radv_device.c | 17 +
src/amd/vulkan/radv_pipeline.c | 10 +-
2 files changed, 26 insertions(+), 1 deletion(-)
diff --git a/src/amd/vulkan/radv_dev
On 09/23/2017 08:39 AM, Dylan Baker wrote:
> diff --git a/meson_options.txt b/meson_options.txt
> index e52cec31f11..854cba851d7 100644
> --- a/meson_options.txt
> +++ b/meson_options.txt
> @@ -20,8 +20,10 @@
>
> option('platforms', type : 'string', value : 'x11,wayland',
> desc
Giving the same name to two different types violates the C++ One Definition
Rule and gcc will complain about it in LTO builds.
Signed-off-by: Nicholas Miell
---
src/amd/addrlib/gfx9/gfx9addrlib.cpp| 2 +-
src/amd/addrlib/inc/chip/gfx9/gfx9_gb_reg.h | 2 +-
src/amd/addrlib/inc/chip/r800
On 09/27/2017 11:53 AM, Nicolai Hähnle wrote:
> On 27.09.2017 20:42, Nicholas Miell wrote:
>> Giving the same name to two different types violates the C++ One
>> Definition
>> Rule and gcc will complain about it in LTO builds.
>
> Oh my. What does the gcc warning look
On 10/03/2017 05:26 PM, Dylan Baker wrote:
diff --git a/meson_options.txt b/meson_options.txt
index eccd5c10d59..568903f1a0a 100644
--- a/meson_options.txt
+++ b/meson_options.txt
+option('valgrind', type : 'boolean', vaule : true,
"vaule" typo.
"[PATCH 5/6] meson_options: Remove ext
On 10/03/2017 05:26 PM, Dylan Baker wrote:
diff --git a/meson_options.txt b/meson_options.txt
index 568903f1a0a..62d6b593f88 100644
--- a/meson_options.txt
+++ b/meson_options.txt
+option('glvnd', type : 'boolean', vaule : false,
"vaule" again, although you fix this in "[PATCH 4/6]
On 10/07/2017 10:53 AM, Marek Olšák wrote:
> Would you please share how you build 32-bit Mesa on Linux. I think it
> would be useful to everybody.
1) Name your build directories e.g. BUILD.x86_64 or BUILD.i686. Put them both
in the same directory.
2) Put -m32 or -m64 in the CFLAGS and CXXFLAGS e
FOG_DISTANCE_MODE_NV & FOG_COORD_SRC weren't getting saved
into display lists or restored on glPopAttrib(GL_FOG_BIT).
Signed-off-by: Nicholas Miell
---
src/mesa/main/attrib.c | 4
src/mesa/main/dlist.c | 2 ++
2 files changed, 6 insertions(+)
diff --git a/src/mesa/main/attri
On 06/25/2018 12:04 PM, Ian Romanick wrote:
> On 06/25/2018 11:53 AM, Nicholas Miell wrote:
>> FOG_DISTANCE_MODE_NV & FOG_COORD_SRC weren't getting saved
>> into display lists or restored on glPopAttrib(GL_FOG_BIT).
>
> Good catch. How did you detect this? Do
When extensions get promoted into OpenGL itself, they keep the same
token names minus the _EXT or whatever postfix, which means grepping for
the tokens in the OpenGL specification will find the implementation in
the Mesa source even if it still uses the original token names from the
extension.
Unf
On 05/13/2018 06:14 PM, Bas Nieuwenhuizen wrote:
-#define V_028808_X_0X00 0x00
-#define V_028808_X_0X05 0x05
-#define V_028808_X_0X0A 0x0A
-#define V_028808_X_0X
On 09/12/2018 05:40 PM, Marek Olšák wrote:
> +static void
> +util_set_full_cpu_affinity(void)
> +{
> + cpu_set_t cpuset;
> +
> + CPU_ZERO(&cpuset);
> + for (unsigned i = 0; i < CPU_SETSIZE; i++)
> + CPU_SET(i, &cpuset);
> +
> + pthread_setaffinity_np(pthread_self(), sizeof(cpuset), &cp
On 08/23/2017 06:23 PM, Matt Turner wrote:
On Wed, Aug 23, 2017 at 2:32 AM, Timothy Arceri wrote:
Steam is already analysing cache items
What does this mean?
Steam will attempt to download compiled shaders for your GPU and version
of Mesa, or upload the shaders you compile locally if they'
The NV_fog_distance extension allows you to specify how the fog distance
of a fragment is calculated. The usual method approximates the distance
of the fragment from the eye as the absolute value of the distance of
the fragment from the eye's Z plane. (Or, rather, the distance of each
vertex and th
---
src/gallium/drivers/llvmpipe/.gitignore |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/gallium/drivers/llvmpipe/.gitignore
b/src/gallium/drivers/llvmpipe/.gitignore
index 6ebd2b8..ce96392 100644
--- a/src/gallium/drivers/llvmpipe/.gitignore
+++ b/src/gallium/driv
No driver implements it yet.
---
src/mesa/main/extensions.c |1 +
src/mesa/main/fog.c| 14 ++
src/mesa/main/get.c|5 +
src/mesa/main/mtypes.h |2 ++
4 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/src/mesa/main/extensions.c b/src/me
This is all that is needed to implement NV_fog_distance on programmable
hardware.
---
src/mesa/main/ffvertex_prog.c | 40
1 files changed, 36 insertions(+), 4 deletions(-)
diff --git a/src/mesa/main/ffvertex_prog.c b/src/mesa/main/ffvertex_prog.c
index 2
The fixed-function generated vertex program is all that's needed for
Gallium drivers.
---
src/mesa/state_tracker/st_extensions.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/mesa/state_tracker/st_extensions.c
b/src/mesa/state_tracker/st_extensions.c
index 722db8d..
This has not been tested on real hardware. I have no idea if it works.
Add support for NV_fog_distance to the NV10 and NV20 drivers.
---
src/mesa/drivers/dri/nouveau/nv10_context.c |1 +
src/mesa/drivers/dri/nouveau/nv10_state_tnl.c | 14 +++---
src/mesa/drivers/dri/nouveau/nv20_c
On 09/19/2011 10:23 AM, Ian Romanick wrote:
>
> I guess the big question is... why? With vertex shaders, this
> functionality is not terribly useful. Over the past few weeks we've
> been *removing* code like this, so it seems kind of odd to add some of
> it. If I'm not mistaken, the only hardwa
The code formatting in translate_fog_distance_mode has been fixed.
The NV10/NV20 patch isn't include this time around because it is still
untested and was only included in the first place in case the nouveau
people were interested.
___
mesa-dev mailing
No driver implements it yet.
---
src/mesa/main/extensions.c |1 +
src/mesa/main/fog.c| 14 ++
src/mesa/main/get.c|5 +
src/mesa/main/mtypes.h |2 ++
4 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/src/mesa/main/extensions.c b/src/me
This is all that is needed to implement NV_fog_distance on programmable
hardware.
---
src/mesa/main/ffvertex_prog.c | 43 +---
1 files changed, 39 insertions(+), 4 deletions(-)
diff --git a/src/mesa/main/ffvertex_prog.c b/src/mesa/main/ffvertex_prog.c
index 2
The fixed-function generated vertex program is all that's needed for
Gallium drivers.
---
src/mesa/state_tracker/st_extensions.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/mesa/state_tracker/st_extensions.c
b/src/mesa/state_tracker/st_extensions.c
index 108d7ae..
31 matches
Mail list logo
