From: Dave Airlie
Older versions of virglrenderer before 33da7361aec486290df0aec4ad8dfa8ff6adde2c
in vtest mode, misrender gears.
Fixes: 9d81cd8e7c (virgl: Pass resource size and transfer offsets)
---
src/gallium/winsys/virgl/vtest/virgl_vtest_winsys.c | 2 +-
1 file changed, 1 insertion(+), 1
https://bugs.freedesktop.org/show_bug.cgi?id=109153
Hai changed:
What|Removed |Added
CC|xinyux.d...@intel.com |
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=109153
--- Comment #4 from Hai ---
*** Bug 109157 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the
https://bugs.freedesktop.org/show_bug.cgi?id=109151
Hai changed:
What|Removed |Added
CC|xinyux.d...@intel.com |
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=109151
--- Comment #5 from Hai ---
*** Bug 109158 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the
From: Dave Airlie
This fixes the drisw paths to use the new shm2 interface, so that
we don't trigger the X server overflow checks when the x offset is non-zero.
This just hides the versioning in drisw, and either passes the src_x
or adds the offset fixup for the fallback path.
---
From: Dave Airlie
This adds a new interface to the swrast interface to fix an shm put image bug.
The current code adds the x,y src offsets into the offset parameters,
however if the x offset is > 0, and the put image copies up to the height
of the image, this can trigger an X server validation
Back with
drisw: use putImageShm if available
this caused a regression when moving a window with mutter
off the edge of the screen in swrast mode.
I traced this down to the X server shm sizing checks, where
it validates the image offset can fit the height * stride
passed. Unfortunately since
From: Dave Airlie
Allow the src x,y to be specified and pass in the values from
the different interfaces to allow this.
---
src/glx/drisw_glx.c | 30 +++---
1 file changed, 23 insertions(+), 7 deletions(-)
diff --git a/src/glx/drisw_glx.c b/src/glx/drisw_glx.c
index
If the last-active context gets deleted, the pushbuf doesn't have a
bufctx to reference. Then there could be a sequence of binds which would
trigger a reset on that bin before validation was done. Instead we just
pass in the bufctx in question directly.
All other instances of PUSH_RESET happen
The whole user_priv thing is a mess, but as long as it's there, it
basically has to map 1:1 to the cur_ctx. Unfortunately we were setting
user_priv to some context, then that context could get deleted without
any draws/validations in it, leading user_priv to become NULL, with
cur_ctx still
https://bugs.freedesktop.org/show_bug.cgi?id=109138
Hai changed:
What|Removed |Added
QA Contact|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
https://bugs.freedesktop.org/show_bug.cgi?id=108878
Hai changed:
What|Removed |Added
Version|unspecified |18.3
Hardware|Other
https://bugs.freedesktop.org/show_bug.cgi?id=108878
Hai changed:
What|Removed |Added
QA Contact|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
https://bugs.freedesktop.org/show_bug.cgi?id=108877
Hai changed:
What|Removed |Added
QA Contact|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
Make sure that the next line starts with spaces so that bullets are
maintained throughout, add `` around a few more special tokens, and fix
SAMPLE_COUNT_TEXTURE -> SAMPLE_COUNT.
Signed-off-by: Ilia Mirkin
---
Hardly exhaustive or complete, but a handful of things I noticed.
https://bugs.freedesktop.org/show_bug.cgi?id=109151
--- Comment #4 from Hai ---
It's not an regression. I tried Mesa 18.2.2, it also failed, thanks.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109086
Ilia Mirkin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
On Wed, Dec 19, 2018 at 10:12 AM Brian Paul wrote:
>
> On 12/19/2018 06:47 AM, Ilia Mirkin wrote:
> > On Wed, Dec 19, 2018 at 8:38 AM Brian Paul wrote:
> >>
> >> On 12/18/2018 08:50 PM, Ilia Mirkin wrote:
> >>> Not sure if this ever worked, but the current logic for setting the
> >>> min/max
https://bugs.freedesktop.org/show_bug.cgi?id=109156
Bug ID: 109156
Summary: Meson doesn't always strip when --strip is used
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=109155
Bug ID: 109155
Summary: Update documentation for using custom llvm to build
Mesa with Meson
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=109151
--- Comment #3 from Bas Nieuwenhuizen ---
Is this a regression? If so what is the last working version of mesa for you?
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the
https://bugs.freedesktop.org/show_bug.cgi?id=109151
Bas Nieuwenhuizen changed:
What|Removed |Added
Product|DRI |Mesa
https://bugs.freedesktop.org/show_bug.cgi?id=109153
--- Comment #3 from Cheng ---
Thanks for your email. I’m OOO. Please expect slow email response.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109153
Bas Nieuwenhuizen changed:
What|Removed |Added
Component|DRM/AMDgpu |Drivers/Vulkan/radeon
On Tuesday, 2018-12-25 23:09:53 +0100, Jan Vesely wrote:
> Guess my meson-fu is still pretty weak.
> Now I see the build failure again:
> In file included from ../mesa/src/intel/vulkan/anv_private.h:77:0,
> from ../mesa/src/intel/vulkan/genX_pipeline.c:24:
>
26 matches
Mail list logo
