ubuntu: release notes updates for 15.01

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

1 files changed, 17 insertions, 27 deletions

diff --git a/ubuntu/boards/snapdragon/README.textile.in b/ubuntu/boards/snapdragon/README.textile.in
index 2341dc3..6e28e69 100644
--- a/ubuntu/boards/snapdragon/README.textile.in
+++ b/ubuntu/boards/snapdragon/README.textile.in
@@ -2,16 +2,14 @@ The Linaro Qualcomm Landing Team is pleased to announce the new release of the _
 
 h4. What's new in this release
 
-* This release is based on Linux kernel v3.18
-* Bluetooth support is enabled for IFC6410 using the mainline ar3k BT drivers and Bluez stack. File transfer, keyboard, mouse and PAN have been validated in this release.
-* The graphic stack is using Xorg 1.16 and has been updated to use Mesa master branch as of 12/10/2014
-* The serial device node name has been changed from ttyHSL to ttyMSM since Linux kernel 3.14
+* Support for CPU thermal sensors (sensors 7..10 are respectively for CPU0..CPU3)
+* Support for HDMI audio has been added (requires DSP proprietary firmware)
+* Support for Compulab Utilite2 board
+* The graphic stack has been updated to use Mesa master branch as of 01/05/2015
 * Bug fixed:
-** "cpufreq wrongly configured CLK in Linaro 3.17 integration branch":https://bugs.linaro.org/show_bug.cgi?id=998
-** "On IFC6410 CPUIDLE v14 driver patches do not work with latest trustzone firmware":https://bugs.linaro.org/show_bug.cgi?id=981
-** "Verify USB functionality without DRM_MSM on 3.18 tracking branch":https://bugs.linaro.org/show_bug.cgi?id=898
+** "AP8064 Boards bootup failure with new version of RPM firmware":https://bugs.linaro.org/show_bug.cgi?id=970
 
-This is the second release of a new series for the Linaro Linux release for Snapdragon 600 processor. Going forward, the Linaro member monthly builds for Snapdragon 600 processor will be providing a kernel based on the current Linux kernel ("www.kernel.org":https://www.kernel.org) available at the time of the release. The goals of the Linaro Linux releases for Snapdragon 600 processor are to align with the latest Linux Kernel, close the gaps in features provided and migrate from the existing 3.4 vendor kernel. One immediate consequence of this migration is that some regressions are expected. Current regressions include: lack of audio support, video hardware acceleration and support for running CPU beyond 1Ghz. Developers can continue to use the "Linaro Linux release 14.10 for Snapdragon 600 processor":http://releases.linaro.org/14.10/ubuntu/ifc6410/, which is based on Linux kernel v3.4 and Ubuntu 14.04 if needed.
+This is the third release of a new series for the Linaro Linux release for Snapdragon 600 processor. Going forward, the Linaro member monthly builds for Snapdragon 600 processor will be providing a kernel based on the current Linux kernel ("www.kernel.org":https://www.kernel.org) available at the time of the release. The goals of the Linaro Linux releases for Snapdragon 600 processor are to align with the latest Linux Kernel, close the gaps in features provided and migrate from the existing 3.4 vendor kernel. One immediate consequence of this migration is that some regressions are expected. Current regressions include: lack of audio support, video hardware acceleration and support for running CPU beyond 1Ghz. Developers can continue to use the "Linaro Linux release 14.10 for Snapdragon 600 processor":http://releases.linaro.org/14.10/ubuntu/ifc6410/, which is based on Linux kernel v3.4 and Ubuntu 14.04 if needed.
 
 h4. Features
 
@@ -25,10 +23,9 @@ The Linaro Linux version ##RELEASE## for the Snapdragon 600 supports the followi
 ** @gnome@ image that includes a minimal Gnome Shell environment GUI
 * All images have a pre-configured user called @linaro@, and the password for this user is set to @linaro@
 * The root file system can be installed on eMMC or any other external media such as USB, SD card, SATA.
-* Android Debug Bridge (adb) can be used to connect to the target
 * Support for the following Snapdragon 600 based boards:
 ** Inforce IFC6410 Rev P1 and A1
-** Compulab CM-QS600
+** Compulab Utilite2 (CM-QS600)
 * The following Snapdragon 600 features are supported:
 ** Quad Core Krait 300 CPU (up to 1GHz)
 ** Adreno 320 GPU, powered by @freedreno@ Mesa/Gallium GPU driver
@@ -38,15 +35,17 @@ The Linaro Linux version ##RELEASE## for the Snapdragon 600 supports the followi
 ** HDMI display
 ** UART, Ethernet, SD, eMMC, SATA
 ** USB2.0 (Mouse, Keyboard, Storage)
-** Wifi and Bluetooth using on-board QCA6234x, on IFC6410 only, not on Compulab QS600
+** Wifi using on-board QCA6234x
+** Bluetooth using on-board QCA6234x, on IFC6410 only, not on Compulab Utilite2
+** CPU thermal sensors
 
 h4. Information about the IFC6410 board
 
 For more information about Linaro Linux release for Snapdragon 600 processor and the Inforce IFC6410 board, please check the "Linaro wiki":https://wiki.linaro.org/Boards/IFC6410. This wiki page provides additional information on board setup and getting started with Ubuntu on the IFC6410 (e.g. customize the kernel, rebuild the images, ...).
 
-h4. Information about the Compulab CM-QS600 Board
+h4. Information about the Compulab Utilite2 Board
 
-For more information about Compulab QS600 board, please check "Compulab website":http://www.compulab.co.il/products/computer-on-modules/cm-qs600/.
+For more information about Compulab Utilite2 board, please check "Compulab website":http://www.compulab.co.il/utilite-computer/web/utilite2-overview.
 
 h4. Download the release binaries
 
@@ -60,7 +59,7 @@ You also need to download the proper boot partition, based on the actual board y
 
 bc. boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img.gz
 
-for the Compulab CM QS600, please download:
+for the Compulab Utilite2, please download:
 
 bc. boot-qcom-apq8064-cm-qs600-qcom-snapdragon-##VERSION##.img.gz
 
@@ -106,7 +105,7 @@ The final step until to complete the upgrade is to boot the new kernel. That req
 
 bc. sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
 
-or on Compulab QS 600:
+or on Compulab Utilite2:
 
 bc. sudo fastboot flash boot boot-qcom-apq8064-cm-qs600-qcom-snapdragon-##VERSION##.img
 
@@ -147,7 +146,6 @@ 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.
@@ -222,7 +220,6 @@ 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.
 
@@ -281,7 +278,7 @@ git: http://git.linaro.org/landing-teams/working/qualcomm/kernel.git
 tag: ubuntu-qcom-snapdragon-##RELEASE##
 defconfig: qcom_defconfig
 
-The kernel compresssed image (@zImage@) is located in the @boot@ image and partition and the kernel modules are installed in the root file system. It is possible for a user to rebuild the kernel and run a custom kernel image instead of the released kernel. You can build the kernel using any recent GCC release using the git tree, tag and defconfig mentioned above. This release only supports booting with device tree, as such both the device tree blobs need to be built as well. DTBs files need to be appended to the kernel image when the booltloader do not support device tree protocol, such as on the IFC6410 and the CM QS-600.
+The kernel compresssed image (@zImage@) is located in the @boot@ image and partition and the kernel modules are installed in the root file system. It is possible for a user to rebuild the kernel and run a custom kernel image instead of the released kernel. You can build the kernel using any recent GCC release using the git tree, tag and defconfig mentioned above. This release only supports booting with device tree, as such both the device tree blobs need to be built as well. DTBs files need to be appended to the kernel image when the booltloader do not support device tree protocol, such as on the IFC6410 and the Utilite2.
 
 To build the Linux kernel, you can use the following instructions:
 
@@ -293,7 +290,7 @@ export CROSS_COMPILE=<path to your GCC cross compiler>/arm-linux-gnueabi-
 make qcom_defconfig
 make -j4 zImage dtbs
 
-Since kernel v3.17 there is a change in the way the kernel is prepared to boot on IFC6410 and CM-QS600. the issue is that bootloaders on these boards use ATAGS to pass the memory information as we use CONFIG_ARM_ATAG_DTB_COMPAT config in kernel this option will extract the memory information from the ATAG list and store it at run time into the appended DTB. But the LK booloader in this case passes an *incorrect* memory address. The workaround for now is to prepend a binary blob before the kernel, and the responsibility of this binary blob is to fixup the wrong ATAGS. While this is definitely a workaround, and not a proper fix, this is the currently proposed and recommended workaround from people from the Linux MSM community.
+Since kernel v3.17 there is a change in the way the kernel is prepared to boot on IFC6410 and Utilite2. the issue is that bootloaders on these boards use ATAGS to pass the memory information as we use CONFIG_ARM_ATAG_DTB_COMPAT config in kernel this option will extract the memory information from the ATAG list and store it at run time into the appended DTB. But the LK booloader in this case passes an *incorrect* memory address. The workaround for now is to prepend a binary blob before the kernel, and the responsibility of this binary blob is to fixup the wrong ATAGS. While this is definitely a workaround, and not a proper fix, this is the currently proposed and recommended workaround from people from the Linux MSM community.
 
 This binary blob is available in the Linaro kernel tree, both in source and precompiled format. The files are @fixup.bin@ and @fixup.S@. You can refer to @fixup.txt@ for instructions on how to rebuilt the binary blob.
 
@@ -301,7 +298,7 @@ To prepare a kernel image one need to prepend @fixup.bin@ to @zImage@. And as di
 
 bc. cat fixup.bin arch/arm/boot/zImage arch/arm/boot/dts/qcom-apq8064-ifc6410.dtb  > zImage-dtb
 
-or, similarly, for CM QS-600:
+or, similarly, for Utilite2:
 
 bc. cat fixup.bin arch/arm/boot/zImage arch/arm/boot/dts/qcom-apq8064-cm-qs600.dtb  > zImage-dtb
 
@@ -344,16 +341,9 @@ The SD card or USB drive is now ready to be plugged and used on the target. For
 bc. abootimg -u boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -c "cmdline=console=ttyMSM0,115200n8 root=/dev/sda1 rootwait rw text"
 sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
 
-h4. Android Debug Bridge
-
-adb can be used to connect to the target, for example it can be used to reboot the board into fastboot mode once the boot partition has been flashed. For more information about how to configure adb on the target, please refer to the "Linaro wiki":https://wiki.linaro.org/Boards/IFC6410/LinaroUbuntu#How_to_install_setup_and_use_Android_ADB.
-
 h4. Known issues and limitations
 
 * The serial/uart driver does not support high speed transfer, and is limited to 115200 speed. Since UART is used between the on-boart Bluetooth devices and the SoC, this limits the bandwidth between Bluetooth device and the Snapdragon 600. Some use cases such as Bluetooth audio cannot work properly at such low speed. Some other use cases such as data transfer will work but slower than expected. Suppport for high speed UART is being implemented, and will be released in a future release.
-* 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.
-* Boards which are shipping with Android 4.4 bootloaders, seem to have an issue with recent Linux kernel. Until the solution is found, a workaround exists and consists in downgrading to version 4.2 rpm.mbn firmware from Bootloaders_4.2_880261_V1.0.zip from Inforce techweb site using the command: @fastboot flash rpm rpm.mbn@. When this issue occurs, the serial console will show traces about "display clocks which cannot be enabled properly". See "this email":http://lists.freedesktop.org/archives/freedreno/2014-November/000135.html for more information.
 * 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.
 * Few software codecs are installed by default; you might install additional codecs such as  @gstreamer1.0-plugins-bad@ or @gstreamer1.0-plugins-ugly@.
 * Once you have flashed the boot partition with a valid boot image, the board will automatically boot that image when powered on. To avoid automatically booting you can jumper the board as explained in this "page":http://mydragonboard.org/2013/forcing-ifc6410-into-fastboot/. If you cannot use this method and still needs to reboot into fastboot mode, you can erase the boot partition on a running target using the following command @sudo cat /dev/zero > /dev/mmcblk0p7@