https://bugs.freedesktop.org/show_bug.cgi?id=111523
--- Comment #4 from Laurent carlier ---
See https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1794
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=111493
Ian Romanick changed:
What|Removed |Added
Status|ASSIGNED|NEEDINFO
--- Comment #5 from Ian Romanic
https://bugs.freedesktop.org/show_bug.cgi?id=111504
m.ort...@telefonica.net changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|--
Getting patches into libglvnd has proven quite difficult (see [0] for
example). There was some talk of moving it to FreeDesktop Gitlab on
IRC recently. Can we move forward with that? Are there objections to
doing so?
[0] https://github.com/NVIDIA/libglvnd/pull/86
__
https://bugs.freedesktop.org/show_bug.cgi?id=111523
--- Comment #3 from Aaron Watry ---
I might be able to get to this tonight if no one else has by then.
Gotta go do family things first.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the b
https://bugs.freedesktop.org/show_bug.cgi?id=111523
--- Comment #2 from Aaron Watry ---
Caused by clang commit (1fac68b0dc19b03fd2c5e9856f0f2c5a11691348):
https://reviews.llvm.org/D66797
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug
https://bugs.freedesktop.org/show_bug.cgi?id=111523
--- Comment #1 from Aaron Watry ---
In theory, the following should be enough to get things going again, but it'd
need to be wrapped in some logic to do clang version detection to keep the
older versions working:
diff --git a/src/gallium/state_
Hi Boris,
On Sat, 31 Aug 2019 at 18:33, Boris Brezillon
wrote:
> On Sat, 31 Aug 2019 17:06:30 +0100 Daniel Stone wrote:
> > On Fri, 30 Aug 2019 at 17:00, Rohan Garg wrote:
> > > Both the BO cache and the transient pool are shared across
> > > context's. Protect access to these with mutexes.
> >
On Sat, 31 Aug 2019 17:06:30 +0100
Daniel Stone wrote:
> Hi Rohan,
>
> On Fri, 30 Aug 2019 at 17:00, Rohan Garg wrote:
> > Both the BO cache and the transient pool are shared across
> > context's. Protect access to these with mutexes.
>
> These fixes seem right to me, and (minus the issues B
On Sat, 31 Aug 2019 19:21:04 +0200
Boris Brezillon wrote:
> On Sat, 31 Aug 2019 17:10:47 +0100
> Daniel Stone wrote:
>
> > Hi Boris,
> >
> > On Sat, 31 Aug 2019 at 11:47, Boris Brezillon
> > wrote:
> > > Right now, the transient memory allocator implements its own BO caching
> > > mechanism
On Sat, 31 Aug 2019 17:10:47 +0100
Daniel Stone wrote:
> Hi Boris,
>
> On Sat, 31 Aug 2019 at 11:47, Boris Brezillon
> wrote:
> > Right now, the transient memory allocator implements its own BO caching
> > mechanism, which is not really needed since we already have a generic
> > BO cache. Let's
On Sat, 31 Aug 2019 17:12:33 +0100
Daniel Stone wrote:
> Hi Boris,
>
> On Sat, 31 Aug 2019 at 08:53, Boris Brezillon
> wrote:
> > @@ -123,8 +123,7 @@ struct panfrost_batch *
> > panfrost_job_create_batch(struct panfrost_context *ctx);
> >
> > void
> > -panfrost_job_free_batch(struct panfrost_
Hi Boris,
On Sat, 31 Aug 2019 at 08:53, Boris Brezillon
wrote:
> @@ -123,8 +123,7 @@ struct panfrost_batch *
> panfrost_job_create_batch(struct panfrost_context *ctx);
>
> void
> -panfrost_job_free_batch(struct panfrost_context *ctx,
> -struct panfrost_batch *batch);
> +
Hi Boris,
On Sat, 31 Aug 2019 at 11:47, Boris Brezillon
wrote:
> Right now, the transient memory allocator implements its own BO caching
> mechanism, which is not really needed since we already have a generic
> BO cache. Let's simplify things a bit.
>
> [...]
>
> bool fits_in_current = (
Hi Rohan,
On Fri, 30 Aug 2019 at 17:00, Rohan Garg wrote:
> Both the BO cache and the transient pool are shared across
> context's. Protect access to these with mutexes.
These fixes seem right to me, and (minus the issues Boris pointed
out), both are:
Reviewed-by: Daniel Stone
I think it might
Right now, the transient memory allocator implements its own BO caching
mechanism, which is not really needed since we already have a generic
BO cache. Let's simplify things a bit.
Signed-off-by: Boris Brezillon
---
src/gallium/drivers/panfrost/pan_allocate.c | 80 -
src/gall
What we currently call a job is actually a batch containing several jobs
all attached to a rendering operation targeting a specific FBO.
Let's rename structs, functions, variables and fields to reflect this
fact.
Suggested-by: Alyssa Rosenzweig
Signed-off-by: Boris Brezillon
---
Changes in v2:
Given the function name it makes more sense to pass it a job batch
directly.
Signed-off-by: Boris Brezillon
---
Changes in v2:
* s/panfrost_job_get_batch_for_fbo/panfrost_get_batch_for_fbo/
* s/panfrost_job_batch/panfrost_batch/g
---
src/gallium/drivers/panfrost/pan_drm.c| 13 ++---
The context can be retrieved from batch->ctx.
Signed-off-by: Boris Brezillon
---
Changes in v2:
* s/panfrost_job_get_batch_for_fbo/panfrost_get_batch_for_fbo/
* s/panfrost_job_batch/panfrost_batch/g
---
src/gallium/drivers/panfrost/pan_context.c | 6 +++---
src/gallium/drivers/panfrost/pan_drm.
https://bugs.freedesktop.org/show_bug.cgi?id=111269
Alexandr Kára changed:
What|Removed |Added
CC||alexandr.k...@gmail.com
--- Comment #2
20 matches
Mail list logo
