https://bugs.freedesktop.org/show_bug.cgi?id=10
--- Comment #1 from Axel Davy ---
Thank you for this bug report,
A similar issue for this game was reported long ago here:
https://github.com/iXit/Mesa-3D/issues/101
I had hoped it had been fixed since, but apparently not.
If you click
We had the flush/stall after the clear but missed the one that needs to
go before the clear.
Cc: mesa-sta...@lists.freedesktop.org
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107760
---
src/intel/vulkan/anv_blorp.c | 10 ++
1 file changed, 10 insertions(+)
diff --git
On Fri, Aug 31, 2018 at 04:04:22PM -0500, Jason Ekstrand wrote:
> We had the flush/stall after the clear but missed the one that needs to
> go before the clear.
>
Does this fix the GPU Hang in DiRT 3?
> Cc: mesa-sta...@lists.freedesktop.org
> Bugzilla:
On Fri 31 Aug 2018, Jason Ekstrand wrote:
> We had the flush/stall after the clear but missed the one that needs to
> go before the clear.
>
> Cc: mesa-sta...@lists.freedesktop.org
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107760
> ---
> src/intel/vulkan/anv_blorp.c | 10
https://bugs.freedesktop.org/show_bug.cgi?id=10
Axel Davy changed:
What|Removed |Added
CC||s...@das-labor.org
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=10
Bug ID: 10
Summary: No 3D in "Vampire: The Masquerade - Bloodlines" when
d3d-nine enabled
Product: Mesa
Version: 18.2
Hardware: x86-64 (AMD64)
OS:
Hi Andres,
The final blockers have been resolved. You should be able to make an RC
that passes all Intel validation, if you pick up:
904c2a617d8 * i965/gen7_urb: Re-emit PUSH_CONSTANT_ALLOC on some gen9
d9cf4308cee * i965/screen: Allow modifiers on sRGB formats
Looking forward to the release,
On Fri, Aug 31, 2018 at 4:35 PM Nanley Chery wrote:
> On Fri, Aug 31, 2018 at 04:04:22PM -0500, Jason Ekstrand wrote:
> > We had the flush/stall after the clear but missed the one that needs to
> > go before the clear.
> >
>
> Does this fix the GPU Hang in DiRT 3?
>
It appears to mostly fix it,
On Fri, Aug 31, 2018 at 4:05 PM Emil Velikov wrote:
>
> On 31 August 2018 at 14:36, Timothy Arceri wrote:
> > On 31/08/18 21:07, Emil Velikov wrote:
> >>
> >> On 31 August 2018 at 11:37, Timothy Arceri wrote:
> >>>
> >>> On 31/08/18 20:10, Emil Velikov wrote:
>
>
> Hi Timothy,
>
On Fri, Aug 31, 2018 at 11:05:13AM +0100, Lionel Landwerlin wrote:
> On 30/08/2018 22:41, Rodrigo Vivi wrote:
> > Whiskey Lake uses the same gen graphics as Coffe Lake, including some
> > ids that were previously marked as reserved on Coffe Lake, but that
> > now are moved to WHL page.
> >
> >
https://bugs.freedesktop.org/show_bug.cgi?id=107772
Ian Romanick changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #3 from Ian
This is basically what we do in i965 only we support two SRGB formats.
Acked-by: Jason Ekstrand
On Fri, Aug 31, 2018 at 11:37 AM Daniel Stone wrote:
> Though the SARGB format is used internally through its FourCC value,
> it is not a real format as defined by drm_fourcc.h; it cannot be
https://bugs.freedesktop.org/show_bug.cgi?id=107778
Bug ID: 107778
Summary: 3d renders does not work at all in game, only 2d (like
menus) shows up.
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS:
Juan, should we also include this in the stable queues ?
On Thu, 2018-08-30 at 13:59 +0200, Juan A. Suarez Romero wrote:
> If color buffer is locked, do not set its wayland buffer to NULL;
> otherwise it can not be freed later.
>
> Rather, flag it in order to destroy it later on the release
From: Marek Olšák
This prevents radeonsi from running out of memory. It also increases
texture upload performance by being nice to the kernel memory manager.
---
src/gallium/auxiliary/util/u_helpers.c | 120 +
src/gallium/auxiliary/util/u_helpers.h | 17
From: Marek Olšák
---
src/gallium/docs/source/screen.rst | 3 +++
src/gallium/drivers/etnaviv/etnaviv_screen.c | 1 +
src/gallium/drivers/freedreno/freedreno_screen.c | 1 +
src/gallium/drivers/i915/i915_screen.c | 1 +
src/gallium/drivers/llvmpipe/lp_screen.c
https://bugs.freedesktop.org/show_bug.cgi?id=10
--- Comment #4 from ilia ---
Created attachment 141403
--> https://bugs.freedesktop.org/attachment.cgi?id=141403=edit
Windowed
Tried to click on menu items - I even heard it, but no
> err:d3dadapter:PRESENTPixmap FATAL ERROR: Trying to
On Fri, Aug 31, 2018 at 05:15:53PM -0500, Jason Ekstrand wrote:
> We make the flush after a HiZ clear unconditional and add a flush/stall
> before the clear as well.
>
> Cc: mesa-sta...@lists.freedesktop.org
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107760
> ---
>
Cc: Dylan Baker
Cc: Juan A. Suarez
Cc: Emil Velikov
Signed-off-by: Andres Gomez
---
docs/release-calendar.html | 25 +
1 file changed, 25 insertions(+)
This is just a proposal for the beginning of the 18.3 releasing
process.
18.2 has gotten exceptionally long to be
https://bugs.freedesktop.org/show_bug.cgi?id=10
--- Comment #2 from ilia ---
Created attachment 141401
--> https://bugs.freedesktop.org/attachment.cgi?id=141401=edit
NINE OFF log
Output of
env NINE_DEBUG=all GALLIUM_HUD="fps,requested-VRAM" LIBGL_DEBUG=verbose
GALLIUM_PRINT_OPTIONS=1
https://bugs.freedesktop.org/show_bug.cgi?id=10
--- Comment #3 from ilia ---
Created attachment 141402
--> https://bugs.freedesktop.org/attachment.cgi?id=141402=edit
NINE ON log
env NINE_DEBUG=all GALLIUM_HUD="fps,requested-VRAM" LIBGL_DEBUG=verbose
GALLIUM_PRINT_OPTIONS=1
On Fri, Aug 31, 2018 at 5:38 PM Nanley Chery wrote:
> On Fri, Aug 31, 2018 at 05:15:53PM -0500, Jason Ekstrand wrote:
> > We make the flush after a HiZ clear unconditional and add a flush/stall
> > before the clear as well.
> >
> > Cc: mesa-sta...@lists.freedesktop.org
> > Bugzilla:
https://bugs.freedesktop.org/show_bug.cgi?id=107670
--- Comment #9 from i...@yahoo.com ---
(In reply to Timothy Arceri from comment #8)
> Using SSE2 memcpy seems to avoid this problem"
>
> Glib should select the SSE2 (or better) version of memcpy. If Slackware
> doesn't ship and SSE2 support for
We were going out of our way to disable dual-location re-mapping in NIR
only to then do the remapping in st_glsl_to_nir.cpp. Presumably, this
was so that double_inputs would be correct for the core state tracker.
However, now that we've it to gl_program::DualSlotInputs which is
unaffected by NIR
It was very inconsistently handled; the only things that made use of it
were glsl_to_nir, glspirv, and nir_gather_info. In particular,
nir_lower_io completely ignored it so anyone using nir_lower_io on
64-bit vertex attributes was going to be in for a shock. Also, as of
the previous commit, it's
NIR handling of 64-bit vertex attributes is inconsistent at best. When it
comes vertex attributes which are 196 or 256 bits (dvec3 or dvec4), some
passes assume they consume two slots, some passes assume they consume one,
and some passes are configurable. When you combine that with the limited
Previously, we had two field in shader_info: double_inputs_read and
double_inputs. Presumably, the one was for all double inputs that are
read and the other is all that exist. However, because nir_gather_info
regenerates these two values, there is a possibility, if a variable gets
deleted, that
On Fri 31 Aug 2018, Jason Ekstrand wrote:
> On Fri, Aug 31, 2018 at 4:35 PM Nanley Chery <[1]nanleych...@gmail.com> wrote:
>
> If that doesn't fix it, I think it'd be good to comment that we've
> observed this pipecontrol be necessary for 3DSTATE_WM_HZ_OP.
>
>
> I'm happy to add some
We make the flush after a HiZ clear unconditional and add a flush/stall
before the clear as well.
Cc: mesa-sta...@lists.freedesktop.org
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107760
---
src/intel/vulkan/anv_blorp.c | 44 +++-
1 file changed, 33
On 31/08/18 21:07, Emil Velikov wrote:
On 31 August 2018 at 11:37, Timothy Arceri wrote:
On 31/08/18 20:10, Emil Velikov wrote:
Hi Timothy,
On 31 August 2018 at 10:57, Timothy Arceri wrote:
On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
+TImothy
On Fri, Aug 31, 2018 at 11:32 AM
Am Dienstag, den 13.03.2018, 14:24 +1000 schrieb Dave Airlie:
> This is the main code for the soft fp64 work. It's mostly Elie's
> code with a bunch of changes by me.
>
With all the changes that landed lately for r600 I wanted to check how
things are doing, but unfortunately the series doesn't
> I'm looking into forward porting laanwj's patches for GC7000 support to
> current mesa master. Luckily most of it already got merged last November
> with mostly only the texture descriptor support missing(
> https://github.com/laanwj/mesa/commit/b71802207432543745dff471c68fbc40495b4858)
>
>
On 31 August 2018 at 14:36, Timothy Arceri wrote:
> On 31/08/18 21:07, Emil Velikov wrote:
>>
>> On 31 August 2018 at 11:37, Timothy Arceri wrote:
>>>
>>> On 31/08/18 20:10, Emil Velikov wrote:
Hi Timothy,
On 31 August 2018 at 10:57, Timothy Arceri
wrote:
>
From: Andrii Simiklit
It fixes a bit incorrectly implemented ARB_program_interface_query.
If input aoa element is unused in shader program
the 'glGetProgramResourceIndex' function shouldn't
return a valid resource index for it according to:
ARB_program_interface_query spec:
" For an active
On Fri, Aug 31, 2018 at 1:57 AM Dave Airlie wrote:
>
> From: Dave Airlie
>
> ac_surface.c: gfx6_compute_surface says
> /* DB doesn't support linear layouts. */
I think r100 was the last chip to support linear depth surfaces.
Alex
>
> Now if we expose linear depth and create a linear depth
https://bugs.freedesktop.org/show_bug.cgi?id=97003
Timothy Arceri changed:
What|Removed |Added
QA Contact|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
On 08/30/2018 07:42 PM, Marek Olšák wrote:
> Sadly, there are no tests for this.
Ok... I just sent one to the piglit list. It should be easy enough to
create a few more for other glDeleteFoo functions. I'll save that for
during boring meetings. ;)
> Marek
>
> On Thu, Aug 30, 2018 at 6:24 PM,
On Thu, 2018-08-30 at 18:03 +0300, Andres Gomez wrote:
> Due to having 2 additional RCs for 18.2.
>
> Cc: Dylan Baker
> Cc: Juan A. Suarez
> Cc: Emil Velikov
> Signed-off-by: Andres Gomez
Acked-by: Juan A. Suarez
> ---
> docs/release-calendar.html | 10 --
> 1 file changed, 8
From: "J Karanje, Kedar"
The feature is enabled by default during make however we need to
add the following to drirc to enable the feature at runtime.
vbo: Main algorithm & code to check for MVP & vertex position location
Build Files: Flags to enable BBOX Code and check AVX version
compiler:
Quoting Andres Gomez (2018-08-30 08:03:04)
> Due to having 2 additional RCs for 18.2.
>
> Cc: Dylan Baker
> Cc: Juan A. Suarez
> Cc: Emil Velikov
> Signed-off-by: Andres Gomez
> ---
> docs/release-calendar.html | 10 --
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff
Reviewed-by: Bas Nieuwenhuizen
On Fri, Aug 31, 2018 at 7:56 AM Dave Airlie wrote:
>
> From: Dave Airlie
>
> ac_surface.c: gfx6_compute_surface says
> /* DB doesn't support linear layouts. */
>
> Now if we expose linear depth and create a linear depth image
> and use CmdCopyImage to copy into
On 31 August 2018 at 11:37, Timothy Arceri wrote:
> On 31/08/18 20:10, Emil Velikov wrote:
>>
>> Hi Timothy,
>>
>> On 31 August 2018 at 10:57, Timothy Arceri wrote:
>>>
>>> On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
+TImothy
On Fri, Aug 31, 2018 at 11:32 AM Alexander
We would need a fairly recent kernel (drm-tip?) to test this in CI.
I can't see any issue with this because we always have the meta path as
a fallback for tiled buffers.
Reviewed-by: Lionel Landwerlin
On 30/08/2018 16:22, Chris Wilson wrote:
On more recent HW, the indirect writes via the
Quoting Lionel Landwerlin (2018-08-31 12:16:19)
> We would need a fairly recent kernel (drm-tip?) to test this in CI.
Unpatched mesa, assumes all is fine.
Post-patch mesa, assumes all is broken.
So we can quickly see if anything actually fails if a persistent GGTT
mmap is rejected. Which is the
On 31/08/2018 12:22, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-08-31 12:16:19)
We would need a fairly recent kernel (drm-tip?) to test this in CI.
Unpatched mesa, assumes all is fine.
Post-patch mesa, assumes all is broken.
So we can quickly see if anything actually fails if a
Quoting Lionel Landwerlin (2018-08-31 12:32:23)
> On 31/08/2018 12:22, Chris Wilson wrote:
> > Quoting Lionel Landwerlin (2018-08-31 12:16:19)
> >> We would need a fairly recent kernel (drm-tip?) to test this in CI.
> > Unpatched mesa, assumes all is fine.
> > Post-patch mesa, assumes all is
On 31/08/2018 12:43, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-08-31 12:32:23)
On 31/08/2018 12:22, Chris Wilson wrote:
Quoting Lionel Landwerlin (2018-08-31 12:16:19)
We would need a fairly recent kernel (drm-tip?) to test this in CI.
Unpatched mesa, assumes all is fine.
Yes, please.
Acked-by: Emil Velikov
-Emil
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Hi, I'm the developer behind flatpak (https://flatpak.org/) and we've
recently run into some issues with the mesa shader cache. Flatpak has
a app/runtime split where the runtime is shared between app and
provides /usr. The runtime contains a version of mesa, but this can be
overridden by runtime
Tested-by: Juan A. Suarez
J.A.
On Sat, 2018-06-30 at 15:10 +, Vinson Lee wrote:
> Fix build error after llvm-7.0svn r336028 ("[instsimplify] Move the
> instsimplify pass to use more obvious file names and diretory.").
>
> rasterizer/jitter/blend_jit.cpp:873:20: error: use of
+TImothy
On Fri, Aug 31, 2018 at 11:32 AM Alexander Larsson wrote:
>
> Hi, I'm the developer behind flatpak (https://flatpak.org/) and we've
> recently run into some issues with the mesa shader cache. Flatpak has
> a app/runtime split where the runtime is shared between app and
> provides /usr.
https://bugs.freedesktop.org/show_bug.cgi?id=107767
Bug ID: 107767
Summary: Segfault with standalone compiler and --dump-builder
Product: Mesa
Version: git
Hardware: All
OS: All
Status: NEW
Severity:
https://bugs.freedesktop.org/show_bug.cgi?id=107767
--- Comment #1 from Sergii Romantsov ---
Patch series: https://patchwork.freedesktop.org/series/48998/
--
You are receiving this mail because:
You are the assignee for the bug.___
mesa-dev mailing
On 30/08/2018 22:41, Rodrigo Vivi wrote:
Amber Lake uses the same gen graphics as Kaby Lake, including a id
that were previously marked as reserved on Kaby Lake, but that
now is moved to AML page.
This follows the ids and approach used on kernel's commit
e364672477a1 ("drm/i915/aml: Introducing
On 30/08/2018 22:41, Rodrigo Vivi wrote:
Many new platforms got added to gen_device_name_to_pci_device_id()
but the error message inside aubinator didn't reflected those
changes. So syncing on the same order to be sure that we are not
missing any now.
Cc: Anuj Phogat
Cc: Matt Turner
Cc:
On 31/08/18 20:10, Emil Velikov wrote:
Hi Timothy,
On 31 August 2018 at 10:57, Timothy Arceri wrote:
On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
+TImothy
On Fri, Aug 31, 2018 at 11:32 AM Alexander Larsson
wrote:
Hi, I'm the developer behind flatpak (https://flatpak.org/) and we've
Signed-off-by: Lionel Landwerlin
---
src/intel/genxml/gen10.xml | 33 +
src/intel/genxml/gen11.xml | 33 +
2 files changed, 66 insertions(+)
diff --git a/src/intel/genxml/gen10.xml b/src/intel/genxml/gen10.xml
index
As right now piglit only have one ARB_gl_spirv test with double inputs,
and Im not really sure if intel CI already runs piglit with spirv-tools
available, I tested this patch with my local piglit, that includes all
the va64 tests converted to SPIR-V (that as some already know/complained
about,
https://bugs.freedesktop.org/show_bug.cgi?id=105333
Timothy Arceri changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
For standalone compilation with parameter --dump-builder in dump
absent description of texture invocation.
Added the simplest handling.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107767
Signed-off-by: Sergii Romantsov
---
src/compiler/glsl/ir_builder_print_visitor.cpp | 51
On 30/08/2018 22:41, Rodrigo Vivi wrote:
Whiskey Lake uses the same gen graphics as Coffe Lake, including some
ids that were previously marked as reserved on Coffe Lake, but that
now are moved to WHL page.
This follows the ids and approach used on kernel's commit
b9be78531d27 ("drm/i915/whl:
On Wed, 29 Aug 2018 at 16:43, Eric Engestrom wrote:
> On Tuesday, 2018-08-28 21:44:54 -0500, Jason Ekstrand wrote:
> > On Tue, Aug 28, 2018 at 5:22 PM Jason Ekstrand wrote:
> > > This effectively reverts a26693493570a9d0f0fba1be617e01ee7bfff4db which
> > > was a misguided attempt at protecting
On Thu, 30 Aug 2018 at 12:59, Juan A. Suarez Romero wrote:
> If color buffer is locked, do not set its wayland buffer to NULL;
> otherwise it can not be freed later.
>
> Rather, flag it in order to destroy it later on the release event.
>
> v2: instruct release event to unlock only or free
Shader that contains builtin functions texture* causes segfault for
standalone compiler with parameter --dump-builder.
Added handling of ir_texture as rhs of assignment.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107767
Signed-off-by: Sergii Romantsov
---
On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
+TImothy
On Fri, Aug 31, 2018 at 11:32 AM Alexander Larsson wrote:
Hi, I'm the developer behind flatpak (https://flatpak.org/) and we've
recently run into some issues with the mesa shader cache. Flatpak has
a app/runtime split where the runtime is
Hi Timothy,
On 31 August 2018 at 10:57, Timothy Arceri wrote:
> On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
>>
>> +TImothy
>>
>> On Fri, Aug 31, 2018 at 11:32 AM Alexander Larsson
>> wrote:
>>>
>>>
>>> Hi, I'm the developer behind flatpak (https://flatpak.org/) and we've
>>> recently run into
Hi,
I'm looking into forward porting laanwj's patches for GC7000 support to
current mesa master. Luckily most of it already got merged last November
with mostly only the texture descriptor support missing(
https://github.com/laanwj/mesa/commit/b71802207432543745dff471c68fbc40495b4858)
Putting
On Fri, Aug 31, 2018 at 11:57 AM Timothy Arceri wrote:
>
> On 31/08/18 19:40, Bas Nieuwenhuizen wrote:
> We depend on build timestamps of the mesa/llvm binaries when generating
> the sha for cache items. So if flatpak results in two versions of mesa
> having the same timestamp then there is
On 2018-08-31 2:14 a.m., Dave Airlie wrote:
> On Fri., 31 Aug. 2018, 01:22 Michel Dänzer, wrote:
>>
>> On 2018-08-27 11:16 p.m., Dave Airlie wrote:
>>> From: Dave Airlie
>>>
>>> This hijacks the top 16-bits of swizzle, to pass in the swizzle
>>> for the second channel.
>>>
>>> This fixes
https://bugs.freedesktop.org/show_bug.cgi?id=107772
--- Comment #2 from Ian Romanick ---
(In reply to Ian Romanick from comment #1)
> I'll add a piglit test for this. I cut-and-paste that code into a shader
> (and did 's/[[]ERROR]: [0-9]*: //'), and I get:
And 's/ \\$//'
> Failed to compile
https://bugs.freedesktop.org/show_bug.cgi?id=107772
Ian Romanick changed:
What|Removed |Added
CC||i...@freedesktop.org,
https://bugs.freedesktop.org/show_bug.cgi?id=107772
Mark Janes changed:
What|Removed |Added
Assignee|mesa-dev@lists.freedesktop. |t_arc...@yahoo.com.au
https://bugs.freedesktop.org/show_bug.cgi?id=107477
--- Comment #19 from Samuel Pitoiset ---
Fixed with
https://cgit.freedesktop.org/mesa/mesa/commit/?id=6f47df312943b05653efc0494551ebf8c3903d43
Feel free to open a new bug report if you think the reflection issue is on the
driver side.
Thanks
https://bugs.freedesktop.org/show_bug.cgi?id=107477
Samuel Pitoiset changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
On Thu, Aug 30, 2018 at 6:41 AM Erik Faye-Lund
wrote:
>
> This moves the evergreen-specific max-sizes out as a driver-cap, so
> other drivers with less strict requirements also can use hw-atomics.
>
> Remove ssbo_atomic as it's no longer needed.
>
> We should now be able to use hw-atomics for
From: Emil Velikov
Unlike the other platforms, here we aim do guess if the device that we
somewhat arbitrarily picked, is supported or not.
In particular: when a vendor is _not_ requested we loop through all
devices, picking the first one which can create a DRI screen.
When a vendor is
This needs to be split into more than one patch before anyone is going
to look at it. Each commit should do one, self-contained thing.
"Implement a giant feature" in +2535 lines of code is not one,
self-contained thing.
Doing "simple shader" detection at the GLSL AST level (not even HIR yet,
in
https://bugs.freedesktop.org/show_bug.cgi?id=107772
Bug ID: 107772
Summary: Mesa preprocessor matches if(def)s & endifs
incorrectly
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Hi,
On 31.08.2018 08:25, kedar.j.kara...@intel.com wrote:
From: "J Karanje, Kedar"
The feature is enabled by default during make however we need to
add the following to drirc to enable the feature at runtime.
vbo: Main algorithm & code to check for MVP & vertex position location
Build
Though the SARGB format is used internally through its FourCC value,
it is not a real format as defined by drm_fourcc.h; it cannot be used
with KMS or other interfaces expecting drm_fourcc.h format codes.
Ensure we don't advertise it through the dmabuf format/modifier query
interfaces,
On Thu, Aug 30, 2018 at 6:41 AM Erik Faye-Lund
wrote:
>
> From: Tomeu Vizoso
>
> Emulating atomics on top of ssbos can lead to too small max SSBO count,
> so let's use the hw-atomics mechanism to expose atomic buffers instead.
>
> Signed-off-by: Erik Faye-Lund
> ---
>
81 matches
Mail list logo