Re: [PATCH app/xrandr] Document that --dpi and --fbmm options set DPI of whole X screen

2017-06-28 Thread Pali Rohár
On Saturday 10 June 2017 21:19:32 Pali Rohár wrote:
> On Sunday 28 May 2017 23:33:59 Pali Rohár wrote:
> > Explicitly document and make it clear that those options does not
> > change DPI of some monitor output. Also state that these options
> > have no useful meaning for multi-monitor configuration.
> 
> I would like to remind this patch. Can you review/comment it?

Any opinion on this patch?

-- 
Pali Rohár
pali.ro...@gmail.com


signature.asc
Description: This is a digitally signed message part.
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

[PATCH xserver] glamor: update "required EGL extensions" comment

2017-06-28 Thread Emil Velikov
From: Emil Velikov 

The extensions listed have not been needed in a while. Replace with the
only remaining requirement.

Signed-off-by: Emil Velikov 
---
Decided to keep KHR_gl_texture_2D_image as-is (as opposed to respinning
the other patch I've just sent) since the hunk is badly outdated anyway.
Can split/squash if people prefer.
---
 glamor/glamor.h | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/glamor/glamor.h b/glamor/glamor.h
index 4ad28df17..5b15a46e5 100644
--- a/glamor/glamor.h
+++ b/glamor/glamor.h
@@ -155,8 +155,7 @@ extern _X_EXPORT struct gbm_device 
*glamor_egl_get_gbm_device(ScreenPtr screen);
  *
  * The EGL layer needs to have the following extensions working:
  *
- * .EGL_KHR_gl_texture_2D_image
- * .EGL_EXT_image_dma_buf_import
+ * .EGL_KHR_surfaceless_context
  * */
 extern _X_EXPORT Bool glamor_supports_pixmap_import_export(ScreenPtr screen);
 
-- 
2.13.0

___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

[PATCH xserver] glamor: remove no longer needed KHR_gl_texture_2D_image requirement

2017-06-28 Thread Emil Velikov
From: Emil Velikov 

The code that needed it was introduced with commit 7cfd9cc2327 ("Add
DRI3 support to glamor") back in 2013. And was nuked a couple of years
ago with commit 51984dddfcc ("glamor: Delay making pixmaps shareable
until we need to.")

Cc: Eric Anholt 
Signed-off-by: Emil Velikov 
---
 glamor/glamor_egl.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/glamor/glamor_egl.c b/glamor/glamor_egl.c
index b0d3e9efe..53a74b8da 100644
--- a/glamor/glamor_egl.c
+++ b/glamor/glamor_egl.c
@@ -665,7 +665,6 @@ glamor_egl_init(ScrnInfoPtr scrn, int fd)
goto error;  \
}
 
-GLAMOR_CHECK_EGL_EXTENSION(KHR_gl_texture_2D_image);
 GLAMOR_CHECK_EGL_EXTENSION(KHR_surfaceless_context);
 
 if (eglBindAPI(EGL_OPENGL_API)) {
-- 
2.13.0

___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

Re: Stabilizing Xdmx -- advice

2017-06-28 Thread Adam Jackson
On Wed, 2017-06-28 at 16:53 -0400, jrmarsha wrote:
> I'm a bioinformatics graduate with at most a month and a half to work on 
> this.  I think this is beyond my paygrade to just pick up and try to 
> handle anything touching openGL.

Sure. The offer to check out the backtrace still stands (Xdmx should
print a backtrace when it crashes just like any other server), consider
this list an oracle that consumes backtraces and produces patches ;)

- ajax
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

Re: Stabilizing Xdmx -- advice

2017-06-28 Thread jrmarsha
I'm a bioinformatics graduate with at most a month and a half to work on 
this.  I think this is beyond my paygrade to just pick up and try to 
handle anything touching openGL.



On 06/28/2017 04:53 PM, Adam Jackson wrote:

On Fri, 2017-06-23 at 13:50 -0400, Joshua Marshall wrote:

Hello all,

Xdmx is giving me a fair bit of trouble.  In particular regard to
segfaulting.  Now, I'm assuming all the easy to catch stuff is
already done, so where in general should I give attention to
improving the state of Xdmx?

Probably an unwise assumption, dmx doesn't get much active attention
(though we do enjoy deleting code from it). I sent a patch for a crash
in the GLX code a bit ago:

https://patchwork.freedesktop.org/patch/162156/

Which I need to revisit to fix properly, but which seems to work at
least on the first generation. If you wanted to address the review
feedback and resubmit it that'd be awesome (I'm blowing up some other
glx code at the moment so I'll get back to it eventually, but Xorg and
Xwayland are more urgent targets for me).

Beyond that: if you're having a crash, post the backtrace here and
we'll help figure it out. The GLX proxy is really the ickiest part of
that server, the rest is pretty docile I find.

- ajax


___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

Re: Stabilizing Xdmx -- advice

2017-06-28 Thread Adam Jackson
On Fri, 2017-06-23 at 13:50 -0400, Joshua Marshall wrote:
> Hello all,
> 
> Xdmx is giving me a fair bit of trouble.  In particular regard to
> segfaulting.  Now, I'm assuming all the easy to catch stuff is
> already done, so where in general should I give attention to
> improving the state of Xdmx?

Probably an unwise assumption, dmx doesn't get much active attention
(though we do enjoy deleting code from it). I sent a patch for a crash
in the GLX code a bit ago:

https://patchwork.freedesktop.org/patch/162156/

Which I need to revisit to fix properly, but which seems to work at
least on the first generation. If you wanted to address the review
feedback and resubmit it that'd be awesome (I'm blowing up some other
glx code at the moment so I'll get back to it eventually, but Xorg and
Xwayland are more urgent targets for me).

Beyond that: if you're having a crash, post the backtrace here and
we'll help figure it out. The GLX proxy is really the ickiest part of
that server, the rest is pretty docile I find.

- ajax
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel

Re: [PATCH xserver 0/4] meson building Xorg server on Cygwin

2017-06-28 Thread Jon Turney

On 27/06/2017 17:45, Adam Jackson wrote:

On Mon, 2017-06-26 at 14:54 +0100, Jon Turney wrote:

Additions to meson build for building the Xorg server on Cygwin (cf. changes
to autotools build in commit c7b16255)

Note that 4/4 relies on a meson PR which is not yet accepted.

Jon Turney (4):
   Move statically linked xorgxkb files from dixmods to a separate
 directory
   meson: Shuffle around subdirs so we build Xorg loadable modules after
 Xorg
   meson: Use --export-all-symbols when building PE/COFF objects


1/3 broke 'make check' because it missed test/Makefile.am. Fixed that
up and merged these three:


Thanks for catching that.
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel