Michel Dänzer writes:
> From: Michel Dänzer
>
> Always use 3 buffers when flipping. With only 2 buffers, we have to wait
> for a flip to complete (which takes non-0 time even with asynchronous
> flips) before we can start working on the next frame. We were previously
> only using 2 buffers for f
Kristian Høgsberg writes:
> I sent a reply to the sourceforge addresses in the original emails,
> but I didn't see it show up in the archives. Trying again with the
> freedesktop addresses.
(sorry for having an ancient shell script with sourceforge addresses in
it)
>> +typedef uint32_t *
>> +(
Jordan Justen writes:
> After patch 6, this will add SARGB8, right? So, maybe add this to the
> commit message, or separate out adding SARGB8 into a separate commit?
I added the SARGB8 define in patch 4; is there some other separation you
think would be warranted?
Oh, just so everyone knows --
Keith Packard writes:
> This sequence first adds a a couple of new DRIimage extensions to the
> dri/common, dri/i915 and dri/i965 directories which define a
> loader-independent API for managing window system operations.
>
> The last patch adds a new DRI3000 loader using those
Eric Anholt writes:
> It seems like we could just stick these things in __DRI_CORE as opposed
> to having another new extension to look up.
Having the driver expose this new extension is how I tell that the
driver is going to actually call the __DRIimage-based loader; the
alternative to a new ex
This exposes the kernel API for performing asynchronous flips
Signed-off-by: Keith Packard
---
include/drm/drm.h | 1 +
include/drm/drm_mode.h | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/drm/drm.h b/include/drm/drm.h
index 725bf51..f0b4c16 100644
--- a
Eric Anholt writes:
> Keith Packard writes:
>
>> This exposes the kernel API for performing asynchronous flips
>>
>> Signed-off-by: Keith Packard
>
> Reviewed-by: Eric Anholt
I've pushed this to master.
--
keith.pack...@intel.com
pgprKBc6E
libudev doesn't have a stable API/ABI, and if the application wants to use one
version, we'd best not load another into libGL.
Signed-off-by: Keith Packard
---
configure.ac | 5 +--
src/glx/dri3_common.c | 106 +++---
2 files c
libudev doesn't have a stable API/ABI, and if the application wants to use one
version, we'd best not load another into libGL.
Signed-off-by: Keith Packard
---
Sorry for the patch spam; I hadn't rebased in a while and there was a
configure.ac conflict. Here's a versio
Emil Velikov writes:
> On 18/11/13 01:08, Keith Packard wrote:
>> libudev doesn't have a stable API/ABI, and if the application wants to use
>> one
>> version, we'd best not load another into libGL.
>>
>> Signed-off-by: Keith Packard
>>
Kenneth Graunke writes:
> For non-API facing stuff, you can just use stdbool.h's
> bool/true/false.
tnx. I pushed that to my dri3 branch. Btw, that branch also has some
gallium support for __DRIimageDriverExtension. I don't have any hardware
to test with, so it's surely broken in some major ways
Emil Velikov writes:
> On 18/11/13 01:08, Keith Packard wrote:
>> libudev doesn't have a stable API/ABI, and if the application wants to use
>> one
>> version, we'd best not load another into libGL.
>>
>> Signed-off-by: Keith Packard
>> ---
&
Eric Anholt writes:
> Keith Packard writes:
>
>> libudev doesn't have a stable API/ABI, and if the application wants to use
>> one
>> version, we'd best not load another into libGL.
>>
>> Signed-off-by: Keith Packard
>
> This looks so simp
__IMAGE_FORMAT_SARGB8 in both the i915 and i965 drivers.
I'll refrain from comments on whether I think having two separate sets of
format defines in dri_interface.h is a good idea or not...
Signed-off-by: Keith Packard
---
This gets iceweasel running with the GL compositor enabled.
inclu
ked will get updated by the XCB special event queue used by
DRI3.
Signed-off-by: Keith Packard
---
This patch makes sure that drawables get invalidated when the window
changes size or when SwapBuffers is called; dri3 has only a single
location to smite when things change, so we need to make sure t
ing 'void *' in mesa, which
works with both the int32_t* and struct xshmfence* versions.
Signed-off-by: Keith Packard
---
libxshmfence will also be providing a HAVE_STRUCT_XSHMFENCE define, so
we could actually check for that and use struct xshmfence when
available. Just using 'voi
Always nice to clean up after ourselves.
Signed-off-by: Keith Packard
---
Ok, so not having this in the dri3 code led to a bit of extra memory
usage in apps and the X server.
src/glx/dri3_glx.c | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/src/glx
Always nice to clean up after ourselves.
Signed-off-by: Keith Packard
---
v2: Include changes to dri3_priv.h as well
src/glx/dri3_glx.c | 17 -
src/glx/dri3_priv.h | 5 -
2 files changed, 20 insertions(+), 2 deletions(-)
diff --git a/src/glx/dri3_glx.c b/src/glx
This allows GL to support the GLX_INTEL_swap_event extension
Signed-off-by: Keith Packard
---
This is the X server side; the mesa patch will be sent shortly (it's tiny)
glx/Makefile.am | 3 ++-
glx/glxcmds.c | 69 +
sequence number that we send in the
PresentPixmap requests, and that's done by using the same variable for both
roles.
Signed-off-by: Keith Packard
---
This passes the piglet glx-swap-event test.
src/glx/dri3_glx.c | 27 ++-
src/glx/dri3_priv.h | 3 +--
2 files c
Daniel Vetter writes:
> Hm, where do we have the canonical source for all these fourcc codes? I'm
> asking since we have our own copy in the kernel as drm_fourcc.h, and that
> one is part of the userspace ABI since we use it to pass around
> framebuffer formats and format lists.
I think it's the
igned-off-by: Keith Packard
---
This one took a while to find -- multiple bo_gem structs pointing at
the same gem handle would either cause the object to be destroyed
before we were done using it, or we'd end up sending the same
gem_handle for multiple buffers.
This looks a lot like the na
While debugging the libdrm duplicate buffer object adventure, I managed to
temporarily understand object lifetimes in the __DRIimage getBuffers path, and
also to compare that to the DRI2 getBuffers path. Here are a couple of small
fixes.
I haven't looked at the i915 code, but I suspect the first o
.
Signed-off-by: Keith Packard
---
src/mesa/drivers/dri/i965/brw_context.c | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_context.c
b/src/mesa/drivers/dri/i965/brw_context.c
index bee98e3..64ff855 100644
--- a/src/mesa/drivers
Just copying code from the dri2 path to set up the fast color clear state.
This also removes a couple of bogus intel_region_reference calls.
Signed-off-by: Keith Packard
---
src/mesa/drivers/dri/i965/intel_mipmap_tree.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff
Kristian Høgsberg writes:
> I already explained to Keith why we use different sets of format codes
> in the DRI interface, but it's always fun to slam other peoples code.
As we discussed, my complaint isn't so much about __DRI_IMAGE_FOURCC,
but the fact that the __DRIimage interfaces use *both*
Ville Syrjälä writes:
> What is this format anyway? -ENODOCS
Same as MESA_FORMAT_SARGB8 and __DRI_IMAGE_FORMAT_SARGB8 :-)
> If its just an srgb version of ARGB, then I wouldn't really want it
> in drm_fourcc.h. I expect colorspacy stuff will be handled by various
> crtc/plane properties in
is is because flips are always done from within the
ring, and so the latency between the vblank event and the async flip happening
can cause tearing at the top of the screen.
That's why I'm keying the need for the extra buffer on the lack of 2D
driver support for async flips.
Signed-off-
Daniel Vetter writes:
> Yeah, it unfortunately took a few rounds of kernel fixes and other
> haggling to get the semantics right on this one. The kernel atm promises
> to userspace (minus one big in a racy corner case no one should care
> about, still need to fix that one) that it'll return the s
Also checks for prime buffers in the flink case.
Signed-off-by: Keith Packard
---
intel/intel_bufmgr_gem.c | 50 +---
1 file changed, 43 insertions(+), 7 deletions(-)
diff --git a/intel/intel_bufmgr_gem.c b/intel/intel_bufmgr_gem.c
index df6fcec..2b7fe07 1
Eric Anholt writes:
> I'd prefer to see sbc stay with its current name, since that's its name
> in the specs we're trying to implement (GLX_OML_sync_control,
> GLX_INTEL_swap_event). If you drop the rename from the patch,
>
> Reviewed-by: Eric Anholt
Sounds good.
> I read that as "SBC is incr
Eric Anholt writes:
> There's a minor behavior change that the event now gets sent to the
> drawable owner rather than the caller of DRI2SwapBuffers.
Yeah, probably not ideal, especially when the GLX drawable is created
using the window XID (as is the case for some older GLX clients). I
don't ha
Move the depth field up with width and height.
Remove unused previous_time and frames fields.
Signed-off-by: Keith Packard
---
src/glx/dri3_priv.h | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/src/glx/dri3_priv.h b/src/glx/dri3_priv.h
index 05f66cf..34c67a6 100644
Tracking the full 64-bit SBC values makes it clearer how those values are
being used, and simplifies the wait_msc code. The only trick is in
re-constructing the full 64-bit value from Present's 32-bit serial number that
we use to pass the SBC value from request to event.
Signed-off-by:
seen the specified SBC value come back in a
PresentCompleteNotify event yet.
The change is a bit larger than that as I've broken out a piece of common code
to wait for and process a single Present event for the target drawable.
Signed-off-by: Keith Packard
---
src/glx/dri3_
Now that we're tracking SBC values correctly, and the X server has the ability
to send the GLX swap events from a PresentPixmap request, enable this extension.
Signed-off-by: Keith Packard
---
src/glx/dri3_glx.c | 18 +-
1 file changed, 1 insertion(+), 17 deletions(-)
I've split the GLX_INTEL_swap_event enabling patch into four bits -- the first
three just fix the existing code to track SBC values correctly and to fix
wait_for_sbc. The fourth is the trivial patch to actually turn on the new
extension; all of the hard work for that is actually dealt with in the X
Daniel Vetter writes:
> The kernel actually doesn't bother with this, i.e. an open on an flink
> name will always create a new handle. Given that it was a major pita to
> get the prime reimporting going (due to a pile of funny lifetime issues
> around reference loops and some assorted locking fun
Jordan Justen writes:
>> We find the driver foo's name by using the dladdr function
>> which gives the path of the dynamic library's name that
>> was being loaded.
That sounds like all kinds of win for existing X servers. Thanks for
doing it up in style, so that a megadrivers build can actually
porate fixes and suggestions from Keith
Reviewed-by: Keith Packard
--
keith.pack...@intel.com
pgp1rPNEULXgK.pgp
Description: PGP signature
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
These are duplicates from gl.h; I'm not sure which file they belong in, but
you don't get to have them in both places.
Signed-off-by: Keith Packard
---
include/GL/glext.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/GL/glext.h b/include/GL/glext.h
index fea9e1f..4c0a
I stole the conditional for _X_ATTRIBUTE_PRINTF from xproto and
changed the name to _DRM_ATTRIBUTE_PRINTF to avoid future conflicts.
Signed-off-by: Keith Packard
---
xf86drm.h | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/xf86drm.h b/xf86drm.h
index 1e763a3
Alan Coopersmith writes:
> You should drop that line - those comments are used for us to figure out which
> xproto version to list in the pkg-config requirements when using newer _X_*
> macros out of Xfuncproto.h, so doesn't make sense here.
>
> Also be warned that using a macro name starting wi
Kenneth Graunke writes:
> I see that Eric reviewed it, and that it has not landed. Are there any
> objections to merging it?
They're on top of a series of DRI3/Present patches, not all of which
have seen review. I was hoping the rest of that series would get
reviewed so that I could merge it al
These are the same address, but different types and driContextSetFlags wants
a gl_context pointer.
Signed-off-by: Keith Packard
---
src/mesa/drivers/dri/swrast/swrast.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/mesa/drivers/dri/swrast/swrast.c
b/src/mesa/drivers
These are duplicates from gl.h; I'm not sure which file they belong in, but
you don't get to have them in both places.
Signed-off-by: Keith Packard
---
include/GL/glext.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/GL/glext.h b/include/GL/glext.h
index 7d6033e..b432
It is the maximum number of back buffers, but the name is confusing and is
easily read as the maximum back buffer index. Chage to DRI3_NUM_BACK to make
the intended usage a bit clearer.
Signed-off-by: Keith Packard
---
src/glx/dri3_glx.c | 4 ++--
src/glx/dri3_priv.h | 10 +-
2 files
This series has a bunch of DRI3 cleanups and fixes followed by a few patches
that finish up DRI3 support in gallium.
The first two patches have nothing to do with DRI3, just some warning fixes:
[PATCH 01/18] Remove glBlendColor and glBlendEquations decls from
[PATCH 02/18] dri/swrast: Passing d
Tracking the full 64-bit SBC values makes it clearer how those values are
being used, and simplifies the wait_msc code. The only trick is in
re-constructing the full 64-bit value from Present's 32-bit serial number that
we use to pass the SBC value from request to event.
Signed-off-by:
libudev doesn't have a stable API/ABI, and if the application wants to use one
version, we'd best not load another into libGL.
Signed-off-by: Keith Packard
---
configure.ac | 8 -
src/glx/dri3_common.c | 85 ++-
2 files c
Now that we're tracking SBC values correctly, and the X server has the ability
to send the GLX swap events from a PresentPixmap request, enable this extension.
Signed-off-by: Keith Packard
---
src/glx/dri3_glx.c | 18 +-
1 file changed, 1 insertion(+), 17 deletions(-)
XCB doesn't flush the output buffer automatically, so we have to call
xcb_flush ourselves before waiting.
Signed-off-by: Keith Packard
---
src/glx/dri3_glx.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/glx/dri3_glx.c b/src/glx/dri3_glx.c
index c26d6e5..7982f6b 100644
--- a/sr
Move the depth field up with width and height.
Remove unused previous_time and frames fields.
Signed-off-by: Keith Packard
Reviewed-by: Kenneth Graunke
---
src/glx/dri3_priv.h | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/src/glx/dri3_priv.h b/src/glx/dri3_priv.h
Just copying code from the dri2 path to set up the fast color clear state.
This also removes a couple of bogus intel_region_reference calls.
Signed-off-by: Keith Packard
Reviewed-by: Eric Anholt
---
src/mesa/drivers/dri/i965/intel_mipmap_tree.c | 10 +++---
1 file changed, 7 insertions
seen the specified SBC value come back in a
PresentCompleteNotify event yet.
The change is a bit larger than that as I've broken out a piece of common code
to wait for and process a single Present event for the target drawable.
Signed-off-by: Keith Packard
---
src/glx/dri3_
__IMAGE_FORMAT_SARGB8 in both the i915 and i965 drivers.
I'll refrain from comments on whether I think having two separate sets of
format defines in dri_interface.h is a good idea or not...
Signed-off-by: Keith Packard
Reviewed-by: Eric Anholt
---
include/GL/internal/dri_interface.h | 1 +
From: Ben Skeggs
Signed-off-by: Ben Skeggs
Signed-off-by: Keith Packard
---
src/gallium/drivers/nouveau/nvc0/nvc0_resource.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/gallium/drivers/nouveau/nvc0/nvc0_resource.c
b/src/gallium/drivers/nouveau/nvc0
From: Ben Skeggs
Signed-off-by: Ben Skeggs
Signed-off-by: Keith Packard
---
src/gallium/state_trackers/dri/drm/dri2.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/src/gallium/state_trackers/dri/drm/dri2.c
b/src/gallium/state_trackers/dri/drm
ked will get updated by the XCB special event queue used by
DRI3.
Signed-off-by: Keith Packard
Reviewed-by: Marek Olšák
---
src/gallium/state_trackers/dri/common/dri_drawable.c | 4 ++--
src/gallium/state_trackers/dri/drm/dri2.c| 2 +-
2 files changed, 3 insertions(+), 3 deletions(
libxshmfence v1.0 foolishly used 'int32_t *' for the fence type, which
works when the fence is a linux futex. However, version 1.1
changes the exported datatype to 'struct xshmfence *'
Require libxshmfence version 1.1 and switch the API around.
Signed-off-by: Keith Packar
Always nice to clean up after ourselves.
Signed-off-by: Keith Packard
---
src/glx/dri3_glx.c | 17 -
src/glx/dri3_priv.h | 5 -
2 files changed, 20 insertions(+), 2 deletions(-)
diff --git a/src/glx/dri3_glx.c b/src/glx/dri3_glx.c
index 1834c6d..4c0dc29 100644
--- a/src
.
Signed-off-by: Keith Packard
Reviewed-by: Eric Anholt
---
src/mesa/drivers/dri/i965/brw_context.c | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_context.c
b/src/mesa/drivers/dri/i965/brw_context.c
index 688091f..78c06fc
Provide the hook to pull textures out of __DRIimage structures and use them as
renderbuffers.
Signed-off-by: Keith Packard
---
src/gallium/state_trackers/dri/drm/dri2.c | 238 +-
1 file changed, 230 insertions(+), 8 deletions(-)
diff --git a/src/gallium
Kenneth Graunke writes:
> NAK. These headers come directly from Khronos; we need to somehow get
> this fixed upstream and take their version.
Until they're fixed upstream, we should fix them when incorporating them
into the repository. Having broken headers in our code just because
they're brok
Kenneth Graunke writes:
> Would be great to line these comments up.
Fixed.
> Patches 2 and 4-6 are:
> Reviewed-by: Kenneth Graunke
Review marked. Thanks much!
--
keith.pack...@intel.com
pgpkJlR4qfmew.pgp
Description: PGP signature
___
mesa-dev m
Marek Olšák writes:
> Some of the code seems to be copy-pasted from
> dri2_drawable_process_buffers. The MSAA color and depth-stencil
> texture allocation could be moved to a common function.
It's either that or plan on moving DRI2 to the image interface as well
at some point? As we'll have to k
the drmServerInfo member, debug_print, takes a printf format string
and varargs list. Tell the compiler about it.
Signed-off-by: Keith Packard
---
xf86drm.h | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/xf86drm.h b/xf86drm.h
index 1e763a3..5e170f8 100644
--- a
Thierry Reding writes:
> While at it, perhaps the drmMsg() and drmDebugPrint() functions should
> be similarily annotated as well?
I don't know; I'm just fixing X server warnings this week and this was
the source of one of them. Additional warning fixes for drm would be
a great idea!
--
keith.
Ian Romanick writes:
> Reviewed-by: Ian Romanick
Thanks. Pushed.
8279c8f..cb4bc8e master -> master
--
keith.pack...@intel.com
pgpkKf6zSEV5v.pgp
Description: PGP signature
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.fr
Eric Anholt writes:
> By using a dlopen() with RTLD_LOCAL, we can explicitly look for the
> symbols we want, while they get the symbols they want.
This is way better than the patch I sent that open-coded some of this.
Reviewed-by: Keith Packard
--
keith.pack...@intel.com
pgp2pcQjAic
Eric Anholt writes:
> Noticed when valgrinding an unrelated bug.
Reviewed-by: Keith Packard
--
keith.pack...@intel.com
pgpbTv2iprHuM.pgp
Description: PGP signature
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
h
Eric Anholt writes:
> I want to stop trusting the server for the driver name, and instead decide
> on our own based on the fd, so I needed this code motion.
Reviewed-by: Keith Packard
--
keith.pack...@intel.com
pgp0Q34HtVkgL.pgp
Description: PGP sig
Eric Anholt writes:
> This allows Mesa to choose to rename driver .sos (or split drivers),
> without needing a flag day with the corresponding 2D driver.
Reviewed-by: Keith Packard
--
keith.pack...@intel.com
pgpcrXYj0vHR5.pgp
Description: PGP sig
ebased my dri3+gallium branch and needed this patch to avoid a segfault)
Reviewed-by: Keith Packard
Tested-by: Keith Packard
--
keith.pack...@intel.com
pgp7EiKVwTrj4.pgp
Description: PGP signature
___
mesa-dev mailing list
mesa-dev@list
Eric Anholt writes:
> ---
> src/loader/loader.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Keith Packard
--
keith.pack...@intel.com
pgp69RQVpsMzq.pgp
Description: PGP signature
___
mesa-dev mailing list
then I saw this one)
Reviewed-by: Keith Packard
--
keith.pack...@intel.com
pgpMV6LIMX4sK.pgp
Description: PGP signature
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Now that we have everything in place we can finally make it official
and announce it:
XDC2013 will take place from September 23th to September 25th in
Portland, Oregon at the University Place Hotel and Conference Center
Ian Romanick, Bart Massey, and I will be orgainzing this event.
The initial
# Call For Proposals
**2013 X.Org Developers Conference (XDC 2013)**
**23-25 September 2013**
**Portland, Oregon USA**
The [2013 X.Org Developers Conference]
(http://www.x.org/wiki/Events/XDC2013) is the annual
technical meeting for [X Window System](http://x.org) and
[Free Desktop](http://freede
Kenneth Graunke writes:
> The __DRI_USE_INVALIDATE extension was added in May 11th, 2010 by commit
> 4258e3a2e1c327. At this point, it's unlikely that anyone's using the
> right mix of new and old components to hit this path. Deleting it
> removes an untested code path and cleans up the driver
Lauri Kasanen writes:
> Forgot to mention, this would appear to make 3d impossible without udev
> (ie, static devices, mdev, or other solutions).
No, DRI2 continues to fall back to using the driver provided by the X
server if it can't find one locally.
--
keith.pack...@intel.com
pgppIx3XzY_4
pposed to *not* count
regular glXSwapBuffers calls. We have no way to tell at this level which
function the application called, so I suspect treating them all the same
is about the best we can do...
> This patch fixes the problem.
Yup, looks great to me.
Reviewed-by: Keith Packard
--
keith.
Mario Kleiner writes:
> This patch fixes the problem.
Yes, this looks like a good fix, but the names chosen seem very
misleading to me. Given that you're splitting the functionality, using
new names for the two functions will ensure that we carefully review all
current uses of the values and can
Mario Kleiner writes:
> Restores proper immediate tearing swap behaviour for
> OpenGL bufferswap under DRI3/Present.
Hrm. I'd love for this to be controlled by the GLX_EXT_swap_control_tear
extension, but that one uses negative interval values to indicate
tearing, instead of providing a new API,
Mario Kleiner writes:
> The 0 case is good for benchmarking.
Sure, but the current code does benchmarking just fine. In fact, because
it doesn't copy queued frames that aren't the most recent before the
vblank, benchmarks tend to run *faster* as a result, and people
generally like that aspect of
Mario Kleiner writes:
> Hmm. For benchmarking i think i'd consider that a mild form of cheating.
> You get higher fps because you skip processing like the whole gpu blit
> overhead and host processing overhead for queuing / validating /
> processing the copy command in the command stream, so t
Mario Kleiner writes:
> It's just that i need access to both, the old behaviour i described, and
> the new "drop frame" behaviour, and i need a way to select what i want
> at runtime via api without the need for easily overwhelmed and confused
> users to change config files or environment vari
18:10618:0930/200525:ERROR:webgraphicscontext3d_command_buffer_impl.cc(256)]
Failed to initialize command buffer.
This made it pretty easy to diagnose the problem in the referenced bug report.
Bugzilla: https://code.google.com/p/chromium/issues/detail?id=415681
Signed-off-by: Keith Packard
---
src
Matt Turner writes:
> Reviewed-by: Matt Turner
>
> Should we add a Cc: for the stable branch?
Also seems like a good plan. I've added that and pushed.
--
keith.pack...@intel.com
pgp3KeIMuqnda.pgp
Description: PGP signature
___
mesa-dev mailing lis
u'd get the presentation time, rather than the time of the swap?
Otherwise, this all seems fine to me
Reviewed-by: Keith Packard
--
keith.pack...@intel.com
pgpu01DhelnAs.pgp
Description: PGP signature
___
mesa-dev mailing list
mesa-dev@lists.free
Kenneth Graunke writes:
> Is UST expressed in a particular unit? I thought it was just "monotonically
> increasing" but otherwise meaningless. At which point, our FPS would be
> "frames per...something?" :)
UST in GL's extension is not defined, but Present uses microseconds. As
this is all h
Kenneth Graunke writes:
> v2: Use the UST value provided in the PRESENT_COMPLETE_NOTIFY event
> rather than gettimeofday(), which gives us the presentation time
> instead of the time when SwapBuffers was called. Suggested by
> Keith Packard. This relies on the fac
Kenneth Graunke writes:
> v2: Use the UST value provided in the PRESENT_COMPLETE_NOTIFY event
> rather than gettimeofday(), which gives us the presentation time
> instead of the time when SwapBuffers was called. Suggested by
> Keith Packard. This relies on the fact tha
Michel Dänzer writes:
> +#if HAVE_LLVM >= 0x0500
> + virtual void deregisterEHFrames() {
> + mgr()->deregisterEHFrames();
> + }
> +#elif HAVE_LLVM >= 0x0304
> + virtual void deregisterEHFrames(uint8_t *Addr, uint64_t LoadAddr,
> size_t Size) {
> + mgr()->deregister
This uses X leases to provide the same API as nVidia, allowing an
application to discover available display resources and acquire one from
the X server using RandR leases.
Signed-off-by: Keith Packard
---
configure.ac | 11 +
src/amd/vulkan/Makefile.am
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_device.c | 22 ++-
src/amd/vulkan
Implements VK_KHR_display and VK_EXT_direct_mode_display using
DRM/KMS.
Expose ability to get to that using VK_KEITHP_kms_display, which
allows the application to provide a master fd to the library which it
uses instead of opening its own.
Signed-off-by: Keith Packard
---
configure.ac
I've split this into three patches to make review at least a little
easier.
The first provides the KHR_display extension using the new
KEITHP_kms_display extension that allows you to pass in a DRM master
to vkCreateInstance.
The second provides EXT_acquire_xlib_display, which is an API that
nVidi
Emil Velikov writes:
> Is the VK_KEITHP_kms_display spec available somewhere?
I haven't written one yet. I'll go draft one.
> Since there are multiple companies [participating in Mesa] with
> Khronos membership, could we make this an EXT extension? Once
> everything else is settled in, of cours
**Status**
Draft.
**Last Modified Date**
2017-08-02
**Revision**
1
**IP Status**
No known IP claims.
**Dependencies**
This extension is written against version 1.0 of the Vulkan
API.
Requires VK_KHR_display
**Contributors**
Keith
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
1 - 100 of 294 matches
Mail list logo
