On 21.03.2017 17:51, Philipp Zabel wrote:
Stop trying to specify texture or renderbuffer objects for unsupported
EGL images. Generate the error codes specified in the OES_EGL_image
extension.
Signed-off-by: Philipp Zabel
---
EGLImageTargetTexture2D and EGLImageTargetRenderbuffer would call
the
On 22/03/17 07:40 AM, Marek Olšák wrote:
> This looks like a bug in LLVM. Not sure if Mesa should do anything about it:
I don't think we should (assuming we even could). I'm bisecting this
right now and will raise it with the author of the breaking LLVM change
and on the llvm-commits mailing list.
If a proper PRNG like arc4random backed by a syscall like getentropy
were used this would already handle reseeding on fork and fd exhaustion.
And look people have already gone out of their way to provide fallbacks
for these interfaces.
https://github.com/libressl-portable/openbsd/tree/master/src/
On Tue, Mar 21, 2017 at 09:22:50AM -0700, Dylan Baker wrote:
> Quoting Jani Nikula (2017-03-21 07:44:55)
> > On Thu, 16 Mar 2017, Dylan Baker wrote:
> > > First it's written in python, [...]
> >
> > How does meson handle python 2 vs. 3? How do you avoid issues in the
> > build files wrt this? On
From: Grazvydas Ignotas
Instead of using a directory, hash the timestamps into the cache keys
themselves. Since there is no more timestamp directory, there is no more
need for deleting the cache of other mesa versions and we rely on
eviction to clean up the old cache entries. This solves the prob
This can be used to deal with key hash collisions from different
versions (should we find that to actually happen) and to find
which mesa version produced the cache entry.
V2: use blob created add cache creation.
---
src/util/disk_cache.c | 53 +--
From: Grazvydas Ignotas
This allows to get rid of the arch and gpu name directories.
v2: (Timothy Arceri) don't use an opaque data type to store
pointer size and gpu name.
v3: (Timothy Arceri) use blob to store driver keys just make sure
to store null terminator for strings, and make su
v2: Fix argument to nouveau_screen_get_name()
Signed-off-by: Boyan Ding
---
src/gallium/drivers/nouveau/nouveau_screen.c | 30
src/gallium/drivers/nouveau/nouveau_screen.h | 3 +++
2 files changed, 33 insertions(+)
diff --git a/src/gallium/drivers/nouveau/nouveau_s
On Tue, Mar 21, 2017 at 4:59 PM, Matt Turner wrote:
> ---
> Is this what you had in mind?
>
More or less.
> src/compiler/nir/nir.h | 2 +-
> src/compiler/nir/nir_from_ssa.c | 18 --
> 2 files changed, 13 insertions(+), 7 deletions(-)
>
> diff --git a/src/compiler/nir
On 21/03/17 21:23, Timothy Arceri wrote:
On 21/03/17 21:01, Nicolai Hähnle wrote:
On 21.03.2017 10:22, Timothy Arceri wrote:
On 21/03/17 19:25, Nicolai Hähnle wrote:
On 21.03.2017 06:14, Timothy Arceri wrote:
From: Grazvydas Ignotas
This allows to get rid of the arch and gpu name dire
so do I
On Tue, Mar 21, 2017 at 5:43 PM, Chad Versace
wrote:
> I believe 72c89522c23e54ef19d0a8a7fd85f791727a05d6 already does this.
>
> On Tue 21 Mar 2017, Jason Ekstrand wrote:
> > ---
> > src/mesa/drivers/dri/i965/.gitignore | 2 ++
> > 1 file changed, 2 insertions(+)
> > create mode 100644
https://bugs.freedesktop.org/show_bug.cgi?id=99956
Vinson Lee changed:
What|Removed |Added
CC||chadvers...@chromium.org
Keywords
Currently the following build errors are seen on mips64el:
cube-tex.c: In function 'get_fd_rgba':
cube-tex.c:230:2: error: 'for' loop initial declarations are only allowed in
C99 mode
for (uint32_t i = 0; i < texh; i++) {
^
cube-tex.c:230:2: note: use option -std=c99 or -std=gnu99 to compile
https://bugs.freedesktop.org/show_bug.cgi?id=100303
Samuel Pitoiset changed:
What|Removed |Added
Component|Drivers/Gallium/radeonsi|glsl-compiler
QA Contact|dri-
On Wed, Mar 22, 2017 at 1:59 AM, Timothy Arceri wrote:
> Otherwise for apps that don't seed the regular rand() we will always
> remove old cache entries from the same dirs.
>
> V2: assume bits returned by rand are independent uniformly distributed
> bits and grab our hex value without taking t
Quoting Dylan Baker (2017-03-20 09:51:58)
> Quoting Emil Velikov (2017-03-20 08:11:58)
> > On 8 March 2017 at 18:11, Emil Velikov wrote:
> > > On 7 March 2017 at 21:14, Dylan Baker wrote:
> > >> There are a number of small style cleanups and simplifications in this
> > >> series,
> > >> but the
I believe 72c89522c23e54ef19d0a8a7fd85f791727a05d6 already does this.
On Tue 21 Mar 2017, Jason Ekstrand wrote:
> ---
> src/mesa/drivers/dri/i965/.gitignore | 2 ++
> 1 file changed, 2 insertions(+)
> create mode 100644 src/mesa/drivers/dri/i965/.gitignore
>
> diff --git a/src/mesa/drivers/dri/
On Tue 21 Mar 2017, Jason Ekstrand wrote:
> Found by inspection.
>
> Cc: "17.0 13.0"
> ---
> src/intel/vulkan/anv_image.c | 9 +
> 1 file changed, 5 insertions(+), 4 deletions(-)
Reviewed-by: Chad Versace
___
mesa-dev mailing list
mesa-dev@li
Found by inspection.
Cc: "17.0 13.0"
---
src/intel/vulkan/anv_image.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/intel/vulkan/anv_image.c b/src/intel/vulkan/anv_image.c
index aeb144e..dfd193e 100644
--- a/src/intel/vulkan/anv_image.c
+++ b/src/intel/vulkan/a
On 22/03/17 05:53, Grazvydas Ignotas wrote:
On Tue, Mar 21, 2017 at 10:57 AM, Timothy Arceri wrote:
---
src/gallium/drivers/radeon/r600_test_dma.c | 3 +-
src/util/rand_xor.c| 62 --
src/util/rand_xor.h| 6 ++-
3 f
---
Is this what you had in mind?
src/compiler/nir/nir.h | 2 +-
src/compiler/nir/nir_from_ssa.c | 18 --
2 files changed, 13 insertions(+), 7 deletions(-)
diff --git a/src/compiler/nir/nir.h b/src/compiler/nir/nir.h
index db47699..0a127cd 100644
--- a/src/compiler/nir/
V2: pass the seed to the seed function so that we can isolate
its uses. Stop leaking fd when urandom couldn't be read.
---
src/gallium/drivers/radeon/r600_test_dma.c | 3 +-
src/util/rand_xor.c| 57 ++
src/util/rand_xor.h
Otherwise for apps that don't seed the regular rand() we will always
remove old cache entries from the same dirs.
V2: assume bits returned by rand are independent uniformly distributed
bits and grab our hex value without taking the modulus of the whole
value, this also fixes a bug where 'f
V2: pass the seed to rand_xorshift128plus() so that we can isolate
its uses.
---
src/gallium/drivers/radeon/r600_test_dma.c | 24 +-
src/util/Makefile.sources | 2 ++
src/util/rand_xor.c| 20 ++
src/util/rand_xor.h
Rather than using 3 different ways to wrap _mesa_sha1_*() to SHA1*()
functions (a macro, prototype with implementation in .c and an inline
function), make all 3 inline functions.
Signed-off-by: Grazvydas Ignotas
---
src/util/mesa-sha1.c | 6 --
src/util/mesa-sha1.h | 13 ++---
2 fil
Fix linking error with build.
CXXLD glsl_compiler
glsl/.libs/libstandalone.a(lt16-libmesautil_la-u_queue.o): In function
`u_thread_get_time_nano':
src/util/../../src/util/u_thread.h:84: undefined reference to `clock_gettime'
Signed-off-by: Vinson Lee
---
src/compiler/Makefile.glsl.am |3
Reviewed-by: Nanley Chery
Reviewed-by: Anuj Phogat
Reviewed-by: Jason Ekstrand
---
src/intel/isl/isl.c | 13 +++--
src/intel/isl/isl.h | 3 ---
2 files changed, 3 insertions(+), 13 deletions(-)
diff --git a/src/intel/isl/isl.c b/src/intel/isl/isl.c
index 357f98f6b24..22ef57a561a 10064
It does the obvious.
bdw => 80
hsw => 75
ivb => 70
...
g4x => 45
---
src/intel/common/gen_device_info.c | 11 +++
src/intel/common/gen_device_info.h | 3 +++
2 files changed, 14 insertions(+)
diff --git a/src/intel/common/gen_device_info.c
b/src/intel/common/gen_devi
isl will use this for validating the depth buffer pitch.
---
src/intel/genxml/gen5.xml | 56 +++
1 file changed, 56 insertions(+)
diff --git a/src/intel/genxml/gen5.xml b/src/intel/genxml/gen5.xml
index 39fec3723f6..97c13699673 100644
--- a/src/intel/ge
Validate that isl_surf::row_pitch fits in the below bitfields,
if applicable based on isl_surf::usage.
RENDER_SURFACE_STATE::SurfacePitch
RENDER_SURFACE_STATE::AuxiliarySurfacePitch
3DSTATE_DEPTH_BUFFER::SurfacePitch
3DSTATE_HIER_DEPTH_BUFFER::SurfacePitch
---
src/intel/isl/isl.c
genX_bits.h contains the sizes of bitfields in genxml instructions,
structures, and registers. It also defines some functions to query those
sizes.
Currently, the bitfields in genX_bits.h are those whose name matches
/.*Surface(Q?)Pitch/.
isl_surf_init() will use the new header to validate that r
For each structure or instruction member in gen*_pack.h whose name
matches /.*Surface(Q?)Pitch$", add a macro that defines the member's
bitfield size.
isl will use these macros to validate requested pitches.
Example: Changes to RENDER_SURFACE_STATE in gen9_pack.h:
#define GEN9_RENDER_SURFACE_S
All callers of isl_surf_init() that set 'min_pitch' wanted to
request an *exact* row pitch, as evidenced by nearby asserts, but isl
lacked API for doing so. This series fixes that by adding a field,
isl_surf_init_info::row_pitch.
This prepares for VK_MESAX_external_image_dma_buf, which requires
su
The caller does so by setting the new field
isl_surf_init_info::row_pitch.
v2: Validate the requested row_pitch.
Reviewed-by: Jason Ekstrand (v2)
---
src/intel/isl/isl.c | 14 +-
src/intel/isl/isl.h | 6 ++
2 files changed, 19 insertions(+), 1 deletion(-)
diff --git a/src/inte
All callers of isl_surf_init() that set 'min_row_pitch' wanted to
request an *exact* row pitch, as evidenced by nearby asserts, but isl
lacked API for doing so. Now that isl has an API for that, update the
code to use it.
v2: Assert that isl_surf_init() succeeds because the callers assume
it.
On 22 March 2017 at 08:18, Marek Olšák wrote:
> From: Marek Olšák
For the first 2,
Reviewed-by: Dave Airlie
>
> ---
> src/gallium/auxiliary/gallivm/lp_bld_misc.cpp | 11 ---
> src/gallium/auxiliary/gallivm/lp_bld_misc.h | 3 ---
> src/gallium/drivers/radeonsi/si_shader.c | 2
This looks like a bug in LLVM. Not sure if Mesa should do anything about it:
llvm-config --cxxflags
-I/usr/llvm/x86_64-linux-gnu/include -fPIC
-fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W
-Wno-unused-parameter -Wwrite-strings -Wcast-qual
-Wno-missing-field-initializers -pedan
Both are
Reviewed-by: Jason Ekstrand
On Tue, Mar 21, 2017 at 2:57 PM, Anuj Phogat wrote:
> Yf/Ys tiling never got used in i965 due to not delivering
> the expected performance benefits. So, this patch is deleting
> this dead code in favor of adding it later in ISL when we
> actually find it us
From: Marek Olšák
I get -fno-rtti-DLLVM_... in LLVM_CXX_FLAGS, so add spaces.
---
configure.ac | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure.ac b/configure.ac
index 8c9d756..480f493 100644
--- a/configure.ac
+++ b/configure.ac
@@ -909,23 +909,23 @@ llvm_add_ta
From: Marek Olšák
---
src/amd/common/ac_llvm_helper.cpp | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/src/amd/common/ac_llvm_helper.cpp
b/src/amd/common/ac_llvm_helper.cpp
index 4f03103..83ad7ff 100644
--- a/src/amd/common/ac_llvm_helper.cpp
+++ b/src/amd/common/ac
From: Marek Olšák
---
src/gallium/auxiliary/gallivm/lp_bld_misc.cpp | 11 ---
src/gallium/auxiliary/gallivm/lp_bld_misc.h | 3 ---
src/gallium/drivers/radeonsi/si_shader.c | 2 +-
3 files changed, 1 insertion(+), 15 deletions(-)
diff --git a/src/gallium/auxiliary/gallivm/lp_bld
Yf/Ys tiling never got used in i965 due to not delivering
the expected performance benefits. So, this patch is deleting
this dead code in favor of adding it later in ISL when we
actually find it useful. ISL can then share this code between
vulkan and GL.
Signed-off-by: Anuj Phogat
Cc: Kenneth Gra
Fast copy blit was primarily added to support Yf/Ys detiling.
But, Yf/Ys tiling never got used in i965 due to not delivering
the expected performance benefits. Also, replacing legacy blits
with fast copy blit didn't help the benchmarking numbers. This
is probably due to a h/w restriction that says
On 03/17/2017 05:20 AM, Jan Vesely wrote:
> On Thu, 2017-03-16 at 18:07 -0700, Francisco Jerez wrote:
>> Jan Vesely writes:
>>
>>> On Thu, 2017-03-16 at 17:22 -0700, Francisco Jerez wrote:
Jan Vesely writes:
> On Thu, 2017-03-16 at 15:24 -0700, Francisco Jerez wrote:
>> Jan Vese
Ok, I think we're finally good to land. Whole series is
Reviewed-by: Jason Ekstrand
in case you were still missing any.
On Tue, Mar 21, 2017 at 2:27 PM, Ben Widawsky wrote:
> At image creation create a path for dealing with the linear modifier.
> This works exactly like the old usage flags w
The query is a properties query so it needs to be handled in
GetPhysicalDeviceProperties2, not GetPhysicalDeviceFeatures2.
Cc: Lionel Landwerlin
---
src/intel/vulkan/anv_device.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/src/intel/vulkan/anv_device.c b/
At image creation create a path for dealing with the linear modifier.
This works exactly like the old usage flags where __DRI_IMAGE_USE_LINEAR
was specified.
During development of this patch series, it was decided that a lack of
modifier was an insufficient way to express the required modifiers. A
---
src/mesa/drivers/dri/i965/.gitignore | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 src/mesa/drivers/dri/i965/.gitignore
diff --git a/src/mesa/drivers/dri/i965/.gitignore
b/src/mesa/drivers/dri/i965/.gitignore
new file mode 100644
index 000..e21ae5c
--- /dev/null
+++ b/src/m
On 17-03-21 14:15:05, Jason Ekstrand wrote:
On Tue, Mar 21, 2017 at 2:09 PM, Ben Widawsky wrote:
At image creation create a path for dealing with the linear modifier.
This works exactly like the old usage flags where __DRI_IMAGE_USE_LINEAR
was specified.
During development of this patch serie
Hey Kai,
Quoting Kai Wasserbäch (2017-03-21 11:36:31)
> I hope the rest of the Mesa project would follow such a rule. Because if
> there's
> something I absolutely hate about all those "new" build systems, then it's
> their
> tendency to just download stuff and build/include that. This seems to
On Tue, Mar 21, 2017 at 2:09 PM, Ben Widawsky wrote:
> At image creation create a path for dealing with the linear modifier.
> This works exactly like the old usage flags where __DRI_IMAGE_USE_LINEAR
> was specified.
>
> During development of this patch series, it was decided that a lack of
> mod
This patch begins introducing how we'll actually handle the potentially
many modifiers coming in from the API, how we'll store them, and the
structure in the code to support it.
Prior to this patch, the Y-tiled modifier would be entirely ignored. It
shouldn't actually be used until this point beca
At image creation create a path for dealing with the linear modifier.
This works exactly like the old usage flags where __DRI_IMAGE_USE_LINEAR
was specified.
During development of this patch series, it was decided that a lack of
modifier was an insufficient way to express the required modifiers. A
On Tuesday, March 21, 2017 4:40:26 AM PDT Emil Velikov wrote:
> On 21 March 2017 at 11:14, Emil Velikov wrote:
> > On 20 March 2017 at 22:04, Kenneth Graunke wrote:
> >> This way they become part of libintel_common.la so I can use them in
> >> the i965 driver.
> >> ---
> >> src/intel/Makefile.so
On 17-03-21 13:52:12, Jason Ekstrand wrote:
On Tue, Mar 21, 2017 at 1:45 PM, Ben Widawsky wrote:
This patch begins introducing how we'll actually handle the potentially
many modifiers coming in from the API, how we'll store them, and the
structure in the code to support it.
Prior to this patc
On Tue, Mar 21, 2017 at 1:45 PM, Ben Widawsky wrote:
> This patch begins introducing how we'll actually handle the potentially
> many modifiers coming in from the API, how we'll store them, and the
> structure in the code to support it.
>
> Prior to this patch, the Y-tiled modifier would be entir
On 17-03-21 13:48:13, Jason Ekstrand wrote:
On Tue, Mar 21, 2017 at 1:45 PM, Ben Widawsky wrote:
At image creation create a path for dealing with the linear modifier.
This works exactly like the old usage flags where __DRI_IMAGE_USE_LINEAR
was specified.
During development of this patch serie
On Tue, Mar 21, 2017 at 1:45 PM, Ben Widawsky wrote:
> At image creation create a path for dealing with the linear modifier.
> This works exactly like the old usage flags where __DRI_IMAGE_USE_LINEAR
> was specified.
>
> During development of this patch series, it was decided that a lack of
> mod
This patch begins introducing how we'll actually handle the potentially
many modifiers coming in from the API, how we'll store them, and the
structure in the code to support it.
Prior to this patch, the Y-tiled modifier would be entirely ignored. It
shouldn't actually be used until this point beca
This doesn't really "do" anything because the default tiling for the
winsys buffer is X tiled. We do however want the X tiled modifier to
work correctly from the API perspective, which would imply that if you
set this modifier, and later do a get_modifier, you get back at least X
tiled.
Running wi
All the plumbing is in place so the extension just needs to be
advertised.
Signed-off-by: Ben Widawsky
Reviewed-by: Jason Ekstrand
---
src/mesa/drivers/dri/i965/intel_screen.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/mesa/drivers/dri/i965/intel_screen.c
b/src/mes
At image creation create a path for dealing with the linear modifier.
This works exactly like the old usage flags where __DRI_IMAGE_USE_LINEAR
was specified.
During development of this patch series, it was decided that a lack of
modifier was an insufficient way to express the required modifiers. A
New to the patch series after reordering things for landing smaller
chunks.
This will essentially enable modifiers from clients that were just
enabled in previous patches. A client could use the modifiers by
setting all of them at create, but had no way to actually query them
after creating the su
I intend to need to get to the devinfo structure, and storing the screen
is an easy way to do that.
It seems to be the consensus that you cannot share an image between
multiple screens.
Scape-goat: Rob Clark
Signed-off-by: Ben Widawsky
Reviewed-by: Eric Engestrom
Acked-by: Daniel Stone
Review
Signed-off-by: Ben Widawsky
---
src/mesa/drivers/dri/i965/intel_screen.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/mesa/drivers/dri/i965/intel_screen.c
b/src/mesa/drivers/dri/i965/intel_screen.c
index af9c9a45f3..b77933e100 100644
--- a/src/mesa/drivers/dri/i965/intel_screen.c
+
Signed-off-by: Ben Widawsky
---
src/gbm/backends/dri/gbm_dri.c | 28
1 file changed, 28 insertions(+)
diff --git a/src/gbm/backends/dri/gbm_dri.c b/src/gbm/backends/dri/gbm_dri.c
index a7ac149365..283a73454e 100644
--- a/src/gbm/backends/dri/gbm_dri.c
+++ b/src/gbm/b
v2 of the third chunk of Renderbuffer Decompression support. The big change over
the previous version is that now the INVALID modifier is explcitly disallowed in
the GBM layer (and the equivalent i965 functionality).
The other big change is the priority selection algorithm for modifiers.
As befor
> On Mar 19, 2017, at 4:37 PM, Emil Velikov wrote:
>
> On 19 March 2017 at 22:16, Miklós Máté wrote:
>> On 19/03/17 22:13, Emil Velikov wrote:
>>>
>>> Hi Miklós,
>>>
>>> On 19 March 2017 at 12:28, Miklós Máté wrote:
After this series the build goes further, but eventually stops wi
On Tue, Mar 21, 2017 at 8:07 PM, Grazvydas Ignotas wrote:
> This doesn't build for me:
>
> make[4]: Entering directory
> '/home/notaz/src/radeon/mesa/src/gallium/winsys/amdgpu/drm'
> CC amdgpu_bo.lo
> amdgpu_bo.c: In function ‘amdgpu_buffer_get_metadata’:
> amdgpu_bo.c:615:53: error: ‘AMDG
On Tue, Mar 21, 2017 at 11:56 AM, Emil Velikov wrote:
> On 21 March 2017 at 18:06, Matt Turner wrote:
>> (1) Non-recursive automake is necessary for parallel build performance
> Fully agree
>
>> (2) Non-recursive automake is intractably unmaintainable for
>> sufficiently large projects
> Not sure
On Tue, Mar 21, 2017 at 11:56 AM, Emil Velikov
wrote:
> On 21 March 2017 at 18:06, Matt Turner wrote:
> > On Tue, Mar 21, 2017 at 10:16 AM, Emil Velikov
> wrote:
> >> On 21 March 2017 at 15:57, Matt Turner wrote:
> >>> On Mon, Mar 20, 2017 at 12:39 PM, Emil Velikov <
> emil.l.veli...@gmail.com
This doesn't build for me:
make[4]: Entering directory
'/home/notaz/src/radeon/mesa/src/gallium/winsys/amdgpu/drm'
CC amdgpu_bo.lo
amdgpu_bo.c: In function ‘amdgpu_buffer_get_metadata’:
amdgpu_bo.c:615:53: error: ‘AMDGPU_TILING_SWIZZLE_MODE_SHIFT’
undeclared (first use in this function)
On Tue, Mar 21, 2017 at 2:05 PM, Emil Velikov wrote:
> On 20 March 2017 at 21:51, Jason Ekstrand wrote:
>> On Mon, Mar 20, 2017 at 8:18 AM, Emil Velikov
>> wrote:
>>> diff --git a/src/intel/Makefile.vulkan.am b/src/intel/Makefile.vulkan.am
>>> index 185780246e2..7aacdf4e094 100644
>>> --- a/src/
On 21 March 2017 at 18:06, Matt Turner wrote:
> On Tue, Mar 21, 2017 at 10:16 AM, Emil Velikov
> wrote:
>> On 21 March 2017 at 15:57, Matt Turner wrote:
>>> On Mon, Mar 20, 2017 at 12:39 PM, Emil Velikov
>>> wrote:
On 20 March 2017 at 18:30, Matt Turner wrote:
> On Mon, Mar 20, 2017
On Tue, Mar 21, 2017 at 10:57 AM, Timothy Arceri wrote:
> ---
> src/gallium/drivers/radeon/r600_test_dma.c | 3 +-
> src/util/rand_xor.c| 62
> --
> src/util/rand_xor.h| 6 ++-
> 3 files changed, 64 insertions(+), 7 de
Any users of KitKat are likely using an older version of Mesa and
KitKat support adds complexity to the make files. Dropping support
allows removing the MESA_LOLLIPOP_BUILD make variable in various make
files.
Signed-off-by: Rob Herring
Reviewed-by: Tapani Pälli
---
v2:
- keep LOCAL_MODULE_RELAT
The Android version defines are only needed for versions less than 4.2
which aren't really supported or tested.
Signed-off-by: Rob Herring
Reviewed-by: Tapani Pälli
---
v2:
- Update subject
- drop trailing \ on make variables
Android.common.mk | 4 +---
Android.mk
Commit 6facb0c08fa1 ("android: fix libz dynamic library dependencies")
added libz as a dependency, but this breaks host targets as the host
dependency is libz-host. As no host lib needs libz, just remove the
dependency for them.
Fixes: 6facb0c08fa1 "android: fix libz dynamic library dependencies"
The host libmesa_util is never used for Android builds, so remove it.
Signed-off-by: Rob Herring
Reviewed-by: Tapani Pälli
---
v2:
- no change
src/util/Android.mk | 35 ---
1 file changed, 35 deletions(-)
diff --git a/src/util/Android.mk b/src/util/Android.mk
i
This is a series of clean-ups and fixes to get Mesa master building on
AOSP master again. AOSP master recently changed from X.Y.Z versioning to
just the letter commonly used. Primarily, dropping KitKat and earlier
support removes most of the version number dependencies and fixes the
build.
I've dr
Fixed with the following command:
perl -pe 'BEGIN{undef $/;} s/ \\\n\n/\n\n/smg' $(find . -name 'Android.*')
Signed-off-by: Rob Herring
---
v2:
- new patch
Android.common.mk | 2 +-
src/compiler/Android.glsl.gen.mk | 4 ++--
src/compiler/Android.nir.mk
Hey Dylan,
Dylan Baker wrote on 21.03.2017 18:34:
> Quoting Kai Wasserbäch (2017-03-21 09:50:52)
>> I've just a few points, since I'm not too enthused by the prospect of having
>> to
>> deal with yet another build system with yet another slightly different
>> syntax.
>> But ultimately this is onl
On Tue, Mar 21, 2017 at 10:16 AM, Emil Velikov wrote:
> On 21 March 2017 at 15:57, Matt Turner wrote:
>> On Mon, Mar 20, 2017 at 12:39 PM, Emil Velikov
>> wrote:
>>> On 20 March 2017 at 18:30, Matt Turner wrote:
On Mon, Mar 20, 2017 at 6:55 AM, Emil Velikov
wrote:
> Seems like
Helps mainly Feral-ported games, due to their use of fma()
shader-db changes:
total instructions in shared programs : 3941587 -> 3940749 (-0.02%)
total gprs used in shared programs: 481511 -> 481460 (-0.01%)
total local used in shared programs : 27469 -> 27481 (0.04%)
total bytes used in sha
I hit an assert in the emiter while toying around with optimizations, because
ConstantFolding immediated a big int into a mad.
There is special handling for FMA/MAD in insnCanLoad, which is broken. With
this patch the special path should be not hit anymore. Anyway, the constraints
for the LIMMS ca
Hi Kai,
Quoting Kai Wasserbäch (2017-03-21 09:50:52)
> Hey Dylan,
> I've just a few points, since I'm not too enthused by the prospect of having
> to
> deal with yet another build system with yet another slightly different syntax.
> But ultimately this is only a "my 2 cents" e-mail, since others
On 03/21/2017 05:50 PM, Tim Rowley wrote:
> Function::getArgumentList() doesn't exist anymore, switch to using
> arg_begin() (existed back to at least llvm-3.6.0).
>
> CC:
> ---
> src/gallium/drivers/swr/rasterizer/jitter/blend_jit.cpp | 2 +-
> src/gallium/drivers/swr/rasterizer/jitter/fetc
On 21 March 2017 at 15:57, Matt Turner wrote:
> On Mon, Mar 20, 2017 at 12:39 PM, Emil Velikov
> wrote:
>> On 20 March 2017 at 18:30, Matt Turner wrote:
>>> On Mon, Mar 20, 2017 at 6:55 AM, Emil Velikov
>>> wrote:
Seems like we ended up all over the place, so let me try afresh.
CP DMA and PKT3_WRITE_DATA (in CmdUpdateBuffer) don't (currently) write
through L2. Therefore, to make these writes visible to later accesses
we must invalidate L2 rather than just writing it back, to avoid the
possibility that stale data is read through L2.
Cc: "17.0"
Signed-off-by: Alex Smith
Function::getArgumentList() doesn't exist anymore, switch to using
arg_begin() (existed back to at least llvm-3.6.0).
CC:
---
src/gallium/drivers/swr/rasterizer/jitter/blend_jit.cpp | 2 +-
src/gallium/drivers/swr/rasterizer/jitter/fetch_jit.cpp | 2 +-
src/gallium/drivers/swr/rasterizer
Stop trying to specify texture or renderbuffer objects for unsupported
EGL images. Generate the error codes specified in the OES_EGL_image
extension.
Signed-off-by: Philipp Zabel
---
EGLImageTargetTexture2D and EGLImageTargetRenderbuffer would call
the pipe driver's create_surface callback withou
Hey Dylan,
I've just a few points, since I'm not too enthused by the prospect of having to
deal with yet another build system with yet another slightly different syntax.
But ultimately this is only a "my 2 cents" e-mail, since others are way deeper
involved with Mesa and their opinion is what matte
On Tue, Mar 21, 2017 at 4:50 PM, Marek Olšák wrote:
> On Tue, Mar 21, 2017 at 10:03 AM, Nicolai Hähnle wrote:
>> On 20.03.2017 23:43, Marek Olšák wrote:
>>>
>>> From: Marek Olšák
>>>
>>> Add _GFX6 and _GFX9 suffixes to conflicting definitions.
>>>
>>> sid.h and gfx9d.h can now be included in the
On 03/21/2017 09:54 AM, Alex Deucher wrote:
On Tue, Mar 21, 2017 at 9:46 AM, Marek Olšák wrote:
On Tue, Mar 21, 2017 at 7:49 AM, Christian König
wrote:
Am 20.03.2017 um 23:49 schrieb Marek Olšák:
From: Leo Liu
Signed-off-by: Leo Liu
Acked-by: Alex Deucher
Did we ever released 53.14.4
Quoting Jani Nikula (2017-03-21 07:44:55)
> On Thu, 16 Mar 2017, Dylan Baker wrote:
> > First it's written in python, [...]
>
> How does meson handle python 2 vs. 3? How do you avoid issues in the
> build files wrt this? On Debian meson seems to depend on python 3, so
> are they fully python 3?
I would personally rather have scons and autotools than cmake. I've had the
misfortune of using all three, and cmake is not an improvement in my opinion.
Quoting Grazvydas Ignotas (2017-03-21 08:13:31)
> It might make sense to give more attention to cmake just because many
> mesa-related projects
On Mon, Mar 20, 2017 at 10:10 PM, Jonathan Gray wrote:
> On Mon, Mar 20, 2017 at 11:30:25AM -0700, Matt Turner wrote:
>> On Mon, Mar 20, 2017 at 6:55 AM, Emil Velikov
>> wrote:
>> > Seems like we ended up all over the place, so let me try afresh.
>> >
>> > Above all:
>> > - Saying "I don't care
On Mon, Mar 20, 2017 at 10:00 PM, Jonathan Gray wrote:
> On Tue, Mar 21, 2017 at 08:28:22AM +1100, Timothy Arceri wrote:
>>
>>
>> On 21/03/17 06:39, Emil Velikov wrote:
>> > On 20 March 2017 at 18:30, Matt Turner wrote:
>> > > On Mon, Mar 20, 2017 at 6:55 AM, Emil Velikov
>> > > wrote:
>> > > >
On 03/21/2017 02:51 AM, Christian König wrote:
Am 20.03.2017 um 23:49 schrieb Marek Olšák:
From: Leo Liu
Signed-off-by: Leo Liu
Ah, here it is. This one and the change to version 53.17 should be
squashed with the change to 53.14.
With that done the patch is Reviewed-by: Christian König
On Mon, Mar 20, 2017 at 12:39 PM, Emil Velikov wrote:
> On 20 March 2017 at 18:30, Matt Turner wrote:
>> On Mon, Mar 20, 2017 at 6:55 AM, Emil Velikov
>> wrote:
>>> Seems like we ended up all over the place, so let me try afresh.
>>>
>>> Above all:
>>> - Saying "I don't care" about your users
1 - 100 of 165 matches
Mail list logo
