[PATCH:intel-gpu-tools] tests/gem_seqno_wrap.c: include signal.h for definition of kill()
Fixes build failure on Solaris: gem_seqno_wrap.c: In function ‘run_cmd’: gem_seqno_wrap.c:328:3: error: implicit declaration of function ‘kill’ [-Werror=implicit-function-declaration] Signed-off-by: Alan Coopersmith alan.coopersm...@oracle.com --- tests/gem_seqno_wrap.c |1 + 1 file changed, 1 insertion(+) diff --git a/tests/gem_seqno_wrap.c b/tests/gem_seqno_wrap.c index 2b92cb8..f881245 100644 --- a/tests/gem_seqno_wrap.c +++ b/tests/gem_seqno_wrap.c @@ -40,6 +40,7 @@ #include sys/wait.h #include limits.h #include wordexp.h +#include signal.h #include i915_drm.h #include intel_bufmgr.h -- 1.7.9.2 ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
Re: [Patches] Tiny cleanups to sessreg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/15/12 11:42 AM, Ed Schouten wrote: Hi all, Attached are some tiny cleanup fixes for sessreg. Thanks, pushed to git master: To ssh://git.freedesktop.org/git/xorg/app/sessreg 1d609a5..64e7738 master - master - -- -Alan Coopersmith- alan.coopersm...@oracle.com Oracle Solaris Engineering - http://blogs.oracle.com/alanc -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (SunOS) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlDONCEACgkQovueCB8tEw6lMgCcDBGM3a8BFas1Hlbe9utLe5zi 698AoIeq89xKP9ytRp1Zm/TJOioKAkYt =PlEe -END PGP SIGNATURE- ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
Re: [PATCH xf86-video-mach64] Remove dummy UTS / DFS hooks
On 12/ 7/12 02:21 PM, Alan Coopersmith wrote: On 12/ 7/12 01:53 PM, Connor Behan wrote: When EXA was added to mach64, it included UploadToScreen and DownloadFromScreen hooks that did the same thing that EXA would do in a software fallback. Now they are out of date and cause crashes. The slight benefit of reimplementing those hooks (if there is any) is not worth the maintenance burden of having to rewrite them every time there is a change to the way EXA handles pixmaps. Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=51137 Signed-off-by: Connor Behan connor.be...@gmail.com Confirmed that replacing your previous patch with this one I can still login to GNOME and bring up Firefox on the Sun Ultra 20 test system we have here (the original model had a RageXL chip onboard, before moving to ES-1000 for RoHS compliance in later revs). Tested-by: Alan Coopersmith alan.coopersm...@oracle.com Didn't see anyone else comment or respond in a week, so I've gone ahead and pushed to git master now: To ssh://git.freedesktop.org/git/xorg/driver/xf86-video-mach64 f0d44c1..ece8d35 master - master Unless anyone speaks up soon, I'll probably cut a 6.9.4 release in the next couple days so I can ship it with our Xorg 1.13.1 packages without having to add a bunch more patches. -- -Alan Coopersmith- alan.coopersm...@oracle.com Oracle Solaris Engineering - http://blogs.oracle.com/alanc ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
[PATCH:libXau 2/2] Tell clang to shut up about the padding in struct xauth
We can't clean it up without breaking ABI, so disable the warnings for it:
./include/X11/Xauth.h:33:19: warning: padding struct 'struct xauth' with 4
bytes to align 'address' [-Wpadded]
char*address;
^
./include/X11/Xauth.h:35:19: warning: padding struct 'struct xauth' with 6
bytes to align 'number' [-Wpadded]
char*number;
^
./include/X11/Xauth.h:37:19: warning: padding struct 'struct xauth' with 6
bytes to align 'name' [-Wpadded]
char*name;
^
./include/X11/Xauth.h:39:18: warning: padding struct 'struct xauth' with 6
bytes to align 'data' [-Wpadded]
char*data;
^
Signed-off-by: Alan Coopersmith alan.coopersm...@oracle.com
---
include/X11/Xauth.h | 12
1 file changed, 12 insertions(+)
diff --git a/include/X11/Xauth.h b/include/X11/Xauth.h
index f57a1b3..a707bed 100644
--- a/include/X11/Xauth.h
+++ b/include/X11/Xauth.h
@@ -27,6 +27,14 @@ in this Software without prior written authorization from
The Open Group.
#ifndef _Xauth_h
#define _Xauth_h
+/* struct xauth is full of implicit padding to properly align the pointers
+ after the length fields. We can't clean that up without breaking ABI,
+ so tell clang not to bother complaining about it. */
+#ifdef __clang__
+#pragma clang diagnostic push
+#pragma clang diagnostic ignored -Wpadded
+#endif
+
typedef struct xauth {
unsigned short family;
unsigned short address_length;
@@ -39,6 +47,10 @@ typedef struct xauth {
char *data;
} Xauth;
+#ifdef __clang__
+#pragma clang diagnostic pop
+#endif
+
#ifndef _XAUTH_STRUCT_ONLY
# include X11/Xfuncproto.h
--
1.7.9.2
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
[PATCH:libXau 1/2] Clean up some clang warnings about sign conversion
fread fwrite are defined as taking size_t arguments (an unsigned type),
so stop casting their arguments to a signed int just to confuse things.
Fixes warnings:
AuFileName.c:69:59: warning: implicit conversion loses integer precision:
'unsigned long' to 'int' [-Wshorten-64-to-32]
size = strlen (name) + strlen(slashDotXauthority[1]) + 2;
~ ~~~^~~
AuRead.c:58:44: warning: implicit conversion changes signedness: 'int' to
'size_t' (aka 'unsigned long') [-Wsign-conversion]
if (fread (data, (int) sizeof (char), (int) len, file) != len) {
~ ^
AuWrite.c:49:46: warning: implicit conversion changes signedness: 'int' to
'size_t' (aka 'unsigned long') [-Wsign-conversion]
if (fwrite (string, (int) sizeof (char), (int) count, file) != count)
~~ ^~~
Signed-off-by: Alan Coopersmith alan.coopersm...@oracle.com
---
AuFileName.c |6 +++---
AuRead.c |4 ++--
AuWrite.c|4 ++--
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/AuFileName.c b/AuFileName.c
index bc7b177..473fad1 100644
--- a/AuFileName.c
+++ b/AuFileName.c
@@ -45,12 +45,12 @@ XauFileName (void)
{
const char *slashDotXauthority = /.Xauthority;
char*name;
-static int bsize;
+static size_t bsize;
static int atexit_registered = 0;
#ifdef WIN32
chardir[128];
#endif
-intsize;
+size_t size;
if ((name = getenv (XAUTHORITY)))
return name;
@@ -70,7 +70,7 @@ XauFileName (void)
if (size bsize) {
if (buf)
free (buf);
- buf = malloc ((unsigned) size);
+ buf = malloc (size);
if (!buf)
return NULL;
diff --git a/AuRead.c b/AuRead.c
index 3c59632..5d41f03 100644
--- a/AuRead.c
+++ b/AuRead.c
@@ -35,7 +35,7 @@ read_short (unsigned short *shortp, FILE *file)
{
unsigned char file_short[2];
-if (fread ((char *) file_short, (int) sizeof (file_short), 1, file) != 1)
+if (fread ((char *) file_short, sizeof (file_short), 1, file) != 1)
return 0;
*shortp = file_short[0] * 256 + file_short[1];
return 1;
@@ -55,7 +55,7 @@ read_counted_string (unsigned short *countp, char **stringp,
FILE *file)
data = malloc ((unsigned) len);
if (!data)
return 0;
- if (fread (data, (int) sizeof (char), (int) len, file) != len) {
+ if (fread (data, sizeof (char), len, file) != len) {
bzero (data, len);
free (data);
return 0;
diff --git a/AuWrite.c b/AuWrite.c
index 0924f8d..1eb38a3 100644
--- a/AuWrite.c
+++ b/AuWrite.c
@@ -36,7 +36,7 @@ write_short (unsigned short s, FILE *file)
file_short[0] = (s (unsigned)0xff00) 8;
file_short[1] = s 0xff;
-if (fwrite ((char *) file_short, (int) sizeof (file_short), 1, file) != 1)
+if (fwrite ((char *) file_short, sizeof (file_short), 1, file) != 1)
return 0;
return 1;
}
@@ -46,7 +46,7 @@ write_counted_string (unsigned short count, char *string,
FILE *file)
{
if (write_short (count, file) == 0)
return 0;
-if (fwrite (string, (int) sizeof (char), (int) count, file) != count)
+if (fwrite (string, sizeof (char), count, file) != count)
return 0;
return 1;
}
--
1.7.9.2
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
Re: [PATCH 00/29] Pointer barrier events and barrier releases
n Wed, Dec 12, 2012 at 2:18 AM, Peter Hutterer peter.hutte...@who-t.netwrote: This is the server-side for the pointer-barrier patches, proposed as XI 2.3. It adds events for pointer barriers (when the pointer hits vs leaves the arrier) and the ability to release a pointer across. I hereby propose this for the 1.14 release. Trees for testing available from: git://people.freedesktop.org/~whot/xserver.git barriers git://people.freedesktop.org/~whot/libXi.git barriers git://people.freedesktop.org/~whot/inputproto.git barriers More verbose description: http://who-t.blogspot.com.au/2012/12/whats-new-in-xi-23-pointer-barrier.html KNOWN BROKEN: events/releases in the MPX case, though it works fine if the barrier doesn't apply to more than one device at a time. - releases currently ignore the device id - too many leave events may be sent if a barrier applies to multiple devices I've got patches here that fix this, but they're not quite finished yet. Either way, that's a narrow use-case and it will be fixed before the release. Reviewed-by: Jasper St. Pierre jstpie...@mecheye.net Many thanks to Jasper St. Pierre, who did most of the legwork here. And of course Chris Halse-Rogers who started with this feature quite a while ago. Cheers, Peter ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel -- Jasper ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
Re: [PATCH xf86-video-mach64] Remove dummy UTS / DFS hooks
On Sun, Dec 16, 2012 at 4:01 PM, Alan Coopersmith alan.coopersm...@oracle.com wrote: anyone else comment or respond in a week, so I've gone ahead and pushed to git master now: To ssh://git.freedesktop.org/git/xorg/driver/xf86-video-mach64 f0d44c1..ece8d35 master - master Unless anyone speaks up soon, I'll probably cut a 6.9.4 release in the next couple days so I can ship it with our Xorg 1.13.1 packages without having to add a bunch more patches. Perfect! Thanks, Alex ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
[PULL] pointer barrier events/releases (XI2.3)
The following changes since commit b51a1bd2766e7dc975ca8f1cacc3f8bd0e1a68a3: Merge remote-tracking branch 'whot/for-keith' (2012-11-30 09:31:46 -0800) are available in the git repository at: git://people.freedesktop.org/~whot/xserver barriers for you to fetch changes up to 1fe6c2ef09bd7422e20ef7f7f8d38f2d773d842b: Xi: if a MD is removed, send a barrier leave event (if applicable) (2012-12-17 15:04:11 +1000) Jasper St. Pierre (14): cursor: Move pointer barrier code over to XI barriers: Don't loop over the server to destroy a barrier barriers: Switch to an explicit hook for barrier constrainment barriers: Switch to finding the nearest barrier client barriers: Reindent the constrainment hook Add support for XI2.3: Pointer barrier events and releases. barriers: Add support for edge cases when releasing barriers barriers: Add a couple pixels of elbow room for the hit detection barriers: Increment event ID on hit box leave barriers: Send a BarrierLeave event when we leave the hitbox barriers: Clean up code barriers: Send an XI_BarrierLeave event when a barrier is destroyed barriers: Replace complex intersection test with simpler math barriers: Support line and ray barriers Peter Hutterer (19): include: fix comment barriers: Don't allow destroying other client's barriers barriers: Don't allow releasing the pointer on other client's barriers Pass the event list through to the pointer barrier code to return it Xi: fill in barrier root x/y after clamping to RandR outputs dix: skip delivery if it's not the right pointer barrier client dix: handle barrier events properly when converting to core/XI 1.x dix: ignore barrier events in FixUpEventFromWindow Xi: deliver barrier events as grabbed events where necessary Xi: if the device is currently grabbed, flag the barrier event mi: rename mipointer's internal event list Require inputproto 2.2.99.1 tests/xi2: at protocol conversion test for barrier events Xi: swap sequence number and evtype in barrier events Xi: fix swapping for barrier events dix: don't copy the wrong event mask when activating a passive grab Xi: fix per-device barrier handling Xi: don't store the window pointer in barriers, store the window ID Xi: if a MD is removed, send a barrier leave event (if applicable) Xi/Makefile.am | 2 + Xi/exevents.c| 47 ++ Xi/extinit.c | 41 +- Xi/xibarriers.c | 916 +++ Xi/xibarriers.h | 48 ++ Xi/xichangehierarchy.c | 6 + configure.ac | 2 +- dix/eventconvert.c | 43 ++ dix/events.c | 24 + dix/getevents.c | 15 +- dix/grabs.c | 5 +- include/events.h | 1 + include/eventstr.h | 24 +- include/input.h | 6 + include/inputstr.h | 2 +- mi/mieq.c| 4 + mi/mipointer.c | 54 ++- mi/mipointer.h | 3 +- test/fixes.c | 26 ++ test/xi2/protocol-eventconvert.c | 216 + xfixes/cursor.c | 432 +- xfixes/xfixes.h | 17 +- 22 files changed, 1469 insertions(+), 465 deletions(-) create mode 100644 Xi/xibarriers.c create mode 100644 Xi/xibarriers.h pgpmhYAGYtqAB.pgp Description: PGP signature ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
[PATCH] glx/dri2: initialise api to avoid indirect rendering failing randomly
From: Dave Airlie airl...@redhat.com
Running glxinfo under indirect rendering would randomly fail against the
intel driver, as it would create a context with no attribs, and then the
api value would be passed to the driver uninitialised.
Signed-off-by: Dave Airlie airl...@redhat.com
---
glx/glxdri2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/glx/glxdri2.c b/glx/glxdri2.c
index bce1bfa..b26e501 100644
--- a/glx/glxdri2.c
+++ b/glx/glxdri2.c
@@ -514,7 +514,7 @@ create_driver_context(__GLXDRIcontext * context,
unsigned minor_ver;
uint32_t flags;
int reset;
-int api;
+int api = __DRI_API_OPENGL;
if (num_attribs != 0) {
if (!dri2_convert_glx_attribs(screen, num_attribs, attribs,
--
1.8.0.1
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
Re: [PATCH] glx/dri2: initialise api to avoid indirect rendering failing randomly
Dave Airlie airl...@gmail.com writes: From: Dave Airlie airl...@redhat.com Running glxinfo under indirect rendering would randomly fail against the intel driver, as it would create a context with no attribs, and then the api value would be passed to the driver uninitialised. Reviewed-by: Keith Packard kei...@keithp.com -- keith.pack...@intel.com pgp7T7aEkAdCB.pgp Description: PGP signature ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
Re: [PATCH v2] xauth: improve to handle FamilyWild necessary for GDM/XDMCP/SSH. #43425
On 10/19/12 02:27 AM, Dr. Tilmann Bubeck wrote: Alan, I would step up to be the maintainer for xauth if no one else is willing to do so. I haven't seen anyone else show any interest in xauth in the two months since you said that, so I guess you're it. Enjoy! If you don't already have a freedesktop.org account, you'll need one: http://www.freedesktop.org/wiki/AccountRequests And you'll probably want to read up on the X.Org Development practices: http://www.x.org/wiki/DeveloperStart (though not everything in that page is fully up to date) And for details on the Xauth mechanisms, see: http://cgit.freedesktop.org/xorg/lib/libXau/tree/README http://www.x.org/releases/X11R7.7/doc/man/man3/Xau.3.xhtml (For instance, note that first one describes FamilyWild as being originally intended solely for XDMCP communication, not for storing in .Xauthority files.) -- -Alan Coopersmith- alan.coopersm...@oracle.com Oracle Solaris Engineering - http://blogs.oracle.com/alanc ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
Re: [PATCH v2] xauth: improve to handle FamilyWild necessary for GDM/XDMCP/SSH. #43425
Alan, thanks for handing over maintainership for xauth. Yes, I will read the given documents and take care of it. Kind regards, Tilmann Bubeck On Mon, 17 Dec 2012 08:09:20 +0100, Alan Coopersmith alan.coopersm...@oracle.com wrote: On 10/19/12 02:27 AM, Dr. Tilmann Bubeck wrote: Alan, I would step up to be the maintainer for xauth if no one else is willing to do so. I haven't seen anyone else show any interest in xauth in the two months since you said that, so I guess you're it. Enjoy! If you don't already have a freedesktop.org account, you'll need one: http://www.freedesktop.org/wiki/AccountRequests And you'll probably want to read up on the X.Org Development practices: http://www.x.org/wiki/DeveloperStart (though not everything in that page is fully up to date) And for details on the Xauth mechanisms, see: http://cgit.freedesktop.org/xorg/lib/libXau/tree/README http://www.x.org/releases/X11R7.7/doc/man/man3/Xau.3.xhtml (For instance, note that first one describes FamilyWild as being originally intended solely for XDMCP communication, not for storing in .Xauthority files.) ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
