Re: [PATCH 4/5] Support backtracing through elfutils (#70746)

2013-11-14 Thread Keith Packard
Peter Hutterer peter.hutte...@who-t.net writes: On Tue, Oct 29, 2013 at 10:13:28PM -0400, Jasper St. Pierre wrote: I'm not a fan at all. This API is really bad compared to what's provided by libbacktrace, which is super simple. This also seem to require callbacks that have Linux in the name.

Re: [PULL] xephyr fixes

2013-11-14 Thread Keith Packard
Peter Hutterer peter.hutte...@who-t.net writes: Keith, pls note that I added the diff you sent me in reply as a patch authored and signed-off-by you. Thanks. Keith Packard (1): kdrive: handle WxH as valid geometry spec Peter Hutterer (4): ephyr: xcb_connect returns an error,

[PATCH xf86-video-modesetting] Track X server API changes for DamageUnregister

2013-11-14 Thread Keith Packard
DamageUnregister takes only one argument now. Signed-off-by: Keith Packard kei...@keithp.com --- Here's a fix for the X server API change src/driver.c | 4 ++-- src/drmmode_display.c | 3 +-- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/src/driver.c b/src/driver.c

Re: xf86-video-armsoc, Mali and exynos4

2013-11-14 Thread Daniel Drake
On Wed, Nov 13, 2013 at 7:10 PM, Siarhei Siamashka siarhei.siamas...@gmail.com wrote: I was considering to get xrandr working at least on sunxi hardware. So that dual monitor support and screen resolution switching at runtime works in X11 desktop in a standard way transparently for the

Re: [PATCH xf86-video-modesetting] Track X server API changes for DamageUnregister

2013-11-14 Thread Gaetan Nadon
On 13-11-14 03:09 AM, Keith Packard wrote: - DamageUnregister(pScreen-GetScreenPixmap(pScreen)-drawable, ms-damage); + DamageUnregister(ms-damage); Wouldn't that break on earlier server versions? The Intel driver added this code in compat-api.h: #if XORG_VERSION_CURRENT =

Re: xf86-video-armsoc, Mali and exynos4

2013-11-14 Thread Luc Verhaegen
On Thu, Nov 14, 2013 at 06:57:37AM -0600, Daniel Drake wrote: Yes, it works reasonably well. Not perfect, I did catch a hang, and 800x600 doesn't work quite right, but I think that is fixable. I'd definitely invest more time into it if/when it seems like there is an available X DDX with Mali

Re: xf86-video-armsoc, Mali and exynos4

2013-11-14 Thread Daniel Drake
On Thu, Nov 14, 2013 at 7:20 AM, Luc Verhaegen l...@skynet.be wrote: On Thu, Nov 14, 2013 at 06:57:37AM -0600, Daniel Drake wrote: Yes, it works reasonably well. Not perfect, I did catch a hang, and 800x600 doesn't work quite right, but I think that is fixable. I'd definitely invest more time

Re: [PATCH xf86-video-modesetting] Track X server API changes for DamageUnregister

2013-11-14 Thread Keith Packard
Gaetan Nadon mems...@videotron.ca writes: On 13-11-14 03:09 AM, Keith Packard wrote: -DamageUnregister(pScreen-GetScreenPixmap(pScreen)-drawable, ms-damage); +DamageUnregister(ms-damage); Wouldn't that break on earlier server versions? Yes. The Intel driver added this code in

Re: xf86-video-armsoc, Mali and exynos4

2013-11-14 Thread Luc Verhaegen
On Thu, Nov 14, 2013 at 07:26:13AM -0600, Daniel Drake wrote: On Thu, Nov 14, 2013 at 7:20 AM, Luc Verhaegen l...@skynet.be wrote: On Thu, Nov 14, 2013 at 06:57:37AM -0600, Daniel Drake wrote: Yes, it works reasonably well. Not perfect, I did catch a hang, and 800x600 doesn't work quite

Re: modular: Changes to 'master'

2013-11-14 Thread Jeremy Huddleston Sequoia
As libxshmfence is Linux-only (or is it Linux + Solaris now), including it in xorg.modules for everyone causes build failure for everyone else... http://tinderbox.x.org/builds/2013-11-14-0003/ --Jeremy On Nov 13, 2013, at 9:59, Rob Clark robcl...@kemper.freedesktop.org wrote: xorg.modules |

Re: [PULL] GLX fixes and etc.

2013-11-14 Thread Adam Jackson
On Thu, 2013-11-14 at 16:28 +0900, Keith Packard wrote: Adam Jackson a...@redhat.com writes: Adam Jackson (6): damage: Remove isWindow from the DamageRec xfree86: Bump to video ABI 15 and input ABI 20 glx: Remove current context cache glx: Fix memory leak in

Re: modular: Changes to 'master'

2013-11-14 Thread Gaetan Nadon
On 13-11-14 01:34 PM, Jeremy Huddleston Sequoia wrote: As libxshmfence is Linux-only (or is it Linux + Solaris now), including it in xorg.modules for everyone causes build failure for everyone else... This raises an interesting question. Should the modules list be the lowest common denominator?

Re: [PATCH 4/5] Support backtracing through elfutils (#70746)

2013-11-14 Thread Peter Hutterer
On Thu, Nov 14, 2013 at 05:00:29PM +0900, Keith Packard wrote: Peter Hutterer peter.hutte...@who-t.net writes: On Tue, Oct 29, 2013 at 10:13:28PM -0400, Jasper St. Pierre wrote: I'm not a fan at all. This API is really bad compared to what's provided by libbacktrace, which is super

Re: [PATCH 4/5] Support backtracing through elfutils (#70746)

2013-11-14 Thread Keith Packard
Peter Hutterer peter.hutte...@who-t.net writes: From the discussion I gathered that libunwind is the best option for now until someone implements and external backtracer through fork() + exec(). Sounds good. So please ignore this patchset. I was wondering whether we should add some

[PATCH] configure: allow for --enable-libunwind and --disable-libunwind

2013-11-14 Thread Peter Hutterer
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net --- configure.ac | 15 --- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/configure.ac b/configure.ac index eb90b1a..f08c914 100644 --- a/configure.ac +++ b/configure.ac @@ -306,10 +306,18 @@

Fwd: [oss-security] I miss LSD, slides, paper and tools relating to finding UNIX system level vulnerabilities (as given at 44CON)

2013-11-14 Thread Alan Coopersmith
As we expand our use of shared memory via the new extensions, we should try to make sure we're not making more problems along the lines of those mentioned in the presentation linked below associated whitepaper published at:

[PATCH 1/2] glx: Fix incorrect use of dri_interface.h version defines in extensions.

2013-11-14 Thread Eric Anholt
Those defines are so you can compile-time check do I have a dri_interface.h that defines this new field of the struct? You don't want the server to claim it implements the new struct just because you installed a new copy of Mesa. --- glx/glxdri2.c | 4 ++-- glx/glxdricommon.c | 2 +-

[PATCH 2/2] glx: Fix incorrect use of dri_interface.h version defines in driver probing.

2013-11-14 Thread Eric Anholt
If we extend __DRI_CORE or __DRI_SWRAST in dri_interface.h to allow a new version, it shouldn't make old server code retroactively require the new version from swrast drivers. Notably, new Mesa defines __DRI_SWRAST version 4, but we still want to be able to probe version 1 drivers, since we don't

[PATCH] hw/xfree86: Make strings in DriverRec and ScrnInfoRec const

2013-11-14 Thread Keith Packard
This avoids compiler warnings when initializing with string constants. Signed-off-by: Keith Packard kei...@keithp.com --- hw/xfree86/common/xf86str.h | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/hw/xfree86/common/xf86str.h b/hw/xfree86/common/xf86str.h index

Re: Fwd: [oss-security] I miss LSD, slides, paper and tools relating to finding UNIX system level vulnerabilities (as given at 44CON)

2013-11-14 Thread Matthieu Herrb
On Thu, Nov 14, 2013 at 06:18:06PM -0800, Alan Coopersmith wrote: As we expand our use of shared memory via the new extensions, we should try to make sure we're not making more problems along the lines of those mentioned in the presentation linked below associated whitepaper published at:

Re: Fwd: [oss-security] I miss LSD, slides, paper and tools relating to finding UNIX system level vulnerabilities (as given at 44CON)

2013-11-14 Thread Mouse
My understanding is that the new code, by passing shared memory through fd is a lot better since [...] In those respects, yes. But it's worse in that it requires write access to a filesystem - a filesystem which supports mmap - with space enough to hold the shared memory segments, which

Re: [PATCH] configure: allow for --enable-libunwind and --disable-libunwind

2013-11-14 Thread Rémi Cardona
Le vendredi 15 novembre 2013 à 11:25 +1000, Peter Hutterer a écrit : -AM_CONDITIONAL(HAVE_LIBUNWIND, [test x$HAVE_LIBUNWIND = xyes]) [...] +AM_CONDITIONAL(LIBUNWIND, [test x$LIBUNWIND = xyes]) That's not going to work unless the conditional variable in os/Makefile.am is updated as well. Other

Re: Fwd: [oss-security] I miss LSD, slides, paper and tools relating to finding UNIX system level vulnerabilities (as given at 44CON)

2013-11-14 Thread Matthieu Herrb
On Fri, Nov 15, 2013 at 02:16:19AM -0500, Mouse wrote: My understanding is that the new code, by passing shared memory through fd is a lot better since [...] In those respects, yes. But it's worse in that it requires write access to a filesystem - a filesystem which supports mmap - with