---
src/mesa/drivers/dri/i965/brw_link.cpp | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_link.cpp
b/src/mesa/drivers/dri/i965/brw_link.cpp
index 16bfbaa..ab2484e 100644
--- a/src/mesa/drivers/dri/i965/brw_link.cpp
++
From: Iago Toral Quiroga
From the Cherryview PRM, Volume 7, 3D Media GPGPU Engine,
Register Region Restrictions:
"When source or destination is 64b (...), regioning in Align1
must follow these rules:
1. Source and destination horizontal stride must be aligned to
the same qword
From the Cherryview's PRM, Volume 7, 3D Media GPGPU Engine, Register Region
Restrictions, page 844:
"When source or destination datatype is 64b or operation is integer DWord
multiply, indirect addressing must not be used."
v2:
- Fix it for Broxton too.
Signed-off-by: Samuel Iglesias Gonsálv
https://bugs.freedesktop.org/show_bug.cgi?id=96543
--- Comment #1 from Ilia Mirkin ---
Renders fine (or at least not obviously wrong) on nvc0 if you run glretrace
--sb
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=96543
Fabian Maurer changed:
What|Removed |Added
URL||www.ragdollsoft.com/nballed
https://bugs.freedesktop.org/show_bug.cgi?id=96543
Bug ID: 96543
Summary: N-Ball editor shows only a blackscreen
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: no
On Tue, Jun 14, 2016 at 10:01 PM, Ian Romanick wrote:
> From: Ian Romanick
>
> There are quite a few pipelines that desktop applications (including a
> bunch of piglit test) can expect to have run but don't meet the GLES
> requirements. Instead of failing validation, just emit a debug message.
>
In the process of adding RGBX (XB24) format to mesa for Android, I
started seeing a new problem that makes the UI stop updating. It
happens about when the splash screen is stopped and the lock screen is
displayed. The display flickers on mouse movement, and it looks like
the screen is flipping to o
https://bugs.freedesktop.org/show_bug.cgi?id=96542
Michel Dänzer changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
Window rectangles apply to all framebuffer operations, either in
inclusive or exclusive mode. They may also be specified as part of a
blit operation.
In exclusive mode, any fragment inside any of the specified rectangles
will be discarded.
In inclusive mode, any fragment outside every rectangle w
v2: Merge with PIPE_SHADER_CAP_DOUBLES
Add CHIP_HEMLOCK
v3: only set the instruction on EG and CM
Signed-off-by: Jan Vesely
---
src/gallium/drivers/r600/r600_pipe.c | 8 +---
src/gallium/drivers/r600/r600_shader.c | 4 ++--
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git
On Monday, June 13, 2016, tournier.elie wrote:
> Hi,
>
> After a few weeks of coding, I wrote a new post on my blog (
> https://hopetech.github.io/). I speak about the progress of my project,
> the difficulties encountered and the tools I use.
>
> Happy reading,
> Elie
>
Hello Elie,
Thanks for
On Sat, Jun 11, 2016 at 9:02 AM, Jason Ekstrand wrote:
> ---
> src/mesa/drivers/dri/i965/gen8_surface_state.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/mesa/drivers/dri/i965/gen8_surface_state.c
> b/src/mesa/drivers/dri/i965/gen8_surface_state.c
> index ee4
Patches 5 and 6 are
Reviewed-by: Chad Versace
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
I can't find patches 1 and 2 in my inbox, but they have my r-b.
Reviewed-by: Chad Versace
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Wed, 15 Jun 2016 20:13:13 +0200, Jan Vesely wrote:
Signed-off-by: Jan Vesely
---
Untested (I don't have the required hw)
src/gallium/drivers/r600/r600_pipe.c | 5 -
src/gallium/drivers/r600/r600_shader.c | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/gall
This looks like a candidate for the stable branches.
Reviewed-by: Chad Versace
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Rob Herring writes:
> The expected stride calculation is completely wrong. It should
> ultimately be multiplying cpp and width rather than dividing. The width
> also needs to be aligned to the tiling width first before converting to
> stride bytes.
>
> The whole stride check here is possibly poin
Jose Fonseca writes:
> On 15/06/16 18:13, Emil Velikov wrote:
>> On 15 June 2016 at 15:58, Brian Paul wrote:
>>> Why is this change needed? Does some compiler balk at 1.f?
>>>
>> Since I'm the one 'to blame' for these patches I'll answer - consistency.
>> These are the only remaining cases wher
On 15/06/16 18:13, Emil Velikov wrote:
On 15 June 2016 at 15:58, Brian Paul wrote:
Why is this change needed? Does some compiler balk at 1.f?
Since I'm the one 'to blame' for these patches I'll answer - consistency.
These are the only remaining cases where the trailing zero was missing :-)
On Wed, Jun 15, 2016 at 12:18 PM, Jason Ekstrand
wrote:
>
>
> On Wed, Jun 15, 2016 at 12:16 PM, Jason Ekstrand
> wrote:
>
>>
>>
>> On Wed, Jun 15, 2016 at 10:34 AM, Chad Versace
>> wrote:
>>
>>> On Tue 14 Jun 2016, Jason Ekstrand wrote:
>>> > On Jun 14, 2016 4:23 PM, "Chad Versace"
>>> wrote:
I'd say the proper action is to fix the idx type... we have code like:
src/mesa/main/buffers.c: fb->_ColorDrawBufferIndexes[buf] = -1;
src/mesa/main/mtypes.h: GLint
_ColorDrawBufferIndexes[MAX_DRAW_BUFFERS]; /**< BUFFER_x or -1 */
-ilia
On Wed, Jun 15, 2016 at 3:25 PM, wrote:
> Fro
Hi list,
this is my very first patch and it's inspired by this one:
https://lists.freedesktop.org/archives/mesa-dev/2016-May/118822.html
to address the -Wtautological compiler warning
Cheers,
Francesco
___
mesa-dev mailing list
mesa-dev@lists.freedes
From: Francesco Ansanelli
---
src/mesa/state_tracker/st_cb_fbo.c |5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/src/mesa/state_tracker/st_cb_fbo.c
b/src/mesa/state_tracker/st_cb_fbo.c
index a53b95a..ba9955c 100644
--- a/src/mesa/state_tracker/st_cb_fbo.c
+++ b/src/me
On Thursday, June 9, 2016 9:00:43 AM PDT Alejandro Piñeiro wrote:
> On 09/06/16 05:50, Kenneth Graunke wrote:
> > On Wednesday, June 8, 2016 7:45:16 PM PDT Alejandro Piñeiro wrote:
> >> On 02/06/16 23:09, Kenneth Graunke wrote:
> >>> i965 has no special hardware for this, so we need to pass this va
On 15 June 2016 at 12:01, Ian Romanick wrote:
> From: Ian Romanick
>
> Based loosely on patches submitted ages ago by Thomas Helland.
>
> Signed-off-by: Ian Romanick
> ---
> docs/GL3.txt | 56
> 1 file changed, 56 insertions(+)
>
> diff -
On 15/06/16 18:57, Brian Paul wrote:
If the log file specified by the GALLIUM_LOG_FILE begins with '+', open
the file in append mode. This is useful to log all gallium output for
an entire piglit run, for example.
v2: put GALLIUM_LOG_FILE support inside an #ifdef DEBUG block.
---
src/gallium/
On Wed, Jun 15, 2016 at 12:16 PM, Jason Ekstrand
wrote:
>
>
> On Wed, Jun 15, 2016 at 10:34 AM, Chad Versace
> wrote:
>
>> On Tue 14 Jun 2016, Jason Ekstrand wrote:
>> > On Jun 14, 2016 4:23 PM, "Chad Versace" wrote:
>> > >
>> > > anv_pipeline_binding::index is a uint8_t, but some code assigned
On Wed, Jun 15, 2016 at 10:34 AM, Chad Versace
wrote:
> On Tue 14 Jun 2016, Jason Ekstrand wrote:
> > On Jun 14, 2016 4:23 PM, "Chad Versace" wrote:
> > >
> > > anv_pipeline_binding::index is a uint8_t, but some code assigned to it
> > > UINT16_MAX.
> > > ---
> > > src/intel/vulkan/anv_pipeline
On Wed, Jun 15, 2016 at 2:55 PM, Mike Gorchak
wrote:
> Hi,
>
> hm, could you check "cat ./src/mapi/es2api/glapi_mapi_tmp.h | grep
> glFramebufferParameteri" ?
>
> I can see void APIENTRY gl_dispatch_stub_888(GLenum target, GLenum pname,
> GLint param); instead of glFramebufferParameteri there.
>
>
BTW, glDispatchCompute() is from 3.1, and it is present.
glFramebufferParameteri() is from 3.1, but it is absent.
On Wed, Jun 15, 2016 at 2:55 PM, Mike Gorchak
wrote:
> Hi,
>
> hm, could you check "cat ./src/mapi/es2api/glapi_mapi_tmp.h | grep
> glFramebufferParameteri" ?
>
> I can see void APIE
Hi,
hm, could you check "cat ./src/mapi/es2api/glapi_mapi_tmp.h | grep
glFramebufferParameteri" ?
I can see void APIENTRY gl_dispatch_stub_888(GLenum target, GLenum pname,
GLint param); instead of glFramebufferParameteri there.
Also objdump -x for GLES 2.0 API shows absence of glFramebufferParam
On Wed, Jun 15, 2016 at 8:19 PM, Alex Deucher wrote:
> On Wed, Jun 15, 2016 at 2:13 PM, Jan Vesely wrote:
>> Signed-off-by: Jan Vesely
>> ---
>> Untested (I don't have the required hw)
>>
>> src/gallium/drivers/r600/r600_pipe.c | 5 -
>> src/gallium/drivers/r600/r600_shader.c | 2 +-
>> 2
v2: Merge with PIPE_SHADER_CAP_DOUBLES
Add CHIP_HEMLOCK
Signed-off-by: Jan Vesely
---
src/gallium/drivers/r600/r600_pipe.c | 8 +---
src/gallium/drivers/r600/r600_shader.c | 2 +-
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_pipe.c
b/src
Hm... those should be exposed:
https://cgit.freedesktop.org/mesa/mesa/tree/src/mapi/glapi/gen/ARB_framebuffer_no_attachments.xml
And the dEQP tests that check these also work correctly. What makes
you think they're not properly exposed? (Perhaps I'm confused re what
the "MAPI" interface is?)
-
Hello,
Just found that latest Mesa 11.2.2 and 12.0.0rc3 exposes version 3.1 of
OpenGL ES instead of 3.0 if i965 DRI driver is used on Intel Gen8
(Broadwell) or Gen9 (AppolloLake/Broxton) hardware.
At the same time some of GLES 3.1 functions are not available through MAPI
interface like glFramebuf
On Wed, Jun 15, 2016 at 2:13 PM, Jan Vesely wrote:
> Signed-off-by: Jan Vesely
> ---
> Untested (I don't have the required hw)
>
> src/gallium/drivers/r600/r600_pipe.c | 5 -
> src/gallium/drivers/r600/r600_shader.c | 2 +-
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git
Signed-off-by: Jan Vesely
---
Untested (I don't have the required hw)
src/gallium/drivers/r600/r600_pipe.c | 5 -
src/gallium/drivers/r600/r600_shader.c | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/gallium/drivers/r600/r600_pipe.c
b/src/gallium/drivers/r600/r
On Wed, Jun 15, 2016 at 1:35 PM, Ian Romanick wrote:
> On 06/15/2016 08:04 AM, Ilia Mirkin wrote:
>> On Tue, Jun 14, 2016 at 10:01 PM, Ian Romanick wrote:
>>> From: Ian Romanick
>>>
>>> Based loosely on patches submitted ages ago by Thomas Helland.
>>>
>>> Signed-off-by: Ian Romanick
>>> ---
>>
On Tuesday, June 14, 2016 7:01:59 PM PDT Ian Romanick wrote:
> From: Ian Romanick
>
> A nearly identical block already exists in the gen >= 6 block above.
>
> Signed-off-by: Ian Romanick
> ---
> src/mesa/drivers/dri/i965/intel_extensions.c | 9 -
> 1 file changed, 9 deletions(-)
>
> d
To match what's done in the automake build.
---
src/SConscript | 43 +++
src/mesa/SConscript | 43 ++-
2 files changed, 45 insertions(+), 41 deletions(-)
diff --git a/src/SConscript b/src/SConscript
index 4ba0a32
If the log file specified by the GALLIUM_LOG_FILE begins with '+', open
the file in append mode. This is useful to log all gallium output for
an entire piglit run, for example.
v2: put GALLIUM_LOG_FILE support inside an #ifdef DEBUG block.
---
src/gallium/auxiliary/os/os_misc.c | 15
Hi Eric,
Could you please push both the patches as I don't have the push access.
Thanks,
Nayan.
On Wed, Jun 15, 2016 at 10:28 PM, Eric Engestrom
wrote:
> On Wed, Jun 15, 2016 at 09:07:23PM +0530, Nayan Deshmukh wrote:
> > Signed-off-by: Nayan Deshmukh
>
> After all the fuss :)
> Reviewed-by:
On 06/15/2016 08:04 AM, Ilia Mirkin wrote:
> On Tue, Jun 14, 2016 at 10:01 PM, Ian Romanick wrote:
>> From: Ian Romanick
>>
>> Based loosely on patches submitted ages ago by Thomas Helland.
>>
>> Signed-off-by: Ian Romanick
>> ---
>> docs/GL3.txt | 56 +++
On Tue 14 Jun 2016, Jason Ekstrand wrote:
> On Jun 14, 2016 4:23 PM, "Chad Versace" wrote:
> >
> > anv_pipeline_binding::index is a uint8_t, but some code assigned to it
> > UINT16_MAX.
> > ---
> > src/intel/vulkan/anv_pipeline.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > d
On 15 June 2016 at 15:58, Brian Paul wrote:
> Why is this change needed? Does some compiler balk at 1.f?
>
Since I'm the one 'to blame' for these patches I'll answer - consistency.
These are the only remaining cases where the trailing zero was missing :-)
-Emil
__
On Wed, Jun 15, 2016 at 08:51:14PM +0530, Nayan Deshmukh wrote:
> Hi Eric,
>
> Sorry for the typo in commit message.
>
> I made two separate patches as one was for mesa and other for gallium it
Indeed, I completely missed that and you're right for doing it :)
Sent my r-b on the v2.
> has nothin
On Wed, Jun 15, 2016 at 09:07:23PM +0530, Nayan Deshmukh wrote:
> Signed-off-by: Nayan Deshmukh
After all the fuss :)
Reviewed-by: Eric Engestrom
> ---
> src/mesa/drivers/dri/r200/r200_swtcl.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/src/mesa/drivers/dri/
On Wed, Jun 15, 2016 at 03:38:04PM +0530, Nayan Deshmukh wrote:
> Signed-off-by: Nayan Deshmukh
Reviewed-by: Eric Engestrom
> ---
> src/gallium/auxiliary/draw/draw_pipe_clip.c | 2 +-
> src/gallium/auxiliary/gallivm/lp_bld_arit.c | 4 ++--
> src/gallium/drivers/i915/i915_state_emit.c |
If the log file specified by the GALLIUM_LOG_FILE begins with '+', open
the file in append mode. This is useful to log all gallium output for
an entire piglit run, for example.
---
src/gallium/auxiliary/os/os_misc.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git
Signed-off-by: Nayan Deshmukh
---
src/mesa/drivers/dri/r200/r200_swtcl.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/mesa/drivers/dri/r200/r200_swtcl.c
b/src/mesa/drivers/dri/r200/r200_swtcl.c
index 72f09ae..d3fb37f 100644
--- a/src/mesa/drivers/dri/r200/r200_sw
Hi Brian,
Sorry for the typo in the commit message.
The patch was aimed to have a uniform coding style, just a suggestion given
by emil.
Regards,
Nayan.
On Wed, Jun 15, 2016 at 8:26 PM, Brian Paul wrote:
> On 06/15/2016 07:02 AM, Eric Engestrom wrote:
>
>> On Wed, Jun 15, 2016 at 03:38:05PM +
Hi Eric,
Sorry for the typo in commit message.
I made two separate patches as one was for mesa and other for gallium it
has nothing to do with the use of "f" and "F". Regarding replacing the "F"
with "f", maybe someone can shed some light as to why "F" was used
specifically.
Regards,
Nayan.
On
On Wed, Jun 15, 2016 at 4:38 AM, Nicolai Hähnle wrote:
> From: Nicolai Hähnle
>
> ---
> src/mesa/state_tracker/st_cb_fbo.h| 2 +
> src/mesa/state_tracker/st_cb_readpixels.c | 122
> ++
> 2 files changed, 110 insertions(+), 14 deletions(-)
>
> diff --git a/s
On 06/15/2016 02:38 AM, Nicolai Hähnle wrote:
Hi,
some applications use successive calls to glReadPixels to read data back.
This typically involves a GPU-based blit for each call for de-tiling or
format conversions (e.g. BGRA -> RGBA). Even when the _mesa_readpixels path
is used, such a blit ten
On Tue, Jun 14, 2016 at 10:01 PM, Ian Romanick wrote:
> From: Ian Romanick
>
> Based loosely on patches submitted ages ago by Thomas Helland.
>
> Signed-off-by: Ian Romanick
> ---
> docs/GL3.txt | 56
> 1 file changed, 56 insertions(+)
>
Why is this change needed? Does some compiler balk at 1.f?
-Brian
On 06/15/2016 04:08 AM, Nayan Deshmukh wrote:
Signed-off-by: Nayan Deshmukh
---
src/gallium/auxiliary/draw/draw_pipe_clip.c | 2 +-
src/gallium/auxiliary/gallivm/lp_bld_arit.c | 4 ++--
src/gallium/drivers/i915/i915_sta
This is pretty useful for debugging purposes and those should
not be omitted.
Fixes: 517a93b3 ("nvc0: add ARB_shader_draw_parameters support")
Signed-off-by: Samuel Pitoiset
---
src/gallium/drivers/nouveau/codegen/nv50_ir_print.cpp | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/galli
On 15 June 2016 at 14:07, Christian König wrote:
> Please split that up into multiple parts. E.g. adding the config
> structure, new image format support etc..
>
> Julien, can you take a look as well if you have time and work a bit with
> Boyuan to get this cleaned up?
>
Hi,
I'll be happy to do
Please split that up into multiple parts. E.g. adding the config
structure, new image format support etc..
Julien, can you take a look as well if you have time and work a bit with
Boyuan to get this cleaned up?
Thanks in advance,
Christian.
Am 14.06.2016 um 22:14 schrieb Boyuan Zhang:
Signe
Am 14.06.2016 um 22:14 schrieb Boyuan Zhang:
Signed-off-by: Boyuan Zhang
We need to find an interface that works both for OpenMAX as well as
VA-API and not implement a separate interface for each state tracker.
So I would suggest to implement the logic to provide the reference
picture list
On Wed, Jun 15, 2016 at 03:38:05PM +0530, Nayan Deshmukh wrote:
> Signed-off-by: Nayan Deshmukh
> ---
> src/mesa/drivers/dri/r200/r200_swtcl.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/src/mesa/drivers/dri/r200/r200_swtcl.c
> b/src/mesa/drivers/dri/r200/r200
Am 14.06.2016 um 22:14 schrieb Boyuan Zhang:
Signed-off-by: Boyuan Zhang
---
src/gallium/include/pipe/p_video_state.h | 13 +
1 file changed, 13 insertions(+)
diff --git a/src/gallium/include/pipe/p_video_state.h
b/src/gallium/include/pipe/p_video_state.h
index d353be6..d519d17
Am 14.06.2016 um 22:14 schrieb Boyuan Zhang:
Signed-off-by: Boyuan Zhang
As I said before please drop this change as it is unrelated to
supporting encoding with VA-API and we need to find a conclusion on how
to handle things first.
Christian.
---
src/gallium/drivers/radeon/radeon_vce.h
The third release candidate for Mesa 12.0.0 is now available.
Note for distribution maintainers:
Mesa no longer provides a single VAAPI driver backend - gallium_drv_video.
With this release separate drivers are available analogous to DRI, XvMC and
VDPAU.
Anuj Phogat (3):
blorp: Fix 16x m
Signed-off-by: Nayan Deshmukh
---
src/mesa/drivers/dri/r200/r200_swtcl.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/mesa/drivers/dri/r200/r200_swtcl.c
b/src/mesa/drivers/dri/r200/r200_swtcl.c
index 72f09ae..d3fb37f 100644
--- a/src/mesa/drivers/dri/r200/r200_sw
Signed-off-by: Nayan Deshmukh
---
src/gallium/auxiliary/draw/draw_pipe_clip.c | 2 +-
src/gallium/auxiliary/gallivm/lp_bld_arit.c | 4 ++--
src/gallium/drivers/i915/i915_state_emit.c | 2 +-
src/gallium/drivers/nouveau/nouveau_fence.c | 2 +-
src/gallium/drivers/nouveau/nv30/nv30_draw.c
From: Nicolai Hähnle
---
src/mesa/state_tracker/st_cb_readpixels.c | 8
src/mesa/state_tracker/st_context.c | 3 +++
src/mesa/state_tracker/st_context.h | 11 +++
3 files changed, 22 insertions(+)
diff --git a/src/mesa/state_tracker/st_cb_readpixels.c
b/src/mesa/
From: Nicolai Hähnle
---
src/mesa/state_tracker/st_cb_readpixels.c | 130 ++
1 file changed, 78 insertions(+), 52 deletions(-)
diff --git a/src/mesa/state_tracker/st_cb_readpixels.c
b/src/mesa/state_tracker/st_cb_readpixels.c
index 42ff73b..ef575ba 100644
--- a/src/
From: Nicolai Hähnle
---
src/mesa/state_tracker/st_cb_fbo.h| 2 +
src/mesa/state_tracker/st_cb_readpixels.c | 122 ++
2 files changed, 110 insertions(+), 14 deletions(-)
diff --git a/src/mesa/state_tracker/st_cb_fbo.h
b/src/mesa/state_tracker/st_cb_fbo.h
i
From: Nicolai Hähnle
Found by inspection.
Cc: 11.2 12.0
---
src/mesa/state_tracker/st_cb_copyimage.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/mesa/state_tracker/st_cb_copyimage.c
b/src/mesa/state_tracker/st_cb_copyimage.c
index 617e470..8afb861 100644
--- a/src/mesa/state_tr
From: Nicolai Hähnle
Whenever a draw happens or some other function call might change the result
of future glReadPixels calls, we must invalidate the cache.
---
src/mesa/state_tracker/st_atom_framebuffer.c | 1 +
src/mesa/state_tracker/st_cb_bitmap.c| 3 +++
src/mesa/state_tracker/st_cb_
From: Nicolai Hähnle
In the unlikely case that a program uses glBitmap to render to a framebuffer
whose texture is bound in a compute shader.
Found by inspection.
Cc: 11.2 12.0
---
src/mesa/state_tracker/st_cb_compute.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/mesa/state_tra
From: Nicolai Hähnle
As far as I can tell, a sequence of glBitmap followed by texture functions
that refer to a texture bound as the framebuffer is well within what should
be allowed.
Found by inspection.
Cc: 11.2 12.0
---
src/mesa/state_tracker/st_cb_texture.c | 9 +
src/mesa/state_t
Hi,
some applications use successive calls to glReadPixels to read data back.
This typically involves a GPU-based blit for each call for de-tiling or
format conversions (e.g. BGRA -> RGBA). Even when the _mesa_readpixels path
is used, such a blit tends to be hidden behind the transfer operations.
On 14 June 2016 at 16:11, Nayan Deshmukh wrote:
> Hi Emil,
>
> Thanks for the review and the push. It was inspired by one of the reviews
> you gave me for my previous patch.
>
You're welcome Nayan. There's a few more [1] for when you want to ease
your mind of other things :-)
Thanks
Emil
[1] $ g
From: Iago Toral Quiroga
From the Cherryview PRM, Volume 7, 3D Media GPGPU Engine,
Register Region Restrictions:
"When source or destination is 64b (...), regioning in Align1
must follow these rules:
1. Source and destination horizontal stride must be aligned to
the same qword
From the Cherryview's PRM, Volume 7, 3D Media GPGPU Engine, Register Region
Restrictions, page 844:
"When source or destination datatype is 64b or operation is integer DWord
multiply, indirect addressing must not be used."
Signed-off-by: Samuel Iglesias Gonsálvez
Cc: "12.0"
Bugzilla: https
On 15.06.2016 04:01, Ian Romanick wrote:
From: Ian Romanick
Based loosely on patches submitted ages ago by Thomas Helland.
Signed-off-by: Ian Romanick
---
docs/GL3.txt | 56
1 file changed, 56 insertions(+)
diff --git a/docs/GL3.txt
On 14.06.2016 19:06, Marek Olšák wrote:
From: Marek Olšák
v2: fixup after renaming to util_queue_fence
---
src/gallium/winsys/radeon/drm/radeon_drm_cs.c | 22
src/gallium/winsys/radeon/drm/radeon_drm_cs.h | 4 +-
src/gallium/winsys/radeon/drm/radeon_drm_winsys.c | 63 ++---
80 matches
Mail list logo
