Signed-off-by: Pierre Moreau
---
Notes:
Changes in v4: Use the core define instead of the extension one (Karol
Herbst)
v3: Switch from using a pointer attribute to a vector (Francisco Jerez)
src/gallium/state_trackers/clover/api/program.cpp | 7 +++
1 file changed, 7 insertions(+)
Signed-off-by: Pierre Moreau
---
Notes:
Changes in v4: Use the core define instead of the extension one (Karol
Herbst)
v3: Throw an exception if the cl_khr_il_program extension is not supported
(Francisco Jerez)
src/gallium/state_trackers/clover/api/device.cpp | 7 +++
1 f
Signed-off-by: Pierre Moreau
---
Notes:
Changes in v4: do not advertise SPIR-V support if CLOVER_ALLOW_SPIRV is not
defined
v3: Advertise cl_khr_il_program if if the device support NATIVE as IR
src/gallium/state_trackers/clover/api/platform.cpp | 2 ++
src/gallium/state_trackers/clove
Signed-off-by: Pierre Moreau
---
Notes:
v3: Remove the const from the length argument of clCreateProgramWithIL
src/gallium/state_trackers/clover/api/dispatch.cpp | 2 +-
src/gallium/state_trackers/clover/api/program.cpp | 8
2 files changed, 9 insertions(+), 1 deletion(-)
diff --
Quoting Jason Ekstrand (2018-03-07 06:34:52)
> The original string map assumed that the mapping from strings to
> entrypoints was a bijection. This will not be true the moment we
> add entrypoint aliasing. This reworks things to be an arbitrary map
> from strings to non-negative signed integers.
https://bugs.freedesktop.org/show_bug.cgi?id=77449
Bug 77449 depends on bug 98856, which changed state.
Bug 98856 Summary: DIRT: Showdown broken graphics with Mesa built with -Ofast
https://bugs.freedesktop.org/show_bug.cgi?id=98856
What|Removed |Added
-
From: Ian Romanick
v4: Report progress. This actually helps one more shader!
---
src/intel/compiler/brw_fs.cpp | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/intel/compiler/brw_fs.cpp b/src/intel/compiler/brw_fs.cpp
index 7b51b1f..4937361 100644
--- a/src/intel/compi
From: Ian Romanick
v4: Only set BRW_ALIGN_16 on Gen < 10 (suggested by Matt). Don't reset
the access mode afterwards (suggested by Samuel and Matt). Add support
for CSEL not modifying the flags to more places (requested by Matt).
Reviewed-by: Matt Turner
---
src/intel/compiler/brw_disasm.c
---
.../drivers/swr/rasterizer/archrast/archrast.cpp | 45 ++
.../drivers/swr/rasterizer/archrast/events.proto | 28 ++
2 files changed, 73 insertions(+)
diff --git a/src/gallium/drivers/swr/rasterizer/archrast/archrast.cpp
b/src/gallium/drivers/swr/rasterizer
---
src/gallium/drivers/swr/rasterizer/archrast/archrast.cpp | 15 +++
src/gallium/drivers/swr/rasterizer/archrast/events.proto | 6 ++
.../drivers/swr/rasterizer/archrast/events_private.proto | 6 ++
src/gallium/drivers/swr/rasterizer/core/rasterizer_impl.h | 3 +++
4 fi
In the API event handler we want to share information between the core
layer and the API. Specifically, around associating various ids with
different kinds of events. For example, associate render pass id with
draw ids, or command buffer ids with draw ids.
---
.../drivers/swr/rasterizer/archrast/a
---
src/gallium/drivers/swr/rasterizer/jitter/builder_mem.cpp | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/drivers/swr/rasterizer/jitter/builder_mem.cpp
b/src/gallium/drivers/swr/rasterizer/jitter/builder_mem.cpp
index 67e415c..6fa60a1 100644
--- a/src/gallium/drivers/swr/raste
This is useful for archrast data collection. This greatly speeds up the
post processing script since there is significantly less events generated.
Finally, this is a simpler option to communicate to users than having
them directly adjust MAX_PRIMS_PER_DRAW and MAX_TESS_PRIMS_PER_DRAW.
---
.../dri
Removed specific split draw events.
---
.../drivers/swr/rasterizer/archrast/archrast.cpp | 22 ++
.../drivers/swr/rasterizer/archrast/events.proto | 4
.../swr/rasterizer/archrast/events_private.proto | 20
src/gallium/drivers/swr/rasterizer/cor
Supports popcnt on vector masks (e.g. <8 x i1>)
---
src/gallium/drivers/swr/rasterizer/jitter/builder_misc.cpp | 8
src/gallium/drivers/swr/rasterizer/jitter/builder_misc.h | 1 +
2 files changed, 9 insertions(+)
diff --git a/src/gallium/drivers/swr/rasterizer/jitter/builder_misc.cpp
---
src/gallium/drivers/swr/rasterizer/archrast/archrast.cpp | 6 +++---
src/gallium/drivers/swr/rasterizer/archrast/events.proto | 1 +
src/gallium/drivers/swr/rasterizer/archrast/events_private.proto | 2 ++
src/gallium/drivers/swr/rasterizer/core/api.cpp | 4 ++-
---
src/gallium/drivers/swr/rasterizer/jitter/builder_mem.h | 3 ++-
src/gallium/drivers/swr/rasterizer/jitter/fetch_jit.cpp | 7 ++-
2 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/src/gallium/drivers/swr/rasterizer/jitter/builder_mem.h
b/src/gallium/drivers/swr/rasterizer/jit
https://bugs.freedesktop.org/show_bug.cgi?id=28433
Timothy Arceri changed:
What|Removed |Added
Component|Other |Drivers/DRI/i915
Assignee|mes
https://bugs.freedesktop.org/show_bug.cgi?id=34361
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |NOTABUG
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=33786
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEEDINFO
https://bugs.freedesktop.org/show_bug.cgi?id=41162
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 03/02/2018 02:55 PM, Andres Gomez wrote:
> 2599b92eb97 changed Mesa's behavior to allow Compatiblity profile with
> 3.1, and fail when the driver doesn't implement it, if the Core
> profile is not requested by applications.
>
> Formerly, when requesting a 3.1 Compatibility profile Mesa would
>
https://bugs.freedesktop.org/show_bug.cgi?id=64386
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=65475
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=104302
--- Comment #12 from gloriouseggr...@gmail.com ---
Just thought I'd follow up and let you know the llvm "shoot" patch
(https://reviews.llvm.org/D43831) you provided works very well! The hack patch
for mesa works also. Thanks again!
--
You are r
https://bugs.freedesktop.org/show_bug.cgi?id=80933
Timothy Arceri changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=104302
--- Comment #13 from gloriouseggr...@gmail.com ---
(to clarify for other users -- use either the shoot "hack" patch for mesa, or
the llvm patch to remove the weirdly blinding "shoot" bug and ring-lights etc
on the submarine, not both)
--
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=95083
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |INVALID
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=104625
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=62046
Timothy Arceri changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
You're 4.5 hours too late, I'm afraid. I'd be happy to take some patches
though. :-)
On Wed, Mar 7, 2018 at 4:42 PM, Dylan Baker wrote:
> Quoting Jason Ekstrand (2018-03-07 06:34:52)
> > The original string map assumed that the mapping from strings to
> > entrypoints was a bijection. This will
You sent out a 56 patch series and didn't even wait 12 hours before pushing it?
Quoting Jason Ekstrand (2018-03-07 19:56:21)
> You're 4.5 hours too late, I'm afraid. I'd be happy to take some patches
> though. :-)
>
> On Wed, Mar 7, 2018 at 4:42 PM, Dylan Baker wrote:
>
> Quoting Jason Eks
Yes, that is what happened. That said, wrote that patch in September and
you've had about 6 months to look at it. The only particularly active Mesa
contributor who hasn't had access is Ilia.
On March 7, 2018 20:13:28 Dylan Baker wrote:
You sent out a 56 patch series and didn't even wait 1
On 03/05/2018 04:53 PM, Kenneth Graunke wrote:
> On Friday, February 23, 2018 3:56:06 PM PST Ian Romanick wrote:
>> From: Ian Romanick
>>
>> No changes on other platforms.
>>
>> Haswell, Ivy Bridge, and Sandy Bridge had similar results. (Haswell shown)
>> total instructions in shared programs: 130
https://bugs.freedesktop.org/show_bug.cgi?id=12652
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 03/05/2018 04:35 PM, Matt Turner wrote:
> On Fri, Feb 23, 2018 at 3:56 PM, Ian Romanick wrote:
>> From: Ian Romanick
>>
>> On vector platforms, this helps elide some constant loads.
>>
>> No changes on Broadwell or Skylake.
>>
>> Haswell
>> total instructions in shared programs: 13093793 -> 13
https://bugs.freedesktop.org/show_bug.cgi?id=69682
Timothy Arceri changed:
What|Removed |Added
CC||aux...@gmail.com
--- Comment #9 from Ti
https://bugs.freedesktop.org/show_bug.cgi?id=66359
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=103852
--- Comment #4 from Ben Clapp ---
Bug(s) still present as of 17.3.6. (The issues related to frame drops/frame
presentation don't seem to be an issue at this point, but crop setting still
results in black screen, incorrect colors, etc. persist)
On 03/07/2018 04:29 PM, Emil Velikov wrote:
On 7 March 2018 at 06:02, Tapani Pälli wrote:
On 03/07/2018 12:36 AM, Marek Olšák wrote:
On Mon, Mar 5, 2018 at 7:33 AM, Tapani Pälli
wrote:
Hi;
On 03/02/2018 03:25 PM, Andres Gomez wrote:
This way we won't fail when validating just becau
Looks good to me.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
https://bugs.freedesktop.org/show_bug.cgi?id=105171
--- Comment #4 from Clemens Eisserer ---
just some unrelated, interesting numbers:
Sync time adjustment is 0.0355 msecs.
800 reps @ 0.0012 msec (816000.0/sec): ShmPutImage 10x10 square
800 reps @ 0.0012 msec (818000.0/sec):
Hi Brian,
> Looks good to me. Definitely seems like another step in the right
> direction.
>
> Just two minor comments:
>
> 1. A lot of local vars are named "glarray" and "glbinding". I'd suggest
> dropping the "gl" part since it doesn't really help with readability
> (everything's "gl" in
Hi Emil,
On Tuesday, 6 March 2018 12:13:07 CET Emil Velikov wrote:
> Just putting forward some suggestions. Please take them with a pinch of
salt.
You are welcome!
> Wondering if one cannot split this up somehow. Perhaps introduce
> gl_vertex_array::VertexAttrib first and the gl_vertex_buffer_b
https://bugs.freedesktop.org/show_bug.cgi?id=105171
--- Comment #5 from Dieter Nützel ---
Marek,
any ideas?
My Polaris 20 is somewhat faster, but by no means like Nvidia blob.
git revert xxx do NOT work, clean.
Someone on Phoronix mentioned that fglrx was even much faster then Mesa git
before y
Add support for the EXT_direct_mode_display extension. This just
provides the vkReleaseDisplayEXT function.
Signed-off-by: Keith Packard
---
src/amd/vulkan/radv_extensions.py | 1 +
src/amd/vulkan/radv_wsi_display.c | 11 +++
2 files changed, 12 insertions(+)
diff --git a/src/amd/vulka
This adds support for the KHR_display extension to the radv Vulkan
driver. The driver now attempts to open the master DRM node when the
KHR_display extension is requested so that the common winsys code can
perform the necessary operations.
v2:
* Simplify addition of VK_USE_PLATFORM_DISPLAY
Add support for the EXT_direct_mode_display extension. This just
provides the vkReleaseDisplayEXT function.
Signed-off-by: Keith Packard
---
src/vulkan/wsi/wsi_common_display.c | 17 +
src/vulkan/wsi/wsi_common_display.h | 5 +
2 files changed, 22 insertions(+)
diff --git a
This extension is required to support EXT_display_control as it offers
a way to query whether the vblank counter is supported.
v4: Add anv support
Signed-off-by: Keith Packard
---
src/intel/vulkan/anv_extensions.py | 1 +
src/intel/vulkan/anv_wsi.c | 12
2 files changed, 1
This extension adds a single function to query the current GPU
timestamp, just like glGetInteger64v(GL_TIMESTAMP, ×tamp). This
function is needed to complete the implementation of
GOOGLE_display_timing, which needs to be able to correlate GPU and CPU
timestamps.
Signed-off-by: Keith Packard
---
This adds support for the VK_GOOGLE_display timing extension, which
provides two things:
1) Detailed information about when frames are displayed, including
slack time between GPU execution and display frame.
2) Absolute time control over swapchain queue processing. This allows
the appli
This extension adds the ability to borrow an X RandR output for
temporary use directly by a Vulkan application to the radv driver.
v2:
Simplify addition of VK_USE_PLATFORM_XLIB_XRANDR_KHR to
vulkan_wsi_args
Suggested-by: Eric Engestrom
Signed-off-by: Keith Packard
---
This adds support for the VK_GOOGLE_display timing extension.
Signed-off-by: Keith Packard
---
src/intel/vulkan/anv_extensions.py | 1 +
src/intel/vulkan/anv_wsi.c | 29 +
2 files changed, 30 insertions(+)
diff --git a/src/intel/vulkan/anv_extensions.py
b/s
This extension is required to support EXT_display_control as it offers
a way to query whether the vblank counter is supported.
v2: Thanks to kisak
Fix spelling of VkSurfaceCapabilities2EXT in wsi_common_wayland.c,
it was using ext instead of EXT.
Fix spelling of VK_STRUCTURE_TYPE_SUR
This adds support for the KHR_display extension to the anv Vulkan
driver. The driver now attempts to open the master DRM node when the
KHR_display extension is requested so that the common winsys code can
perform the necessary operations.
v2: Make sure primary fd is usable
When KHR_displa
This extension adds a single function to query the current GPU
timestamp, just like glGetInteger64v(GL_TIMESTAMP, ×tamp). This
function is needed to complete the implementation of
GOOGLE_display_timing, which needs to be able to correlate GPU and CPU
timestamps.
Signed-off-by: Keith Packard
---
This adds support for the KHR_display extension support to the vulkan
WSI layer. Driver support will be added separately.
v2:
* fix double ;; in wsi_common_display.c
* Move mode list from wsi_display to wsi_display_connector
* Fix scope for wsi_display_mode andwsi_display
Here's a new clean version of all of the direct display patches with
fixes suggested by Jason integrated, instead of being made on top of
the patch series.
I've also rebased all of these patches on current master, which
includes the WSI changes to support multiple buffers per image, but
I'm not su
This extension adds a single function to query the current GPU
timestamp, just like glGetInteger64v(GL_TIMESTAMP, ×tamp). This
function is needed to complete the implementation of
GOOGLE_display_timing, which needs to be able to correlate GPU and CPU
timestamps.
Signed-off-by: Keith Packard
---
Add support for the EXT_direct_mode_display extension. This just
provides the vkReleaseDisplayEXT function.
Signed-off-by: Keith Packard
---
src/intel/vulkan/anv_extensions.py | 1 +
src/intel/vulkan/anv_wsi_display.c | 11 +++
2 files changed, 12 insertions(+)
diff --git a/src/intel/v
This extension provides fences and frame count information to direct
display contexts. It uses new kernel ioctls to provide 64-bits of
vblank sequence and nanosecond resolution.
Signed-off-by: Keith Packard
---
src/amd/vulkan/radv_extensions.py | 1 +
src/amd/vulkan/radv_private.h | 11 ++
This extension provides fences and frame count information to direct
display contexts. It uses new kernel ioctls to provide 64-bits of
vblank sequence and nanosecond resolution.
v2: Remove DRM_CRTC_SEQUENCE_FIRST_PIXEL_OUT flag. This has
been removed from the proposed kernel API.
Add NULL
This extension adds the ability to borrow an X RandR output for
temporary use directly by a Vulkan application. For DRM, we use the
Linux resource leasing mechanism.
v2:
Clean up xlib_lease detection
* Use separate temporary '_xlib_lease' variable to hold the
option valu
This extension provides fences and frame count information to direct
display contexts. It uses new kernel ioctls to provide 64-bits of
vblank sequence and nanosecond resolution.
Signed-off-by: Keith Packard
---
src/intel/vulkan/anv_extensions.py | 1 +
src/intel/vulkan/anv_private.h | 4
This extension is required to support EXT_display_control as it offers
a way to query whether the vblank counter is supported.
Signed-off-by: Keith Packard
---
src/amd/vulkan/radv_extensions.py | 1 +
src/amd/vulkan/radv_wsi.c | 12
2 files changed, 13 insertions(+)
diff -
This extension adds the ability to borrow an X RandR output for
temporary use directly by a Vulkan application to the anv driver.
v2:
Simplify addition of VK_USE_PLATFORM_XLIB_XRANDR_KHR to
vulkan_wsi_args
Suggested-by: Eric Engestrom
Signed-off-by: Keith Packard
---
s
This adds support for the VK_GOOGLE_display timing extension.
Signed-off-by: Keith Packard
---
src/amd/vulkan/radv_extensions.py | 1 +
src/amd/vulkan/radv_wsi.c | 33 -
2 files changed, 33 insertions(+), 1 deletion(-)
diff --git a/src/amd/vulkan/radv_ex
Add a new struct kms_sw_plane which delegate a plane and use it
in place of sw_displaytarget. Multiple planes share same underlying
kms_sw_displaytarget.
Change-Id: I0e9ca1d0ba0aa78c27dfdb50c30dc0c424fec172
Signed-off-by: Lepton Wu
---
.../winsys/sw/kms-dri/kms_dri_sw_winsys.c | 162
Excellent work and congratulations to everyone! This IS an awesome community
and I’m very proud of you.
Annie Matheson
From: Jason Ekstrand [mailto:ja...@jlekstrand.net]
Sent: Wednesday, March 7, 2018 3:09 PM
To: ML mesa-dev
Cc: Ekstrand, Jason ; Chema Casanova
; Iago Toral ; Samuel Iglesias
On Wed, 2018-03-07 at 07:46 -0800, Rodrigo Vivi wrote:
> Copied from Mesa with no modifications.
>
> Gives us Geminilake and Kaby Lake platform names updates and
> sync on Coffee Lake PCI IDs.
>
> Cc: Timo Aaltonen
> Signed-off-by: Rodrigo Vivi
Merged, thanks:
remote: I: patch #208689 updated
Thanks for reviewing, just back from vacation and send out V3 for review.
I split it to 2 patches now and I removed lazy unmap since it's unnecessary.
On Wed, Feb 21, 2018 at 7:42 AM, Emil Velikov wrote:
> HI Lepton,
>
> It seems that this has fallen through the cracks.
>
> There's one important
If user calls map twice for kms_sw_displaytarget, the first mapped
buffer could get leaked. Instead of calling mmap every time, just
reuse previous mapping. Since user could map same displaytarget with
different flags, we have to keep two different pointers, one for rw
mapping and one for ro mappin
201 - 272 of 272 matches
Mail list logo
