sorry, my mail server was down most of the weekend, this one got stuck.
On Wed, Jan 11, 2012 at 07:38:11AM -0800, Chase Douglas wrote:
The current code partially reconstructs the touch begin event when
replaying touch history. This change ensures the original begin event
is replayed, including
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/2012 04:47 AM, Daniel Vetter wrote:
On Tue, Jan 10, 2012 at 10:15:01AM +0530, Sateesh Kavuri wrote:
Added support for Android. Changes include fixes for compilation issues
related to Android using an older version of GCC compiler (ver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/16/2012 10:36 AM, Daniel Vetter wrote:
On Mon, Jan 16, 2012 at 10:25:32AM -0800, Chad Versace wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/2012 04:47 AM, Daniel Vetter wrote:
On Tue, Jan 10, 2012 at 10:15:01AM +0530,
On Mon, Jan 16, 2012 at 16:36, Daniel Vetter dan...@ffwll.ch wrote:
Otherwise we'll just stick Android.mk into the root dir and I'll forget
about this (and probably break it every time I change something).
I vote for this approach. It would only be used by android build, so when
it breaks,
Hi,
On 16 January 2012 18:53, Chad Versace chad.vers...@linux.intel.com wrote:
On 01/16/2012 10:36 AM, Daniel Vetter wrote:
I've just read about androgenizer:
http://cgit.collabora.com/git/user/derek/androgenizer.git/
Would that be a useful to at least generate the Android.mk in a sensible
On Sun, 15 Jan 2012 02:35:03 -0800, Jeremy Huddleston jerem...@apple.com
wrote:
Jeremy Huddleston (5):
Revert glx: don't leak fbconfigs
The comment on this one says that the correct fix is in
__glXDRIscreenDestroy, but I don't see those functions doing this. Do we
need another patch
Not all Bourne shell implementation have substr
Signed-off-by: Gaetan Nadon mems...@videotron.ca
---
build.sh | 16 +---
1 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/build.sh b/build.sh
index b01d652..29bdd17 100755
--- a/build.sh
+++ b/build.sh
@@ -80,12 +80,14
Gaetan Nadon mems...@videotron.ca (16/01/2012):
Not all Bourne shell implementation have substr
Maybe better written as:
case foo in
bar) …
;;
esac?
Mraw,
KiBi.
signature.asc
Description: Digital signature
___
xorg-devel@lists.x.org: X.Org
On Jan 16, 2012, at 12:09 PM, Keith Packard wrote:
On Sun, 15 Jan 2012 02:35:03 -0800, Jeremy Huddleston jerem...@apple.com
wrote:
Jeremy Huddleston (5):
Revert glx: don't leak fbconfigs
The comment on this one says that the correct fix is in
__glXDRIscreenDestroy, but I don't
On 12-01-16 05:20 PM, Cyril Brulebois wrote:
Gaetan Nadon mems...@videotron.ca (16/01/2012):
Not all Bourne shell implementation have substr
Maybe better written as:
case foo in
bar) …
;;
esac?
I am not sure what you are suggesting. The goal is to test whether the
variable holds a full
Not all expr implementations have a substr string argument.
According to the POSIX standard, the use of string arguments length,
substr, index, or match produces undefined results.
http://www.freebsd.org/cgi/man.cgi?query=exprapropos=0sektion=0manpath=
On Mon, 16 Jan 2012 14:35:12 -0800, Jeremy Huddleston jerem...@apple.com
wrote:
Sorry if the comment was ambiguous, but I did not mean to imply that
the fix was present already or provided. Reverting this patch does
return the memory leak when using glxdri, and a followup needs to be
From: Trevor Woerner twoer...@gmail.com
Allow a user to specify per-component configure options by
providing them in the --modfile file. Any text remaining on
a line following a given module/component is assumed to be
options which will be passed to the configuration script.
Signed-off-by:
On Jan 16, 2012, at 3:18 PM, Keith Packard wrote:
On Mon, 16 Jan 2012 14:35:12 -0800, Jeremy Huddleston jerem...@apple.com
wrote:
Sorry if the comment was ambiguous, but I did not mean to imply that
the fix was present already or provided. Reverting this patch does
return the memory
On Mon, 16 Jan 2012 15:29:22 -0800, Jeremy Huddleston jerem...@apple.com
wrote:
Well the change that is being reverted *does* cause a regression, so
it should be reverted on that grounds alone. It will be no worse than
our released servers which didn't free that memory. Of course this
On 01/14/2012 02:52 AM, Julien Cristau wrote:
On Fri, Jan 13, 2012 at 16:12:25 -0800, Chad Versace wrote:
When attempting to open the console device during initialization, X first
tries to open /dev/tty0 in write-only mode, and if that fails it attempts
to open /dev/vc/0. If both attempts
If a device has both relative and absolute axes, we'd initialise the
relative axes but label them with the absolute labels.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/evdev.c | 25 ++---
1 files changed, 18 insertions(+), 7 deletions(-)
diff --git
On Sat, Jan 14, 2012 at 10:20:03AM +0100, Tormod Volden wrote:
On Wed, Jan 4, 2012 at 5:14 AM, Peter Hutterer peter.hutte...@who-t.net
wrote:
XF86DRI is defined by xorg-server.h, so --disable-dri in the sis driver
itself does exactly nothing other than not fill in the CFLAGS and thus stop
XF86DRI is defined by xorg-server.h, so --disable-dri in the driver
itself does exactly nothing other than not fill in the CFLAGS
and thus stop the driver from compiling.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
configure.ac |4 ++--
src/mga.h| 10 +++---
XF86DRI is defined by xorg-server.h, so --disable-dri in the driver
itself does exactly nothing other than not fill in the CFLAGS and thus stop
the driver from compiling.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
configure.ac |4 ++--
src/r128.h| 14
XF86DRI is defined by xorg-server.h, so --disable-dri in the driver
itself does exactly nothing other than not fill in the CFLAGS and thus stop
the driver from compiling.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
configure.ac|4 ++--
src/savage_accel.c |4 ++--
XF86DRI is defined by xorg-server.h, so --disable-dri in the driver
itself does exactly nothing other than not fill in the CFLAGS and thus stop
the driver from compiling.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
configure.ac |4 ++--
src/tdfx.h| 10 +++---
On Fri, Jan 13, 2012 at 01:43:01PM -0800, Jeremy Huddleston wrote:
This is provided by dixmods/libshadow.so and is not part of the main binary.
This addresses a build failure on darwin due to MIEXT_SHADOW_LIB having
unsatisfied dependencies (FB_LIB) in XORG_LIBS.
Signed-off-by: Jeremy
23 matches
Mail list logo
