ubuntu: snapdragon: update release notes for 15.10ubuntu-qcom-snapdragon-15.10

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

2 files changed, 23 insertions, 23 deletions

diff --git a/ubuntu/boards/snapdragon/README.textile.in b/ubuntu/boards/snapdragon/README.textile.in
index d30c8ad..8a93f27 100644
--- a/ubuntu/boards/snapdragon/README.textile.in
+++ b/ubuntu/boards/snapdragon/README.textile.in
@@ -2,11 +2,8 @@ The Linaro Qualcomm Landing Team is pleased to announce the new release of the _
 
 h4. What's new in this release
 
-* Migrate to Linux kernel v4.2
-* Support for Krait running up to 1.7Ghz (full speed)
-* Support for high speed UART (up to 3 Mbps)
-* Support for Bluetooth audio (A2DP) on IFC6410
-* Initial support for X11/GLAMOR
+* Migrate to Linux kernel v4.2.4 (stable)
+* Add support for Inforce IFC6410PLUS SBC
 
 The current Linaro member monthly builds for Snapdragon 600 processor provides a kernel based on Linux kernel version ##KERNEL_VER##. The goals of the Linaro Linux releases for Snapdragon 600 processor are to align with the latest Linux Kernel ("www.kernel.org":https://www.kernel.org), close the gaps in features provided and migrate from the existing 3.4 vendor kernel. 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.
 
@@ -15,7 +12,7 @@ h4. Features
 The Linaro Linux version ##RELEASE## for the Snapdragon 600 supports the following features:
 
 * Provides a working Ubuntu environment with access to Ubuntu repositories (apt-get) and updates. It is based on Ubuntu ##UBUNTU_REL## (aka ##UBUNTU_REL_NICK##).
-* It is based on proprietary firmware from ##INFORCE_VERSION## for IFC6410 and ##EINFOCHIPS_VERSION## for ERAGON600.
+* It is based on proprietary firmware from ##INFORCE_VERSION## for IFC6410 (or IFC6410PLUS) and ##EINFOCHIPS_VERSION## for ERAGON600.
 * The following prebuilt images are released:
 ** @boot@ image that includes prebuilt kernel and initrd
 ** @developer@ image that includes Ubuntu core packages as well as typical development packages
@@ -24,6 +21,7 @@ The Linaro Linux version ##RELEASE## for the Snapdragon 600 supports the followi
 * The root file system can be installed on eMMC or any other external media such as USB, SD card, SATA.
 * Support for the following Snapdragon 600 based boards:
 ** Inforce IFC6410 Rev P1 and A1
+** Inforce IFC6410PLUS
 ** Compulab Utilite2 (CM-QS600)
 ** eInfochips ERAGON600 Development Board (based on ERAGON600 SOM)
 * The following Snapdragon 600 features are supported:
@@ -40,10 +38,12 @@ The Linaro Linux version ##RELEASE## for the Snapdragon 600 supports the followi
 ** Bluetooth using on-board QCA6234x
 ** CPU thermal sensors
 
-h4. Information about the IFC6410 board
+h4. Information about the IFC6410 and IFC6410PLUS boards
 
 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, ...).
 
+The IFC6410 is no longer available for purchase and has been replaced by the Inforce IFC6410PLUS. For more information about this board, please check this "website":http://www.inforcecomputing.com/products/single-board-computers/6410-plus-single-board-computer-sbc. The instructions in the release notes are the same for both the IFC6410 and the IFC6410PLUS.
+
 h4. Information about the Compulab Utilite2 Board
 
 For more information about Compulab Utilite2 board, please check "Compulab website":http://www.compulab.co.il/utilite-computer/web/utilite2-overview.
@@ -62,7 +62,7 @@ linaro-##UBUNTU_REL_NICK##-alip-qcom-snapdragon-##VERSION##.img.gz
 
 You also need to download the proper boot partition, based on the actual board you are using. 
 
-For the Inforce IFC6410, please download:
+For the Inforce IFC6410 or IFC6410PLUS, please download:
 
 bc. boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img.gz
 
@@ -113,7 +113,7 @@ On the board running the Linaro Linux release, you now need to install this debi
 bc. sudo dpkg -i linux-image-##KERNEL_VER##-linaro-qcom_##KERNEL_VER##-linaro-qcom-1_armhf.deb
 
 The final step until to complete the upgrade is to boot the new kernel. That requires to reboot the board into fastboot mode. You can use the standard instructions from next sections, which you have used when you installed the Linaro Linux release on your board. Of course you need to make sure to connect your board to the development host (USB for fastboot, UART for the serial console), and ensure that it is booted in fastboot mode, waiting for commands, then you can flash the images 
-on Inforce IFC6410 with:
+on Inforce IFC6410 (or IFC6410PLUS) with:
 
 bc. sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
 
@@ -129,12 +129,12 @@ Your system is now up-to-date, and you are running Linaro ##RELEASE## on your de
 
 h4. Managing the proprietary firmware
 
-To properly use this release, a set of proprietary firmware blobs must be acquired separately from respective board vendors. For IFC6410 firmware, use  "Inforce Techweb website":http://www.inforcecomputing.com/techweb/ and for eInfochips ERAGON600 firmware, use "eInfochips support centre":http://www.supportcenter.einfochips.com/ as Linaro is not redistributing them in this release.
+To properly use this release, a set of proprietary firmware blobs must be acquired separately from respective board vendors. For IFC6410 (or IFC6410PLUS) firmware, use  "Inforce Techweb website":http://www.inforcecomputing.com/techweb/ and for eInfochips ERAGON600 firmware, use "eInfochips support centre":http://www.supportcenter.einfochips.com/ as Linaro is not redistributing them in this release.
 These firmware blobs are needed for audio, power management, video and graphics support. While it is possible to boot the release without the firmware installed, it is not recommended, as various errors can occur.
 
 The Linaro release does not contain any proprietary software and thus provides an _empty_ firmware image. The provided firmware image is only a placeholder for users to install the firmware blobs downloaded from respective board vendor website. The empty firmware image can be flashed as per the instructions in the next sections; of course some functionality will not work without the proprietary firmware blobs. To install the firmware and get all the features of the release, you should extract the firmware from the respective BSP release, install them in the firmware image, and flash the updated firmware image as per the instructions in the next sections.
 
-h5. For Inforce IFC6410
+h5. For Inforce IFC6410 (or IFC6410PLUS)
 
 For bootloader, kernel and firmware, this release is based on _##INFORCE_VERSION##_, which you need to download from Inforce Techweb. The ZIP file @##INFORCE_FILE##@ includes all the proprietary firmware blobs required to use this Ubuntu-based Linaro build.
 
@@ -162,7 +162,7 @@ h4. Installing the LXDE based image
 
 Connect your board to the development host (USB for fastboot, UART for the serial console), and make sure that it is booted in fastboot mode, and waiting for commands, then you can flash the images:
 
-for Inforce IFC6410
+for Inforce IFC6410 (or IFC6410PLUS)
 
 bc. sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
 sudo fastboot flash cache firmware-qcom-snapdragon-##VERSION##.img
@@ -229,7 +229,7 @@ bc. systemctl start ligthdm
 
 The login manager window should appear within a few seconds, and you can log with the user @linaro@, using the password @linaro@. If you want to boot directly to the login manager, you can boot the image with different bootargs (e.g. remove the keyword @systemd.unit=multi-user.target@). 
 
-For Inforce IFC6410,  you can run the following command:
+For Inforce IFC6410 (or IFC6410PLUS),  you can run the following command:
 
 bc. sudo fastboot boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -c "console=ttyMSM0,115200n8 root=/dev/disk/by-partlabel/userdata rootwait rw"
 
@@ -239,7 +239,7 @@ bc. sudo fastboot boot boot-qcom-apq8064-eI_ERAGON600-qcom-snapdragon-##VERSION#
 
 Finally, if you want to make the bootargs change persistent, you can modify the released boot image and reflash it into the @boot@ partition:
 
-for Infoce IFC6410
+for Infoce IFC6410 (or IFC6410PLUS)
 
 bc. abootimg -u boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -c "cmdline=console=ttyMSM0,115200n8 root=/dev/disk/by-partlabel/userdata rootwait rw"
 sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
@@ -257,7 +257,7 @@ h4. Installing the Developer based image
 
 Connect the board to the development host (USB for fastboot, UART for the serial console), and make sure that it is booted in fastboot mode, and waiting for commands, then you can flash the images:
 
-for Inforce IFC6410
+for Inforce IFC6410 (or IFC6410PLUS)
 
 bc. sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
 sudo fastboot flash cache firmware-qcom-snapdragon-##VERSION##.img
@@ -334,7 +334,7 @@ bc. git: http://git.linaro.org/landing-teams/working/qualcomm/kernel.git
 tag: ubuntu-qcom-snapdragon-##RELEASE##
 defconfig: qcom_defconfig kernel/configs/distro.config
 
-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.
+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 (or IFC6410PLUS) and the Utilite2.
 
 Even though it is possible to build natively, on the target board, It is recommended to build the Linux kernel on a PC development host. In which case you need to install a cross compiler for the ARM architecture. It is recommended to download the "Linaro GCC cross compiler":##LINARO_GCC##.
 
@@ -350,7 +350,7 @@ make -j4 zImage dtbs
 
 The DTB file needs to be appended to the @zImage@, as such, you can run the following command to prepare an image 
 
-for the IFC6410:
+for the IFC6410 (or IFC6410PLUS):
 
 bc. cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-apq8064-ifc6410.dtb  > zImage-dtb
 
@@ -370,7 +370,7 @@ If you have followed these instructions, the root file system was flashed into t
 
 If you want to permanently use a custom kernel image, you can update the boot image and reflash it into the @boot@ partition, for example, 
 
-for IFC6410:
+for IFC6410 (or IFC6410PLUS):
 
 bc. abootimg -u boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -k zImage
 sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
@@ -405,7 +405,7 @@ It is very important to run the copy with admin privileges and with @-a@ in orde
 
 The SD card or USB drive is now ready to be plugged and used on the target. For USB drive it is recommended to use externally powered USB drive or through an externally powered USB HUB. When booting with the root file system on USB drive or SD card, the @boot@ partition from the eMMC is still being used for the kernel and initrd. As such you need to update the @boot@ image with the new bootargs, and reflash it. If using a USB or (m)SATA drive or SD card with a single partition, the device to boot from will be either @/dev/sda1@ for USB drive or @/dev/mmcblk1p1@ for SD card. For example, for USB drive, run:
 
-for Inforce IFC6410
+for Inforce IFC6410 (or IFC6410PLUS)
 
 bc. abootimg -u boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -c "cmdline=console=ttyMSM0,115200n8 root=/dev/sda1 rootwait rw systemd.unit=multi-user.target"
 sudo fastboot flash boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img
@@ -512,7 +512,7 @@ reboot
 
 * Some software codecs might not be installed by default; you might install additional codecs such as @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/ for IFC6410. To boot the ERAGON600 board in fastboot mode, please refer @section 7.4.2 Fastboot mode@ on @Software Reference Manual@ at "eInfochips support centre":http://www.supportcenter.einfochips.com/. 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/disk/by-partlabel/boot@
+* 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/ for IFC6410 (or IFC6410PLUS). To boot the ERAGON600 board in fastboot mode, please refer @section 7.4.2 Fastboot mode@ on @Software Reference Manual@ at "eInfochips support centre":http://www.supportcenter.einfochips.com/. 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/disk/by-partlabel/boot@
 
 h4. Feedback and Support
 
diff --git a/ubuntu/boards/snapdragon/README.textile.vars b/ubuntu/boards/snapdragon/README.textile.vars
index 6f5baef..33ea146 100644
--- a/ubuntu/boards/snapdragon/README.textile.vars
+++ b/ubuntu/boards/snapdragon/README.textile.vars
@@ -1,7 +1,7 @@
-export RELEASE="15.09"
-export VERSION="20150916-129"
+export RELEASE="15.10"
+export VERSION="20151026-139"
 export UBUNTU_REL="15.04"
-export KERNEL_VER="4.2.0"
+export KERNEL_VER="4.2.4"
 export UBUNTU_REL_NICK="vivid"
 export INFORCE_VERSION="Inforce IFC6410 Android BSP Rel v1.5"
 export INFORCE_FILE="Inforce-IFC6410_AndroidBSP_880160_Rel_Beta_V1.5.zip"