On Fri, 21 Sep 2018 at 19:48, Jason Ekstrand wrote:
> You should try building with clang. 😜
>
If only there was some way we could do both, in some kind of automated
fashion!
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedes
Hi Emil,
On Thu, 20 Sep 2018 at 15:36, Emil Velikov wrote:
> Mildly related: when using meson, make that you have patchelf or similar tool.
> It nukes the RPATH, removing the need to relink the binaries [as it
> happens on make install].
>
> Perhaps meson should error out when that's missing?
Th
Hi,
On Mon, 17 Sep 2018 at 22:31, Marek Olšák wrote:
> Is there any documentation for configure options? Or do I have to do
> "grep get_option meson.build" to get the list at least?
Most of these questions can be answered by running:
meson configure $builddir
More documentation is available a
faces, preventing us from tripping over an assert.
Signed-off-by: Daniel Stone
Reported-by: Michel Dänzer
Fixes: 8c1b9882b2e0 ("egl/dri2: Guard against invalid fourcc formats")
Cc: Jason Ekstrand
---
src/gallium/state_trackers/dri/dri2.c | 6 ++
1 file changed, 6 insertions(+)
diff --gi
nlock only or free wl_buffer too (Daniel)
>
> This also fixes dEQP-EGL.functional.swap_buffers_with_damage.* tests.
Thanks Juan!
Reviewed-by: Daniel Stone
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
ts[i].fourcc == __DRI_IMAGE_FOURCC_SARGB
> > > ||
> > > + intel_image_formats[i].fourcc == __DRI_IMAGE_FOURCC_SABGR)
> > > + return false;
> > >
> >
> > This should be a continue. Fixed locally.
>
> With that, the series is
> Reviewed-by: Eric Engestrom
... and also:
Reviewed-by: Daniel Stone
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Wed, 22 Aug 2018 at 11:51, Daniel Vetter wrote:
> +See the gitlab project owners for contact details of the libdrm maintainers.
Think this should be 'See MAINTAINERS' ... ?
The rest looks good to me, though I would encourage linking to
Patchwork so people can find patches from others, as well
ver treated as signed. Might be worth a note in the commit about
signedness.
Reviewed-by: Daniel Stone
Cheers,
Daniel
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
d any new
ones. So, series is:
Acked-by: Daniel Stone
Cheers,
Daniel
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Hi Juan,
On Wed, 8 Aug 2018 at 17:40, Juan A. Suarez Romero wrote:
> On Wed, 2018-08-08 at 17:21 +0100, Daniel Stone wrote:
> > On Thu, 2 Aug 2018 at 10:02, Juan A. Suarez Romero
> > wrote:
> > > If color buffer is locked, do not set its wayland buffer to NULL;
>
e), and create the
> image.
You can eke out a little bit of a speed improvement by using the
go-faster runes from before 'apt-get update' here:
https://gitlab.freedesktop.org/wayland/weston/blob/master/.gitlab-ci.yml#L6
Anyway, this all looks great, and I'm really excited to
tely,
> and if user calls eglQuerySurface() it will return the new resized
> values.
I'm pretty confident that these two patches do the right thing; series is:
Reviewed-by: Daniel Stone
Thanks a lot for your patience & persistence!
Cheers,
Daniel
_
(causing all buffers to be released) by the
time they destroy their EGLSurface, but that's of course never going
to happen. So, assuming there's no unexpected consequences I haven't
seen, this is:
Reviewed-by: Daniel Stone
Cheers,
Daniel
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Hi Juan,
On Tue, 5 Jun 2018 at 18:23, Juan A. Suarez Romero wrote:
> On Tue, 2018-06-05 at 12:41 +0100, Daniel Stone wrote:
> > > - In Wayland/Mesa, the surface is not resized at the time the native
> > > window is
> > > resized; this is done in *eglSw
der_buffer() to return NULL and breaks
> rendering when using GLX_DOUBLEBUFFER on pixmaps.
>
> Query the root window of the pixmap on first init, and use the root
> window instead of the pixmap drawable for get_supported_modifiers()
> and pixmap_from_buffers().
Looks good to me, thanks
r usage. Due to currently
> only out of tree lima driver need it, and not sure if this is
> the right way to disable it, so I send this RFC before lima be
> able to upstream.
Series is:
Acked-by: Daniel Stone
Cheers,
Daniel
___
mesa-d
Hi Dylan,
On Tue, 19 Jun 2018 at 16:42, Dylan Baker wrote:
> Historical artifact. When I created the proposed branch we didn't have a
> policy
> of putting it on master instead of a personal repo, and we were discussing a
> transition to gitlab. I also seem to remember that the gitlab doesn't all
Hi,
On 2 June 2018 at 16:45, Jason Ekstrand wrote:
> When the migration happens, there will be a very brief (less than 30
> minutes?) period during which no one will be able to push to either repo.
> I'll fire off an e-mail as well as messages in #dri-devel and #intel-3d
> shortly before we actua
Hi Emil,
On 5 June 2018 at 18:21, Emil Velikov wrote:
> On 5 June 2018 at 18:02, Daniel Stone wrote:
>>>> drm-gralloc.git
> Empty - please nuke, alongside bugzilla & other infra.
Done.
>>>> drm.git
> Out of curiosity - this and others (say igt) projects
We definitely do, but I assume it's not been tested recently ...
(Sorry about mangled formatting)
On Wed, 6 Jun 2018, 8:42 pm Jason Ekstrand, wrote:
> On June 6, 2018 12:37:58 Daniel Stone wrote:
>
>> Right, it's a feature we use, because we do all import them as separat
Right, it's a feature we use, because we do all import them as separate
EGLImages ... and we won't if it's not advertised.
On Wed, 6 Jun 2018, 7:05 pm Jason Ekstrand, wrote:
> On Wed, Jun 6, 2018 at 11:03 AM, Jason Ekstrand
> wrote:
>
>> On Wed, Jun 6, 2018 at 11
Sorry, but as written this will regress ability to import NV12 images as
separately-addressed planes with shader conversion to RGB; Kodi, Mutter and
Weston all use this.
On Wed, 6 Jun 2018, 6:48 pm Jason Ekstrand, wrote:
> Cc: mesa-sta...@lists.freedesktop.org
> ---
> src/mesa/drivers/dri/i965/
On 5 June 2018 at 17:55, Eric Engestrom wrote:
> On Tuesday, 2018-06-05 17:52:17 +0100, Daniel Stone wrote:
>> > I assume that's now mesa, libdrm, piglit, shader-db, crucible, kmscube,
>> > mesa-demos; what about igt? Anything else?
>>
>> We current
Hi Eric,
On 5 June 2018 at 17:49, Eric Engestrom wrote:
> On Tuesday, 2018-06-05 09:11:58 -0700, Jason Ekstrand wrote:
>> Given the discussion below, I think we'll make piglit a sub-project of
>> mesa. Those who need commit access to piglit but not mesa can be added
>> directly to the piglit pro
Hi Juan,
On 5 June 2018 at 09:51, Juan A. Suarez Romero wrote:
> On Mon, 2018-06-04 at 13:22 +0100, Daniel Stone wrote:
>> The first query will correctly return (w1,h1). The second query will
>> incorrectly also return (w1,h1), even though the surface will never
>> have
On 4 June 2018 at 19:29, Dylan Baker wrote:
> Quoting Daniel Stone (2018-06-04 11:20:45)
>> Is git-lfs mainly about supporting large individual files, or large
>> collections of relatively small files? The tarballs aren't massive,
>> there are just tons of them. If it
Hi Dylan,
On 4 June 2018 at 19:18, Dylan Baker wrote:
> Quoting Daniel Stone (2018-06-03 13:19:51)
>> One thing I've just remembered is that https://www.mesa3d.org/archive/
>> serves all the tarballs for Mesa releases. Given how Pages is
>> structured, we don't ha
Hi Juan,
On 4 June 2018 at 12:43, Juan A. Suarez Romero wrote:
> On Fri, 2018-06-01 at 16:32 +0100, Daniel Stone wrote:
>> I think you're right, and this needs more rework to be consistent.
>>
>> wl_egl_window_get_attached_size() always returns the size of the last
&g
Hi Laura,
On 25 May 2018 at 01:27, Laura Ekstrand wrote:
> When reviewing these patches, please note:
> 1. This patch series does *not* touch content. Please do not bikeshed
>the content of webpages here. That will be addressed in later
>commits.
> 2. Ple
Hi,
On 2 June 2018 at 16:45, Jason Ekstrand wrote:
> My current plan (if Daniel is amenable) is to due the migration late next
> week. I'm tentatively thinking Thursday morning pacific but that may change
> depending on Daniel's schedule.
That works for me.
> When the migration happens, there
Hi,
On 1 June 2018 at 15:35, Brendan King wrote:
> IMG has a similar patch to the one you describe, but without the changes to
> the resize_callback, so just this bit:
>
> @@ -255,6 +257,12 @@ dri2_wl_create_window_surface(_EGLDriver *drv,
> _EGLDisplay *disp,
>goto cleanup_surf;
> }
Hi,
On 1 June 2018 at 11:23, Eric Engestrom wrote:
> On Friday, 2018-06-01 11:16:29 +0100, Daniel Stone wrote:
>> https://docs.gitlab.com/ee/user/project/pages/introduction.html
>> > Be aware that Pages are by default branch/tag agnostic and their
>> > deploymen
Hi,
On 1 June 2018 at 09:47, Juan A. Suarez Romero wrote:
> My question then: is mandatory to call eglSwapBuffers() to ensure
> wl_egl_window_get_attached_size() returns the right window size? Because I
> found nothing related about this. If it is mandatory, then calling
> eglSwapBuffers() in the
On 1 June 2018 at 11:10, Eric Engestrom wrote:
> On Thursday, 2018-05-31 14:59:58 -0700, Jason Ekstrand wrote:
>> If you could deal with Daniel's feedback and v3 just this patch sooner
>> rather than later, that would be good. I'd like to merge it before we
>> switch to gitlab so we can start usi
Hi Eric,
On 31 May 2018 at 17:13, Eric Engestrom wrote:
> On Thursday, 2018-05-31 16:57:17 +0100, Daniel Stone wrote:
>> Not initialising attached_{width,height} should not cause any problems
>> with these checks. By definition there cannot have been any buffers
>> allocate
(dri2_surf->wl_win->attached_width != dri2_surf->wl_win->width ||
> + dri2_surf->wl_win->attached_height != dri2_surf->wl_win->height) {
Not initialising attached_{width,height} should not cause any problems
with these checks. By definition there cannot have been any buf
Hi Laura,
On 30 May 2018 at 23:53, Laura Ekstrand wrote:
> @@ -0,0 +1,9 @@
> +pages:
> + stage: deploy
> + script:
> + - mkdir .public
> + - cp -r docs/* .public
> + - mv .public public
You should be able to just write into the 'public' folder directly.
It seems like creating a new di
Hey,
On 30 May 2018 at 21:40, Ilia Mirkin wrote:
> Given that not everyone will be a master by default, it would be good
> to also set out criteria for adding and removing masters. I'm not
> proposing anything heavy -- perhaps by a majority vote of the existing
> masters to either add or remove s
On 29 May 2018 at 15:17, Eric Engestrom wrote:
> On Tuesday, 2018-05-29 09:50:46 -0400, Adam Jackson wrote:
>> GL_LIB expands to GLX_mesa, but applications should not link against
>> that. -lGL is never wrong, just hardcode it.
>
> Agreed, and Archlinux has had this patch since basically forever:
Hey,
On 27 May 2018 at 16:35, Rob Clark wrote:
> On Sun, May 27, 2018 at 10:47 AM, Jason Ekstrand wrote:
>> Given the number of people who have said they still like the mailing list,
>> that's probably a discussion for another email thread.
>
> It would be kinda clever if gitlab could automagica
Hi,
On 26 May 2018 at 07:42, Marek Olšák wrote:
> On Thu, May 24, 2018 at 6:46 AM, Daniel Stone wrote:
>> cgit and anongit will not be orphaned: they remain as push mirrors so
>> are updated simultaneously with GItLab pushes, as will the GitHub
>> mirrors. Realisticall
Hi Mark,
On 26 May 2018 at 00:47, Mark Janes wrote:
> Daniel Stone writes:
>> We had a go at using Jenkins for some of this: Intel's been really
>> quite successful at doing it internally, but our community efforts
>> have been a miserable failure. After a few years I
Hi Eric,
On 25 May 2018 at 12:15, Eric Engestrom wrote:
> If I'm misunderstanding gitlab-ci and this is running one the same
> filesystem as the website, then you'll need to `rm -r public` before the
> move, otherwise `mv .public public` will not do what you want :)
It's always run in a fresh co
Hi,
On 24 May 2018 at 02:23, Jason Ekstrand wrote:
> On Wed, May 23, 2018 at 5:49 PM, Jordan Justen
> wrote:
>> Another project I'm involved with had a contingency that swore
>> github's "issues" were completely inadequate compared to bugzilla,
>> which is to say that I don't think there is cons
Hi,
On 24 May 2018 at 11:46, Daniel Stone wrote:
> It _is_ possible to bend Jenkins to your will - Mark's excellent and
> super-helpful work with Intel's CI is testament to that - and in some
> environments it's fine, but after a few years of trying, I just don't
&g
Hi all,
I'm going to attempt to interleave a bunch of replies here.
On 23 May 2018 at 20:34, Jason Ekstrand wrote:
> The freedesktop.org admins are trying to move as many projects and services
> as possible over to gitlab and somehow I got hoodwinked into spear-heading
> it for mesa. There are a
.2"
> CC: 18.1
> CC: Abel Garcia Dorta
> CC: Daniel Stone
Acked-by: Daniel Stone
Reviewed-by: Jason Ekstrand
Cheers,
Daniel
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Hi,
On 5 May 2018 at 19:07, Jason Ekstrand wrote:
> On Sat, May 5, 2018 at 6:34 AM, Bas Nieuwenhuizen
> wrote:
>> @@ -1043,7 +1043,8 @@ x11_image_init(VkDevice device_h, struct
>> x11_swapchain *chain,
>> uint32_t bpp = 32;
>>
>> if (chain->base.use_prime_blit) {
>> - result = wsi_
On 5 May 2018 at 10:15, Mike Lothian wrote:
> Out of interest can you try running the vulkan smoketest, I'm seeing this:
>
> smoketest
> terminate called after throwing an instance of 'std::runtime_error'
> what(): VkResult -101004 returned
> Aborted (core dumped)
VK_ERROR_OUT_OF_DATE_KHR i
On 27 April 2018 at 16:56, Michel Dänzer wrote:
> And only free no longer needed back buffers there as well.
>
> We want to stick to the same back buffer throughout a frame, otherwise
> we can run into various issues.
Thanks for dealing with this Michel!
Acked-by:
Hi Johan,
On 24 April 2018 at 09:44, Johan Helsing wrote:
> If the call to dri_destroy_buffer is delayed until the next eglMakeCurrent,
> that would also solve the problem (I'm not sure how that would affect other
> things, though).
It _must_ be:
If the EGL surface surface is not current to an
Hi Sergii,
On 6 April 2018 at 09:12, Sergii Romantsov wrote:
> Commit 3160cb86aa92 adds optimization with flag 'reallocate'.
> Processing of flag causes buffers freeing while pointer
> is still hold in caller stack and than again used to be freed.
Thanks a lot for writing this. I take it the cor
Hi all,
On 5 April 2018 at 23:55, Laura Ekstrand wrote:
> So I spoke with Daniel Stone today about the infrastructure. He estimates
> it will be ready to deploy the website in 2-3 weeks, at the most. So I'd
> say the infrastructure will be there when we are ready.
>
> In
ier which supports fast-clears.
I've been running this for a while and haven't seen any issues with it
so far, so:
Reviewed-by: Daniel Stone
Tested-by: Daniel Stone
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.free
Hi James,
On 30 March 2018 at 16:45, James Legg wrote:
> Fixes: bfa22266cd vulkan/wsi/wayland: Add support for zwp_dmabuf
> CC: Daniel Stone
> CC: Jason Ekstrand
Wow, the cleanup hunk must have been lost in a rebase somewhere. :( At
least, I think I remember writing it.
Thanks a lo
On 2 April 2018 at 18:52, Eric Anholt wrote:
> Daniel Stone writes:
>> When allocating a buffer for DRI2, set the modifier to INVALID to inform
>> the backend that we have no supplied modifiers and it should do its own
>> thing. The missed initialisation force
>modifiers_supported && modifier
!= DRM_FORMAT_MOD_INVALID)'.
With that fixed, and I suppose with the same weak-symbol handling as
the others, this is:
Reviewed-by: Daniel Stone
Cheers,
Daniel
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On 30 March 2018 at 19:20, Kenneth Graunke wrote:
> On Friday, March 30, 2018 7:40:13 AM PDT Chris Wilson wrote:
>> For i915, we are proposing to use a quality-of-service parameter in
>> addition to that of just a priority that usurps everyone. Due to our HW,
>> preemption may not be immediate and
Hi Andreas,
On 31 March 2018 at 15:18, Andreas Müller wrote:
> Thanks for prompt an VERY helpful support. I did:
>
> * Check my configure and found: --disable-dri3!
> * Tested your patch (with --disable-dri3) and as expected it fixes the issue
> * Found what causes --disable-dri3 - it came in by
Hi Juan,
On 29 March 2018 at 11:25, Juan A. Suarez Romero wrote:
> The plan is to have 17.3.8 this Monday (2nd April), around or shortly after
> 11:00
> GMT.
Does this mean we could expect 17.3.9 in a couple of weeks, or is this
the last release for the 17.3.x branch?
Cheers,
Daniel
__
:
Modifier 0x0 vs. tiling (0x701) mismatch
Signed-off-by: Daniel Stone
Reported-by: Andreas Müller
Fixes: 3f8513172ff6 ("gallium/winsys/drm: introduce modifier field to
winsys_handle")
---
src/gallium/state_trackers/dri/dri2.c | 1 +
1 file changed, 1 insertion(+)
diff -
On 23 March 2018 at 13:03, Emil Velikov wrote:
> On 22 March 2018 at 15:27, Daniel Stone wrote:
>> The version passed to QueryVersion requests is the version that the
>> client supports. We were just passing in whatever version of XCB was
>> present on the system, which may
Hi Andreas,
On 30 March 2018 at 15:18, Andreas Müller wrote:
> What happened: I build all images cross with Openembedded/Yocto. To
> prepare next release there I updated my builds and that moved mesa
> 17.1.7 -> 17.3.7. Since then all applications using GL/GLES (e.g
> glmark2-es - tried others -
11 compositor uses EGL.
I have no reason to doubt your testing, so this patch is:
Acked-by: Daniel Stone
But it does rather fill me with trepidation, given that X11 Pixmaps
are supposed to be a dumb 'bag of bits', doing nothing else than
providing the same number and size of channels
Hi Ilia,
On 14 March 2018 at 19:02, Ilia Mirkin wrote:
> On Tue, Mar 13, 2018 at 5:30 AM, Daniel Stone wrote:
>> On 12 March 2018 at 20:45, Mario Kleiner wrote:
>>> This way the wayland server can signal support for these formats
>>> to wayland EGL clients. This i
Hi Juan,
On 22 March 2018 at 16:49, Juan A. Suarez Romero wrote:
> Instead we will re-generate them again on building.
Thanks for sending the v2 - that looks good to me. There was some kind
of problem with having the sources in BUILT_SOURCES though, which Emil
might be able to remember. Is it ne
On 22 March 2018 at 15:20, Derek Foreman wrote:
> commit 03dd9a88b0be17ff0ce91e92f6902a9a85ba584a introduced per surface
> queues, but the display_sync for swrast_commit_backbuffer remained on
> the old queue. This is likely to break when dispatching the correct
> queue at the top of function (wh
which we support, and only pass those.
Signed-off-by: Daniel Stone
---
src/egl/drivers/dri2/platform_x11_dri3.c | 19 +++
src/glx/dri3_glx.c | 21 +++--
2 files changed, 30 insertions(+), 10 deletions(-)
diff --git a/src/egl/drivers/dri2
On 22 March 2018 at 11:16, Juan A. Suarez Romero wrote:
> On Thu, 2018-03-22 at 11:03 +, Emil Velikov wrote:
>> On 21 March 2018 at 13:36, Daniel Stone wrote:
>> > I thought we had resolved earlier to _not_ ship files generated by
>> > wayland-scanner in dist af
Hi Juan,
On 19 March 2018 at 17:49, Juan A. Suarez Romero wrote:
> The first two patches in the series is a new fix for issue
> https://bugs.freedesktop.org/show_bug.cgi?id=105211, as the current version
> breaks when running the above command, due "make dist/distcheck" tries to
> generate the th
On 20 March 2018 at 16:24, Dylan Baker wrote:
> Quoting Daniel Stone (2018-03-20 09:17:21)
>> The have-new-DRI3 codepaths would never actually properly trigger, since
>> there was a typo in configure.ac which broke the version check. This
>> went unnoticed but for an error
On 20 March 2018 at 16:16, Dylan Baker wrote:
> Quoting Daniel Stone (2018-03-20 01:54:25)
>> VMware has no (published) support for Arm-architecture guests.
Pushed now with review and the new suggested title - thanks both for review!
Cheer
The have-new-DRI3 codepaths would never actually properly trigger, since
there was a typo in configure.ac which broke the version check. This
went unnoticed but for an error in config.log if you looked closely
enough.
Signed-off-by: Daniel Stone
Reported-by: Lukas F. Hartmann
Fixes
VMware has no (published) support for Arm-architecture guests.
Signed-off-by: Daniel Stone
Cc: Dylan Baker
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index 88e90fe8119..24cad58c61e 100644
--- a/meson.build
+++ b/meson.build
On all Arm architectures (ARMv7 and below as 'arm', ARMv8 and above as
'aarch64'), only build swrast for DRI drivers. The only classic drivers
which could be used are r200 and NV20 cards, which seems unlikely enough
that it shouldn't be the default.
Signed-off-by:
d-off-by: Daniel Stone
Fixes: 7aeef2d4efdc ("dri3: allow building against older xcb (v3)")
Cc: Dave Airlie
---
src/egl/drivers/dri2/egl_dri2.c | 2 +-
src/egl/drivers/dri2/platform_x11_dri3.c | 10 ++
src/glx/dri3_glx.c | 8 +
Hi Dieter,
On 18 March 2018 at 00:48, Dieter Nützel wrote:
> @ least, here fromm Germany.
>
> https://patchwork.freedesktop.org/
> Server Error (500)
This is fixed now, and I think that particular problem shouldn't happen again.
Cheers,
Daniel
___
mes
Hi,
On 16 March 2018 at 15:23, Matt Turner wrote:
> On Fri, Mar 16, 2018 at 8:07 AM, Emil Velikov
> wrote:
>> On 16 March 2018 at 02:39, Matt Turner wrote:
>>> All of your messages are going to spam on gmail:
>>>
>> Setting up a filter for 'list:"mesa-dev.lists.freedesktop.org"' will help
>>
Hi Juan,
On 16 March 2018 at 11:42, Juan A. Suarez Romero wrote:
> Trivial merge conflicts
> ---
>
> [...]
>
> commit 5fd11359b66c8138d2c7ee29bd9740280b02d1e2
> Author: Daniel Stone
>
> egl/wayland: Fix ARGB/XRGB transposition in config map
Hi,
On 14 March 2018 at 13:04, Rob Clark wrote:
> I'm not sure everyone wants to be updating their dri3 in a forced
> march setting, this allows a nicer approach, esp when you want
> to build on distro that aren't brand new.
I don't have that much of an opinion on whether the dependency should
b
Hi Emil,
On 13 March 2018 at 11:40, Emil Velikov wrote:
> During development the version was bumped, yet the comment did not get
> an update.
>
> Cc: Daniel Stone
> Fixes: c80c08e2260 ("vulkan/wsi/x11: Add support for DRI3 v1.2")
> Signed-off-by: Emil Velikov
Hi Mario,
On 12 March 2018 at 20:45, Mario Kleiner wrote:
> This way the wayland server can signal support for these formats
> to wayland EGL clients. This is currently used by nouveau for 10
> bpc support.
>
> Tested with glmark2-wayland and glmark2-es2-wayland under weston
> to now expose 10 bp
Hi Juan,
On 12 March 2018 at 12:10, Juan A. Suarez Romero wrote:
> On Mon, 2018-03-12 at 11:49 +0000, Daniel Stone wrote:
>> On 12 March 2018 at 11:31, Juan A. Suarez Romero wrote:
>> > We are improving this by moving to use Gitlab CI (still wip), which allows
>> >
Hi Juan,
On 12 March 2018 at 11:31, Juan A. Suarez Romero wrote:
> On Fri, 2018-03-09 at 12:12 -0800, Mark Janes wrote:
>> Ilia Mirkin writes:
>> - CI Automation immediately builds/tests the proposed stable branch
>>whenever it changes. Release managers verify the results.
>>
>
> This is k
On 10 March 2018 at 14:53, Christian Gmeiner
wrote:
> Fixes following dependency problem:
> Native dependency xcb-dri3 found: NO found '1.11' but need: '>= 1.13'
Oh, oops! Thanks for the catch Christian.
Reviewed-by: Daniel Stone
Fixes: c80c08e22603 ("vu
Add support for XBGR2101010 and ABGR2101010.
Signed-off-by: Daniel Stone
Cc: Ilia Mirkin
---
src/egl/drivers/dri2/platform_wayland.c | 12
1 file changed, 12 insertions(+)
diff --git a/src/egl/drivers/dri2/platform_wayland.c
b/src/egl/drivers/dri2/platform_wayland.c
index
Add support for XBGR2101010 and ABGR2101010 formats.
Signed-off-by: Daniel Stone
---
src/gbm/backends/dri/gbm_dri.c | 8
1 file changed, 8 insertions(+)
diff --git a/src/gbm/backends/dri/gbm_dri.c b/src/gbm/backends/dri/gbm_dri.c
index df20db40218..b3d6ceb15a3 100644
--- a/src/gbm
Hi,
On 8 March 2018 at 17:08, Ilia Mirkin wrote:
> On Thu, Mar 8, 2018 at 11:57 AM, Mario Kleiner
> wrote:
>> Under EGL there is matching of channel masks, so only X11+GLX is
>> problematic. Not sure if anything special would need to be done for
>> XWayland, haven't looked at that at all so far.
On 5 March 2018 at 14:40, Eric Engestrom wrote:
> Note: `gbm_dri_visuals_table` doesn't need any modification, as the
> channel order doesn't change, so `rgba_mask = { r, g, b, a }` still
> works.
Yeah, this is a very definite and obvious improvement. Thanks Eric!
Review
Hi,
On 2 March 2018 at 12:06, Thierry Reding wrote:
> On Thu, Mar 01, 2018 at 09:37:28AM -0500, Ilia Mirkin wrote:
>> > +static void
>> > +nvc0_query_dmabuf_modifiers(struct pipe_screen *screen,
>> > +enum pipe_format format, int max,
>>
>> Maybe change this to "unsign
Hi,
On 28 February 2018 at 09:33, Eric Engestrom wrote:
> On Tuesday, 2018-02-27 18:01:11 +0000, Daniel Stone wrote:
>> On all Arm architectures (ARMv7 and below as 'arm', ARMv8 and above as
>> 'aarch64'), only build swrast for DRI drivers.
>
> The commit
VMware has no (published) support for Arm-architecture guests.
Signed-off-by: Daniel Stone
Cc: Dylan Baker
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index c349e9e5f85..92200a3d64a 100644
--- a/meson.build
+++ b/meson.build
On all Arm architectures (ARMv7 and below as 'arm', ARMv8 and above as
'aarch64'), only build swrast for DRI drivers. The only classic drivers
which could be used are r200 and NV20 cards, which seems unlikely enough
that it shouldn't be the default.
Signed-off-by:
Hi Dylan,
On Tue, 2018-02-27 at 09:13 -0800, Dylan Baker wrote:
> Quoting Daniel Stone (2018-02-27 02:08:29)
> > --- a/meson.build
> > +++ b/meson.build
> > @@ -100,6 +100,8 @@ if _drivers == 'auto'
> > # TODO: PPC, Sparc
> > if ['
On all Arm architectures (ARMv7 and below as 'arm', ARMv8 and above as
'aarch64'), only build swrast for DRI drivers. The only classic drivers
which could be used are r200 and NV20 cards, which seems unlikely enough
that it shouldn't be the default.
Signed-off-by:
Hi,
On 24 February 2018 at 00:43, Jason Ekstrand wrote:
> On Tue, Feb 13, 2018 at 4:31 PM, Keith Packard wrote:
>> + image->chain = chain;
>> + image->state = wsi_image_idle;
>> + image->fb_id = 0;
>> +
>> + /* XXX extract depth and bpp from image somehow */
>
> You have the format in cr
Reviewed-by: Daniel Stone You can probably tell I only tested XRGB. Sorry!___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Hi Marc,
On 23 February 2018 at 15:42, Marc Dietrich wrote:
> Am Freitag, 23. Februar 2018, 14:31:30 CET schrieb Daniel Stone:
>> On 20 February 2018 at 18:36, Dylan Baker wrote:
>> > Currently meson will generate a pkg-config that links to EGL_mesa (or
>> > GLX_me
Hi Marc,
On 23 February 2018 at 12:58, Marc Dietrich wrote:
> my system has problems with linking xdemos:
> ...
> CCLD glsync
> /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld:
> glsync.o: undefined reference to symbol 'glXQueryExtensionsString'
> /usr/lib64/libGL.
Hi Dylan,
On 20 February 2018 at 18:36, Dylan Baker wrote:
> Currently meson will generate a pkg-config that links to EGL_mesa (or
> GLX_mesa), but this isn't correct, it should always link to EGL or GL.
> Probably the "right" solution is to have glvnd itself provide the pkg
> config files for GL
101 - 200 of 798 matches
Mail list logo
