ubuntu: new release image, and document limatation on qs600ubuntu-qcom-snapdragon-14.11

Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>

2 files changed, 4 insertions, 1 deletions

diff --git a/ubuntu/boards/snapdragon/README.textile.in b/ubuntu/boards/snapdragon/README.textile.in
index 0e94e4e..b7ab8b7 100644
--- a/ubuntu/boards/snapdragon/README.textile.in
+++ b/ubuntu/boards/snapdragon/README.textile.in
@@ -104,6 +104,7 @@ bc. sudo fastboot flash cache firmware-qcom-snapdragon-##VERSION##.img
 sudo fastboot flash -S 768M userdata linaro-##UBUNTU_REL_NICK##-gnome-qcom-snapdragon-##VERSION##.img
 
 Note:
+* Warning: do not flash the @.img@ rootFS images on the Compulab QS-600 board, see "Known issues" section below
 * fastboot should be able to split large files automatically, but it does not work. As such, it is mandatory to add @-S 768M@, when flashing files larger than 768MB as a workaround.
 * the root file system must be flashed in the @userdata@ partition, and the boot image must be flashed in the @boot@ partition, otherwise the system will not boot.
 * the firmware image can be flashed in any partition larger than 64MB, it is recommended to use @cache@ partition, but not strictly required.
@@ -178,6 +179,7 @@ bc. sudo fastboot flash cache firmware-qcom-snapdragon-##VERSION##.img
 sudo fastboot flash -S 768M userdata linaro-##UBUNTU_REL_NICK##-developer-qcom-snapdragon-##VERSION##.img
 
 Note:
+* Warning: do not flash the @.img@ rootFS images on the Compulab QS-600 board, see "Known issues" section below
 * the root file system must be flashed in the @userdata@ partition, and the boot image must be flashed in the @boot@ partition, otherwise the system will not boot.
 * the firmware image can be flashed in any partition larger than 64MB, it is recommended to use @cache@ partition, but not strictly required.
 
@@ -269,6 +271,7 @@ adb can be used to connect to the target, for example it can be used to reboot t
 
 h4. Known issues and limitations
 
+* On Compulab QS-600, do not flash the released root filesystem images (gnome or developer) with fastboot into eMMC. The eMMC partition layout is different than on IFC6410, and userdata partition is too small, and you might end up with corruption, instead you can use the method to install the image on external storage (USB, SATA, SD card).
 * Audio is currently not supported in this release.
 * Some recent IFC6410 or Compulab QS-600 boards come with more recent bootloaders pre flashed (e.g. the bootloaders from Inforce Android Kit Kat release), and display clocks cannot be enabled properly. See "this email":http://lists.freedesktop.org/archives/freedreno/2014-November/000135.html for more information. The solution is to downgrade the bootloader, as explained in the email above.
 * In the Gnome login manager, 2 fallback sessions are proposed: using Metacity or Compiz. Compiz is not working, and there is no plan to fix that, as Compiz is obsolete. Metacity is working fine, and provides an alternative graphical interface that does not use GPU for composition.
diff --git a/vars.mk b/vars.mk
index f72a8ed..7eb6573 100644
--- a/vars.mk
+++ b/vars.mk
@@ -1,5 +1,5 @@
 export RELEASE:=14.11
-export VERSION:=20141124-54
+export VERSION:=20141126-56
 export UBUNTU_REL:=14.10
 export UBUNTU_REL_NICK:=utopic
 export INFORCE_VERSION:=Inforce IFC6410 Android BSP Rel v1.5