Oops, I forgot to send this on to the xwin-discuss list too.
This is step #1 in integrating Xorg server 1.3. The randr 1.2
case will be next.
-alan-
-------- Original Message --------
Subject: X Damage Extension Version 1.1 [LSARC/2007/421 Self Review]
Date: Thu, 19 Jul 2007 13:57:21 -0700 (PDT)
From: Alan Coopersmith <[email protected]>
I am sponsoring this case for myself and closing it as approved automatic
as it simply tracks the community addition of a new function & protocol
request to the existing Damage extension to the X protocol.
This case requests a Micro/Patch binding.
[Since LSARC-EXT does not yet exist, but this is an open case, I will be
sending seperate copies to LSARC & opensolaris-arc.]
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
-------------------------------------------------------------------------------
Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI
This information is Copyright 2007 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
X Damage Extension Version 1.1
1.2. Name of Document Author/Supplier:
Author: Alan Coopersmith
1.3 Date of This Document:
19 July, 2007
4. Technical Description
This case updates the definition of the X Damage protcol used in Solaris
from version 1.0 to version 1.1 of the spec from the X.Org Foundation.
It additionally updates the libXdamage client API from version 1.0 to
version 1.1.
Support for version 1.1 in the Xorg server will be handled by the Xorg
server 1.3 case coming to PSARC soon.
The added request to the protocol is described in this section of the
protocol spec [1]:
3.1 Additions in the 1.1 version of the protocol
Damage is automatically computed by the X Server for X rendering
operations, but direct rendering extensions have allowed clients to
perform rendering outside of the control of the X Server. The 1.1
version of the protocol added a request to allow direct rendering
clients to report damage to a drawable. Some direct rendering
clients, due to architectural limitations, always perform rendering
to the root window, even in when it should be performed to the
backing pixmap in the Composite case. To provide less-incorrect
rendering in this cases, the direct rendering client should
translate its damage region to screen coordinates and report the
damage against the root window rather than the drawable.
The new function in the API is simply a C binding to this new protocol
request:
void XDamageAdd (Display *dpy, Drawable drawable, XserverRegion region);
Imported Interfaces:
--------------------
libXdamage.so.1 External LSARC 2003/506
<X11/extensions/Xdamage.h> External LSARC 2003/506
Damage extension protocol version 1.0 External LSARC 2003/506
Exported Interfaces:
--------------------
Damage extension protocol version 1.1 Volatile [1]
XDamageAdd() in libXdamage.so Volatile
References in case materials directory:
[1] damageproto.txt: The DAMAGE Extension, Protocol Version 1.1, 2007-01-08
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
X Consolidation (Desktop C-Team)
6.5. ARC review type: Automatic
6.6. ARC Exposure: open
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
