https://bugs.freedesktop.org/show_bug.cgi?id=44618
Jonathan Liu changed:
What|Removed |Added
CC||net...@gmail.com
--
You are receiving th
https://bugs.freedesktop.org/show_bug.cgi?id=64959
--- Comment #1 from Andrew Knight ---
If you build gallium targets, you additionally need to comment out the
xlib_sw_winsys include in src/gallium/auxilliary/pipe-loader/pipe_loader_sw.c
as it is not guarded either.
--
You are receiving this ma
On 05/29/2013 12:56 AM, Divick Kishore wrote:
Hi Brian,
thanks for your reply.
On Tue, May 28, 2013 at 9:33 PM, Brian Paul wrote:
I took at look at eglCreateContext(). It's basically:
EGLContext
eglCreateContext(EGLDisplay dpy, EGLConfig config, EGLContext share_list,
https://bugs.freedesktop.org/show_bug.cgi?id=65103
--- Comment #1 from Brian Paul ---
Looks good to me. I'll commit your patch in a bit.
--
You are receiving this mail because:
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@list
https://bugs.freedesktop.org/show_bug.cgi?id=65103
Brian Paul changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=64877
Aaron Watry changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail bec
https://bugs.freedesktop.org/show_bug.cgi?id=44618
Ross Burton changed:
What|Removed |Added
CC||r...@burtonini.com
--- Comment #24 from Ro
https://bugs.freedesktop.org/show_bug.cgi?id=44618
--- Comment #25 from Jonathan Liu ---
Created attachment 79975
--> https://bugs.freedesktop.org/attachment.cgi?id=79975&action=edit
Patch
Here is a new patch I did. I try to make it only affect the cross compile case.
--
You are receiving th
On 05/25/2013 12:12 AM, Zack Rusin wrote:
We need to clamp to make sure invalid shader doesn't crash our
driver. The spec says to return 0-th index for everything that's
out of bounds and to reset everything above the last scissor
to zero.
Signed-off-by: Zack Rusin
---
src/gallium/drivers/llv
On 05/25/2013 12:12 AM, Zack Rusin wrote:
The spec says that everything beyond last set viewport
is reset to zero so make sure to preserve that behavior.
Signed-off-by: Zack Rusin
---
src/gallium/auxiliary/draw/draw_cliptest_tmp.h |8
src/gallium/auxiliary/draw/draw_context.c
On 05/25/2013 12:12 AM, Zack Rusin wrote:
Viewport index should only be used on a per primitive basis, so
instead of fetching it from each vertex, potentially making each
vertex in a primitive use a different viewport index, which is
obviously broken, make sure that we only fetch from the first
v
On Fri, May 24, 2013 at 12:01 PM, Paul Berry wrote:
> On 16 May 2013 11:44, Anuj Phogat wrote:
>>
>> In traditional multisampled framebuffer rendering, color samples must be
>> explicitly resolved via BlitFramebuffer before doing the scaled blitting
>> of the framebuffer. So, scaled blitting of a
On Fri, May 24, 2013 at 2:41 PM, Eric Anholt wrote:
> Paul Berry writes:
>
>> On 16 May 2013 11:44, Anuj Phogat wrote:
>>
>>> This patch enables ext_framebuffer_multisample_blit_scaled extension
>>> on intel h/w >= gen6.
>>>
>>> Note: Patches for piglit tests to verify this functionality are out
https://bugs.freedesktop.org/show_bug.cgi?id=60518
--- Comment #4 from Brian Paul ---
The link to the trace doesn't work. Can you attach the trace to this bug
report?
Which Mesa driver are you using?
--
You are receiving this mail because:
You are the assignee for the bug.
___
I started this discussion with just some of the Intel folks, and Eric
suggested I bring it to the mesa-dev list.
The short version is: in my efforts to implement fast color clears on Intel
hardware, I've uncovered some problems with the fbo-sys-blit piglit test,
which I've traced to 3 bugs. I cou
On 29 May 2013 13:39, Paul Berry wrote:
> *I don't know what code is allocating the new front and back buffers; I
> just know from examining data in the debugger that it's happened (since the
> buffer names have changed). Note that I'm running my tests with a
> compositing desktop (Gnome 3), so
On Wed, May 29, 2013 at 01:39:00PM -0700, Paul Berry wrote:
> I started this discussion with just some of the Intel folks, and Eric
> suggested I bring it to the mesa-dev list.
>
> The short version is: in my efforts to implement fast color clears on Intel
> hardware, I've uncovered some problems
On Wed, May 29, 2013 at 10:06 AM, Anuj Phogat wrote:
> On Fri, May 24, 2013 at 12:01 PM, Paul Berry wrote:
>> On 16 May 2013 11:44, Anuj Phogat wrote:
>>>
>>> In traditional multisampled framebuffer rendering, color samples must be
>>> explicitly resolved via BlitFramebuffer before doing the sca
From: Dave Airlie
This is my attempt at fixing this as the CVE is making RH security team
care enough to make me look at this. (please upstream, security fixes are
more important than whatever else you are doing, if for no other reason than
it saves me having to fix stuff I've no real clue about)
Dave Airlie writes:
> From: Dave Airlie
>
> This is my attempt at fixing this as the CVE is making RH security team
> care enough to make me look at this. (please upstream, security fixes are
> more important than whatever else you are doing, if for no other reason than
> it saves me having to f
On Thu, May 30, 2013 at 10:21 AM, Eric Anholt wrote:
> Dave Airlie writes:
>
>> From: Dave Airlie
>>
>> This is my attempt at fixing this as the CVE is making RH security team
>> care enough to make me look at this. (please upstream, security fixes are
>> more important than whatever else you ar
On Tue, Jan 29, 2013 at 12:52 PM, Ian Romanick wrote:
> On 01/28/2013 05:06 PM, Frank Henigman wrote:
>>
>> Set fs_visitor::params_remap to NULL in the constructor.
>> This variable was potentially tested in
>> fs_visitor::remove_dead_constants()
>> before being set.
>>
>> Signed-off-by: Frank Hen
From: Dave Airlie
This is my attempt at fixing this as the CVE is making RH security team
care enough to make me look at this. (please upstream, security fixes are
more important than whatever else you are doing, if for no other reason than
it saves me having to fix stuff I've no real clue about)
On 05/29/2013 05:44 PM, Dave Airlie wrote:
From: Dave Airlie
This is my attempt at fixing this as the CVE is making RH security team
care enough to make me look at this. (please upstream, security fixes are
more important than whatever else you are doing, if for no other reason than
it saves me
On Mon, May 27, 2013 at 02:15:21AM +0400, Vadim Girlin wrote:
> This will help to improve dumps of the compute shaders,
> also it will be required for complete handling of RAT instructions in sb.
>
> Signed-off-by: Vadim Girlin
> ---
> src/gallium/drivers/r600/r600_isa.c | 19 ++
> src/gall
brw->ib.type is reset to -1 at the start of each batch. If there's no
index buffer, it won't get updated to a sensible value, resulting in
_mesa_primitive_restart_index's "Invalid index buffer type" assertion
tripping.
Fixes a regression since 7c87a3b5dac118697a9b67caa7b6d5cab60f316d.
NOTE: This
On 05/30/2013 05:48 AM, Tom Stellard wrote:
On Mon, May 27, 2013 at 02:15:21AM +0400, Vadim Girlin wrote:
This will help to improve dumps of the compute shaders,
also it will be required for complete handling of RAT instructions in sb.
Signed-off-by: Vadim Girlin
---
src/gallium/drivers/r600
On 05/29/2013 04:54 PM, Dave Airlie wrote:
From: Dave Airlie
This is my attempt at fixing this as the CVE is making RH security team
care enough to make me look at this. (please upstream, security fixes are
more important than whatever else you are doing, if for no other reason than
it saves me
In traditional multisampled framebuffer rendering, color samples must be
explicitly resolved via BlitFramebuffer before doing the scaled blitting
of the framebuffer. So, scaled blitting of a multisample framebuffer
takes two separate calls to BlitFramebuffer.
This patch implements the functionalit
On 05/29/2013 05:44 PM, Dave Airlie wrote:
From: Dave Airlie
This is my attempt at fixing this as the CVE is making RH security team
care enough to make me look at this. (please upstream, security fixes are
more important than whatever else you are doing, if for no other reason than
it saves me
30 matches
Mail list logo
