Add first draft of conformance submission package description

Change-Id: If6581ee5ae7b497f5f7cec7bce0e42598860a5bc
diff --git a/external/vulkancts/README.md b/external/vulkancts/README.md
index a9260f9..9ddad79 100644
--- a/external/vulkancts/README.md
+++ b/external/vulkancts/README.md
@@ -97,6 +97,20 @@
 	$ python <vulkancts>/external/vulkancts/build_mustpass.py
 
 
+Pre-compiling SPIR-V binaries
+-----------------------------
+
+For distribution, and platforms that don't support GLSL to SPIR-V compilation,
+SPIR-V binaries must be pre-built with following command:
+
+	$ python external/vulkancts/build_spirv_binaries.py
+
+Binaries will be written to external/vulkancts/data/vulkan/prebuilt/.
+
+Test modules (or in case of Android, the APK) must be re-built after building
+SPIR-V programs in order for the binaries to be available.
+
+
 Running CTS
 -----------
 
@@ -144,18 +158,46 @@
 Test log will be written into /sdcard/TestResults.qpa
 
 
-Pre-compiling SPIR-V binaries
------------------------------
+Conformance Submission Package Requirements
+-------------------------------------------
 
-For distribution, and platforms that don't support GLSL to SPIR-V compilation,
-SPIR-V binaries must be pre-built with following command:
+Conformance submission package must contain following:
 
-	$ python external/vulkancts/build_spirv_binaries.py
+1) Full test logs (TestResults.qpa) from CTS runs against all driver builds
+2) Result of "git status" and "git log" from CTS source directory
+3) Any patches used on top of release tag
+4) Conformance statement
 
-Binaries will be written to external/vulkancts/data/vulkan/prebuilt/.
+Test logs (1) should be named TestResults-<driver build type>.qpa, for example
+TestResults-armeabi-v7a.qpa. On platforms where multiple different driver
+builds (for example 64-bit and 32-bit) are present, CTS must be ran against
+all of them.
 
-Test modules (or in case of Android, the APK) must be re-built after building
-SPIR-V programs in order for the binaries to be available.
+CTS build must always be done from clean git repository that doesn't have any
+uncommitted changes. Thus it is necessary to run and capture output of "git
+status" and "git log" (2) in the source directory:
+
+	git status > <submission pkg dir>/git-status.txt
+	git log <release tag>..HEAD > <submission pkg dir>/git-log.txt
+
+Any changes made to CTS must be committed to the repository, and provided
+as part of the submission package (3). This can be done by running:
+
+	git format-patch -o <submission pkg dir> <release tag>..HEAD
+
+In general bugfixes and changes to platform-specific code (mostly under
+framework/platform) are allowed.
+
+Conformance statement (4) must be included in a file called STATEMENT-<adopter>
+and must contain following:
+
+	CONFORM_VERSION:         <git tag of CTS release>
+	PRODUCT:                 <string-value>
+	CPU:                     <string-value>
+	OS:                      <string-value>
+
+Note that product/cpu/os information is also captured in dEQP-VK.info.* tests
+if vk::Platform::describePlatform() is implemented.
 
 
 Vulkan platform port