On Thu, 2014-05-01 at 15:39 +0300, Alexey Brodkin wrote:
Xorg server could be built for and run on Synopsys DesignWare ARC cores.
These changes are required for successful building and execution of the
server.
Both little-endian and big-endian flavors of ARC cores are supported.
This patch fixes some compile warnings that arise after
commit 7070ebeebaca1b51f8a2801989120784a1c374ae
(xfree86: add new key MatchSeat to xorg.conf sections Device, Screen, and
ServerLayout)
available at git repository
git://people.freedesktop.org/~whot/xserver for-keith
---
Patch sent:
http://lists.x.org/archives/xorg-devel/2014-May/042386.html
CANTATE DOMINO CANTICUM NOVUM
QUIA MIRABILIA FECIT
Laércio
2014-05-09 0:31 GMT-03:00 Keith Packard kei...@keithp.com:
Laércio de Sousa lbsous...@gmail.com writes:
These warnings are all related to a malformed
On Thu, Oct 31, 2013 at 03:43:41PM -0700, Keith Packard wrote:
+static void
+miSyncShmFenceSetTriggered(SyncFence * pFence)
+{
+SyncShmFencePrivatePtr pPriv = SYNC_FENCE_PRIV(pFence);
+
+if (pPriv-fence)
+xshmfence_trigger(pPriv-fence);
+
Le 11/04/2014 16:57, Hans de Goede a écrit :
Signed-off-by: Hans de Goede hdego...@redhat.com
Hi Hans,
I never received this patch although I was the main recipient :s That
concerns me greatly because it means I have no email address immune to
dropping emails...
Anyway, I heard about it
Le 09/05/2014 15:02, Hans de Goede a écrit :
Hi,
On 05/09/2014 02:46 PM, Martin Peres wrote:
Le 11/04/2014 16:57, Hans de Goede a écrit :
Signed-off-by: Hans de Goede hdego...@redhat.com
Hi Hans,
I never received this patch although I was the main recipient :s That concerns
me greatly
From: Owen W. Taylor otay...@fishsoup.net
When XCB owns the X socket, dpy-request is not updated, so
NextRequest() and XNextRequest() return the wrong value. There's
nothing we can do to fix NextRequest() while retaining ABI compat,
but change XNextRequest() to grab the socket back from XCB,
On 09.05.2014 22:33, otay...@redhat.com wrote:
From: Owen W. Taylor otay...@fishsoup.net
When XCB owns the X socket, dpy-request is not updated, so
NextRequest() and XNextRequest() return the wrong value. There's
nothing we can do to fix NextRequest() while retaining ABI compat,
but change
From: Owen W. Taylor otay...@fishsoup.net
When XCB owns the X socket, dpy-request is not updated, so
NextRequest() and XNextRequest() return the wrong value. There's
nothing we can do to fix NextRequest() while retaining ABI compat,
but change XNextRequest() to grab the socket back from XCB,
Uli Schlachter wrote:
unsigned long XNextRequest(Display *dpy)
{
+unsigned long next_request;
+LockDisplay(dpy);
+next_request = _XNextRequest(dpy);
+UnlockDisplay(dpy);
+
return (NextRequest(dpy));
Unused variable next_request. Did you really mean to
10 matches
Mail list logo