This is NOT a legal contract; it is simply a mechanism used to specify
the details of an unusual dependency between two components that is not
allowed under the normal rules set forth in the interface taxonomy.]

	CONTRACT ALLOWING/REQUIRING SPECIAL ARRANGEMENTS FOR INTERFACES

0.  Number:
    [PSARC/2009/016-01]

1.  This contract is between
	a SUPPLIER of INTERFACES and
	a CONSUMER of those INTERFACES,

2.  The SUPPLIER (definer and/or implementor) is identified by the following:
    Product or Bundle:		Solaris 
    Consolidation:		ON
    Department or Group:	x64 Platform
    Bugster Product/Category/SubCategory:
				solaris/driver/acpi_drv
    Responsible Manager: 	Neal Pollack <neal.pollack@sun.com>

3.  The CONSUMER is identified by the following:
    Product or Bundle:		Solaris
    Consolidation:		X
    Department or Group:	X Server Group
    Bugster Product/Category/SubCategory:
				solaris/xserver/xorg-server
    Responsible Manager:	Frederick Thornborrow <fred.thornborrow@sun.com>

4.  The INTERFACES are:

    The supplier provides the following ACPI hotkey event with
    libsysevent interface:

    ACPI hotkey class:			
    "EC_acpiev"			contracted consolidation private
    ACPI hotkey sub class:			
    "ESC_acpiev_display_switch"	contracted consolidation private   display device switch  
    "ESC_acpiev_sleep"		contracted consolidation private   suspend to RAM
    "ESC_acpiev_screen_lock"	contracted consolidation private   screen lock

5.  The ARC controlling these INTERFACES is:
    PSARC

6.  The CASE describing (Exporting) these INTERFACES is:
    [PSARC/2009/016 ]

7.  The following SPECIAL ARRANGEMENTS are made which modify the rules
    imposed by the stability levels listed in section 4 above:
 
_N_ 7a. Although the stability level doesn't normally restrict it,
        SUPPLIER promises to only modify INTERFACES in an incompatible
	way as follows:

_N_ 7b. Although the stability level doesn't normally allow it, CONSUMER will
        expose INTERFACES to a PARTNER, which is external to Sun, namely:
		Name of Company:
		Name of Department or Group within Company:
		Responsible Manager:

_Y_ 7c. Although the stability level doesn't normally allow it, CONSUMER will
        import INTERFACES from a separate consolidation.

_Y_ 7d. If SUPPLIER decides to change (including replace or remove) any
	portion of the INTERFACES, SUPPLIER will notify CONSUMER of the
	proposed new version, no later than the application for ARC
	approval of the new version.
	If SUPPLIER and CONSUMER are contained in the same consolidation,
	they have the option of arranging for simultaneous conversion
	to the new interfaces.  If this is not possible, or if they are
	not in the same consolidation, then SUPPLIER will either make best
	effort to work with CONSUMER so that CONSUMER can detect which
	version of INTERFACES is being supplied, or else SUPPLIER will
	make best effort to supply both old and new versions of
	INTERFACES.
	If SUPPLIER cannot make both versions of INTERFACES available,
	and SUPPLIER and CONSUMER cannot devise a method whereby
	CONSUMER can detect which version of INTERFACES is being
	supplied, and the old version of CONSUMER will not run with the
	new version of SUPPLIER, then either the EOL process must be
	followed by SUPPLIER, or else a major release of SUPPLIER will
	be required, or the change will not be allowed.

8. If CONSUMER requires changes in INTERFACES, SUPPLIER will make
   best effort to accommodate such changes, which shall then be
   treated in accordance with paragraph 7 above.

9. Notwithstanding paragraphs 7 and 8, a change to any portion
   of the INTERFACES shall be regarded as a completely new set of
   INTERFACES which require both ARC approval and execution of
   a new contract.

10. SUPPLIER and CONSUMER agree that evolution of INTERFACES shall be
    handled as follows:

    Evolution of interfaces are generally limited to modification,
    addition or deletion of ACPI hotkey sub class strings, changes
    beyond that need approval from CONSUMER.

11. SUPPLIER and CONSUMER agree that INTERFACES will be supported as
    follows:

    SUPPLIER will notify CONSUMER immediately of any planned changes
    of ACPI hotkey sub class strings, including addition and deletion.

12. SUPPLIER and CONSUMER agree that INTERFACES will be documented as
    follows:

    See 4.

13. SUPPLIER and CONSUMER agree that changes to the INTERFACES will be
    tested as follows:

    Manual testing.

14. SUPPLIER and CONSUMER agree that this contract can be terminated as
    follows:

    By mutual agreement from SUPPLIER and CONSUMER.

15. This contract is not valid until "signed" via agreement from the
    SUPPLIER and CONSUMER, and approved by the ARC CASE referenced by
    this contract.  E-mail agreement to the contract should be archived
    in the mail archive of CASE; verbal agreement to the contract
    should be noted in the meeting minutes.  This contract remains
    valid until superseded or invalidated.

For SUPPLIER:	Neal.Pollack@Sun.COM  DATE: 04/08/2009
For CONSUMER:	Fred.Thornborrow@Sun.COM	Date: 04/08/2009
For ARC:			Date:

    A copy of this contract shall be deposited in the CASE directory as
    [LSARC/2009/191.0]

16. (Not to be filled in until superseded or invalidated.)
    This contract was superseded or invalidated by CASE:
    For ARC:			Date: