Re: [Xcb] [PATCH] Remove fieldref from sole list in GetIndicatorMap reply

2013-02-19 Thread Alan Coopersmith
On 02/19/13 12:47 PM, Peter Harris wrote: I was going to, but I can't locate the XKB protocol spec. There isn't one in xorg/proto/kbproto, and the specs in xorg/lib/libX11 appear to document the Xlib interface only, not the on-wire protocol. I see a specs directory in proto/kbproto when I

Re: [Xcb] [PATCH] Remove fieldref from sole list in GetIndicatorMap reply

2013-02-19 Thread Peter Harris
On 2013-02-19 15:51, Alan Coopersmith wrote: On 02/19/13 12:47 PM, Peter Harris wrote: I was going to, but I can't locate the XKB protocol spec. There isn't one in xorg/proto/kbproto, and the specs in xorg/lib/libX11 appear to document the Xlib interface only, not the on-wire protocol. I

[PATCH] Set nIndicators in XkbGetIndicatorMap

2013-02-19 Thread Peter Harris
Xlib doesn't use this value (it computes it from the reply length instead) which is why nobody has noticed yet. But the spec http://www.x.org/releases/X11R7.7/doc/kbproto/xkbproto.html says that it should be set. Signed-off-by: Peter Harris phar...@opentext.com --- xkb/xkb.c |1 + 1 files

Re: [PATCH xts] Remove pad adjustments from Xproto/GetImage/PutImage

2013-02-19 Thread Aaron Plattner
On 12/17/2012 12:38 PM, Peter Harris wrote: GetImage adjusts the length field incorrectly, and PutImage does not adjust the length field at all. Since the only stored images are those from GetImage, it makes more sense to remove the pad code entirely than to fix it. Signed-off-by: Peter Harris

Re: [Xcb] [PATCH] Remove fieldref from sole list in GetIndicatorMap reply

2013-02-19 Thread Peter Harris
Context for xorg-devel, since this thread started on the xcb list: The nIndicators field is never set in xkbGetIndicatorMapReply (nor does the Xlib half read it). http://cgit.freedesktop.org/xorg/proto/kbproto/tree/XKBproto.h#n487 On 2013-02-19 14:46, Bart Massey wrote: Seems to me that there's

Initial DRI3000 protocol specs available

2013-02-19 Thread Keith Packard
I've written down a preliminary description of the DRI3000 stuff and uploaded the two (yes, two) new extension specifications to git: http://keithp.com/blogs/DRI3000/ -- keith.pack...@intel.com pgpa5OQUv7Gej.pgp Description: PGP signature

Re: Initial DRI3000 protocol specs available

2013-02-19 Thread Keith Packard
Here's the spec for DRI3: The DRI3 Extension Version 1.0 2013-2-19 Keith Packard kei...@keithp.com Intel Corporation 1.

Re: Initial DRI3000 protocol specs available

2013-02-19 Thread Keith Packard
And here's the Swap extension The Swap Extension Version 1.0 2013-2-14 Keith Packard kei...@keithp.com Intel Corporation

[ANNOUNCE] xts 0.99.1

2013-02-19 Thread Aaron Plattner
This release re-enables all of the Xt* test scenarios, along with the ShapeEx scenario. It also fixes a few test bugs. Some tests are still expected to fail, which is why this is still version 0.99.* rather than 1.0. Results vs. xts-0.99.0 on Xvfb -screen 0 1050x1200x24 :1 CASES TESTS

[PATCH modular] release.sh: use Cc: rather than CC:

2013-02-19 Thread Aaron Plattner
git-send-email ignores CC headers, so using that to send announcements generated by release.sh fails to actually carbon copy the Cc'd list. Use Cc instead. Signed-off-by: Aaron Plattner aplatt...@nvidia.com --- release.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] os: use libunwind to generate backtraces

2013-02-19 Thread Marcin Slusarz
On Tue, Feb 19, 2013 at 09:41:35AM +1000, Peter Hutterer wrote: On Mon, Feb 18, 2013 at 10:40:13PM +0100, Marcin Slusarz wrote: On Mon, Feb 18, 2013 at 10:22:20PM +0100, Julien Cristau wrote: On Sat, Feb 16, 2013 at 16:45:54 +0100, Marcin Slusarz wrote: Libunwind generates backtraces