Hello Ilia,
On Thu, Jan 25, 2018 at 08:41:11AM -0500, Ilia Mirkin wrote:
> Should you also expose PIPE_CAP_TEXTURE_RECTANGLE? (Or whatever it's
> called... I forget.)
I checked and I don't think a capability exists for this (anymore?).
Everywhere, the assumption is meant that all Gallium
Subpixel precision bias, dilation and the post-snap mode are supported on
GM200 and newer. The pre-snap mode is supported for triangle primitives on
GP100.
v2: fix code to handle earlier hardware
---
src/gallium/drivers/nouveau/nvc0/nvc0_3d.xml.h | 5 +
Although the specs are written against compatibility GL 4.3 and allows core
profile and GLES2+, it is exposed for GL 1.0+ and GLES1 and GLES2+.
v2: fix indentation error in gl_API.xml
---
src/mapi/glapi/gen/gl_API.xml | 47 +++
src/mapi/glapi/gen/gl_genexec.py| 1 +
This patch-set adds support for GL_NV_conservative_raster and
GL_NV_conservative_raster_dilate on GM2xx and newer. It also adds support for
GL_NV_conservative_raster_pre_snap_triangles on GP1xx.
In doing so, it implements various functions in mesa core, extends the Gallium
API, connects the new
---
src/gallium/docs/source/cso/rasterizer.rst | 18 ++
src/gallium/docs/source/screen.rst | 18 ++
src/gallium/drivers/etnaviv/etnaviv_screen.c | 10 ++
src/gallium/drivers/freedreno/freedreno_screen.c | 10 ++
---
src/mesa/state_tracker/st_atom_rasterizer.c | 12 ++
src/mesa/state_tracker/st_atom_viewport.c | 4
src/mesa/state_tracker/st_context.c | 2 ++
src/mesa/state_tracker/st_extensions.c | 34 +
4 files changed, 52 insertions(+)
diff
On 22 March 2018 at 12:32, Juan A. Suarez Romero wrote:
> On Thu, 2018-03-22 at 12:08 +, Daniel Stone wrote:
>> On 22 March 2018 at 11:16, Juan A. Suarez Romero wrote:
>> > On Thu, 2018-03-22 at 11:03 +, Emil Velikov wrote:
>> > > On 21 March
On March 22, 2018 06:07:01 Tapani Pälli wrote:
On 03/22/2018 01:01 PM, Emil Velikov wrote:
Hi guys,
On 22 March 2018 at 08:23, Tomasz Figa wrote:
Hi Chih-Wei,
On Thu, Feb 22, 2018 at 2:53 PM, Chih-Wei Huang wrote:
https://bugs.freedesktop.org/show_bug.cgi?id=105396
soredake changed:
What|Removed |Added
CC||fds...@krutt.org
--
You
On 03/22/2018 01:01 PM, Emil Velikov wrote:
Hi guys,
On 22 March 2018 at 08:23, Tomasz Figa wrote:
Hi Chih-Wei,
On Thu, Feb 22, 2018 at 2:53 PM, Chih-Wei Huang wrote:
2018-02-21 3:03 GMT+08:00 Rob Herring :
Perhaps worth
On Thu, 2018-03-22 at 13:32 +0100, Juan A. Suarez Romero wrote:
> On Thu, 2018-03-22 at 12:08 +, Daniel Stone wrote:
> > On 22 March 2018 at 11:16, Juan A. Suarez Romero
> > wrote:
> > > On Thu, 2018-03-22 at 11:03 +, Emil Velikov wrote:
> > > > On 21 March 2018 at
On Thu, 2018-03-22 at 12:08 +, Daniel Stone wrote:
> On 22 March 2018 at 11:16, Juan A. Suarez Romero wrote:
> > On Thu, 2018-03-22 at 11:03 +, Emil Velikov wrote:
> > > On 21 March 2018 at 13:36, Daniel Stone wrote:
> > > > I thought we had
On Thu, 2018-03-22 at 02:36 +0100, Bas Nieuwenhuizen wrote:
> On Thu, Mar 8, 2018 at 12:59 PM, James Legg
> wrote:
> > This avoids bug 105396 somehow. I suspect it is a VI and GFX9 hardware
> > bug which PAL calls WaTcCompatZRange, but I don't know for sure.
> >
> >
On Monday, 2018-03-12 10:16:33 -0700, Dylan Baker wrote:
> Quoting Emil Velikov (2018-03-12 09:09:50)
> > On 12 March 2018 at 15:01, Eric Engestrom wrote:
> > > Signed-off-by: Eric Engestrom
> > > ---
> > > Dylan, was there any reason to have
On 22 March 2018 at 11:16, Juan A. Suarez Romero wrote:
> On Thu, 2018-03-22 at 11:03 +, Emil Velikov wrote:
>> On 21 March 2018 at 13:36, Daniel Stone wrote:
>> > I thought we had resolved earlier to _not_ ship files generated by
>> >
https://bugs.freedesktop.org/show_bug.cgi?id=105670
--- Comment #1 from Tapani Pälli ---
Could be related to loop unrolling (?) While playing back trace on i965 I saw
this:
--- 8< ---
glretrace: ../src/compiler/nir/nir_opt_loop_unroll.c:414: complex_unroll:
Assertion
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105440
Fixes: 2458ea95c56 "nir/lower_vec_to_movs: Coalesce movs on-the-fly when
possible"
Signed-off-by: Andriy Khulap
Signed-off-by: Vadym Shovkoplias
---
On Thu, 2018-03-22 at 11:03 +, Emil Velikov wrote:
> On 21 March 2018 at 13:36, Daniel Stone wrote:
> > Hi Juan,
> >
> > On 19 March 2018 at 17:49, Juan A. Suarez Romero
> > wrote:
> > > The first two patches in the series is a new fix for issue
>
On 21 March 2018 at 13:36, Daniel Stone wrote:
> Hi Juan,
>
> On 19 March 2018 at 17:49, Juan A. Suarez Romero wrote:
>> The first two patches in the series is a new fix for issue
>> https://bugs.freedesktop.org/show_bug.cgi?id=105211, as the current
Hi guys,
On 22 March 2018 at 08:23, Tomasz Figa wrote:
> Hi Chih-Wei,
>
> On Thu, Feb 22, 2018 at 2:53 PM, Chih-Wei Huang wrote:
>> 2018-02-21 3:03 GMT+08:00 Rob Herring :
>>>
>>> Perhaps worth revisiting. Given we've failed to progress
On Wed, 2018-03-21 at 13:36 +, Daniel Stone wrote:
> Hi Juan,
>
> On 19 March 2018 at 17:49, Juan A. Suarez Romero wrote:
> > The first two patches in the series is a new fix for issue
> > https://bugs.freedesktop.org/show_bug.cgi?id=105211, as the current version
> >
On 22 March 2018 at 08:21, Tomasz Figa wrote:
> Hi Rob,
>
> On Thu, Mar 22, 2018 at 12:16 AM, Robert Foss
> wrote:
>> Sharing the device between components
>> -
>>
>> Currently the device is used by drm_hwc,
On Thu, 2018-03-22 at 00:28 +, Emil Velikov wrote:
> Hi all,
>
> Having gone through the thread a few times, I believe it can be
> summarised as follows:
> * Greater transparency is needed.
> * Subsystem/team maintainers.
> * Unfit and late nominations.
> * Developers/everyone should be
Hi Stefan,
On Thu, Mar 22, 2018 at 8:42 AM, Stefan Schake wrote:
> Hey Robert,
>
> On Wed, Mar 21, 2018 at 4:16 PM, Robert Foss
> wrote:
>> Hey,
>>
>> I've started looking into removing the gralloc method
>> GRALLOC_MODULE_PERFORM_GET_DRM_FD.
>>
Hi Chih-Wei,
On Thu, Feb 22, 2018 at 2:53 PM, Chih-Wei Huang wrote:
> 2018-02-21 3:03 GMT+08:00 Rob Herring :
>>
>> Perhaps worth revisiting. Given we've failed to progress at all since
>> then may change opinions some. We already have to handle multiple
>>
Hi Rob,
On Thu, Mar 22, 2018 at 12:16 AM, Robert Foss wrote:
> Hey,
>
> I've started looking into removing the gralloc method
> GRALLOC_MODULE_PERFORM_GET_DRM_FD.
Thanks a lot for looking into this.
>
> The issues around this seems to be two parts:
> 1) Finding the
Reviewed-by: Alejandro Piñeiro
On 22/03/18 01:58, Ian Romanick wrote:
> From: Ian Romanick
>
> No shader-db changes. This source must have been written by a previous
> instruction, so it cannot be a uniform or a shader input. However, this
>
Reviewed-by: Alejandro Piñeiro
On 22/03/18 01:58, Ian Romanick wrote:
> From: Ian Romanick
>
> The math inside the add and the cmp in this instruction sequence is the
> same. We can utilize this to eliminate the compare.
>
> add(8)
Reviewed-by: Alejandro Piñeiro
On 22/03/18 01:58, Ian Romanick wrote:
> From: Ian Romanick
>
> No shader-db changes. This source must have been written by a previous
> instruction, so it cannot be a uniform or a shader input. However, this
>
Looks good in general, just a comment below.
On 22/03/18 01:58, Ian Romanick wrote:
> From: Ian Romanick
>
> This method is similar to the existing ::equals methods. Instead of
> testing that two src_regs are equal to each other, it tests that one is
> the negation of
Any reason to not add tests on test_vec4_cmod_propagation as the fs
equivalent did?
Also, two small comments below.
On 22/03/18 01:58, Ian Romanick wrote:
> From: Ian Romanick
>
> No changes on Broadwell and later becuase those plaforms do not use the
> vec4 backend at
On 21/03/18 22:10, Vinson Lee wrote:
This patch fixes these build errors with GCC 4.4.
Compiling src/gallium/auxiliary/util/u_debug_stack.c ...
src/gallium/auxiliary/util/u_debug_stack.c: In function
‘debug_backtrace_capture’:
src/gallium/auxiliary/util/u_debug_stack.c:268: error: #pragma
Reviewed-by: Timothy Arceri
As talked about on IRC I'll probably push this tomorrow morning unless
you get to it first.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
101 - 133 of 133 matches
Mail list logo