snapdragon: updates for 15.07 release

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

2 files changed, 49 insertions, 51 deletions

diff --git a/ubuntu/boards/snapdragon/README.textile.in b/ubuntu/boards/snapdragon/README.textile.in
index 4178ed2..e03f70b 100644
--- a/ubuntu/boards/snapdragon/README.textile.in
+++ b/ubuntu/boards/snapdragon/README.textile.in
@@ -1,9 +1,12 @@
-The Linaro Qualcomm Landing Team is pleased to announce the new release of the _Linaro Linux release for Qualcomm(tm) Snapdragon(R) 600 processor_. The Linaro Linux release ##RELEASE## is an Ubuntu-based Linaro Member Build that provides developers with a _desktop like_ environment using Ubuntu and the Gnome desktop, as well as a console-only image.
+The Linaro Qualcomm Landing Team is pleased to announce the new release of the _Linaro Linux release for Qualcomm(tm) Snapdragon(R) 600 processor_. The Linaro Linux release ##RELEASE## is an Ubuntu-based Linaro Member Build that provides developers with a _desktop like_ environment using Ubuntu and the LXDE desktop, as well as a console-only image.
 
 h4. What's new in this release
 
-* Added support for eInfochips ERAGON600 Development board (based on ERAGON600 SOM). This will be available for purchase from eInfochips (pre order "here":http://einfochips.viewpage.co/pre-order-now-eragon600-qualcomm). For features and release note please refer to "eInfochips Release Note":http://www.supportcenter.einfochips.com/ERAGON600_Ubuntu_Linux_ReleaseNote.pdf (coming soon).
-* Added Bluetooth support for Compulab CM-QS600
+* Migrate to Ubuntu 15.04 (aka vivid)
+* Use systemd for init instead of upstart
+* Use LXDE as default desktop instead of Gnome
+* Upgrade to Mesa 10.6.2
+* Migrate kernel distro configuration to "distro.config file":https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/blob/ce5c75ed2a5bf6530ce5c0bcd6b38e5cd3affcd4:/kernel/configs/distro.config
 
 The current Linaro member monthly builds for Snapdragon 600 processor provides 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. 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.
 
@@ -16,7 +19,7 @@ The Linaro Linux version ##RELEASE## for the Snapdragon 600 supports the followi
 * 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
-** @gnome@ image that includes a minimal Gnome Shell environment GUI
+** @alip@ image that includes a desktop based on LXDE
 * 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.
 * Support for the following Snapdragon 600 based boards:
@@ -54,7 +57,7 @@ To install this release on a Snapdragon 600 based board, you need to download th
 
 bc. firmware-qcom-snapdragon-##VERSION##.img.gz
 linaro-##UBUNTU_REL_NICK##-developer-qcom-snapdragon-##VERSION##.img.gz
-linaro-##UBUNTU_REL_NICK##-gnome-qcom-snapdragon-##VERSION##.img.gz
+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. 
 
@@ -154,7 +157,7 @@ bc. gunzip  firmware-eragon600-v1.0.img.gz
 
 The firmware image @firmware-eragon600-v1.0.img@ contains all the relevant proprietary firmware blobs.
 
-h4. Installing the Gnome based image
+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:
 
@@ -175,16 +178,16 @@ sudo fastboot flash cache firmware-eragon600-v1.0.img
 
 then:
 
-bc. sudo fastboot flash -S 768M userdata linaro-##UBUNTU_REL_NICK##-gnome-qcom-snapdragon-##VERSION##.img
+bc. sudo fastboot flash -S 768M userdata linaro-##UBUNTU_REL_NICK##-alip-qcom-snapdragon-##VERSION##.img
 
 Note:
 * 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.
 
-Flashing the Gnome image takes several minutes. Be patient. You should see the following fastboot traces on the PC while flashing the image:
+Flashing the LXDE image takes several minutes. Be patient. You should see the following fastboot traces on the PC while flashing the image:
 
-bc. sudo fastboot flash -S 768M userdata linaro-##UBUNTU_REL_NICK##-gnome-qcom-snapdragon-##VERSION##.img
+bc. sudo fastboot flash -S 768M userdata linaro-##UBUNTU_REL_NICK##-alip-qcom-snapdragon-##VERSION##.img
 sending sparse 'userdata' (785202 KB)...
 OKAY [ 55.368s]
 writing 'userdata'...
@@ -207,11 +210,11 @@ bc. [34320] fastboot: getvar:partition-type:userdata
 
 Do not power off the PC, or the board while flashing.
 
-h4. Running the Gnome based image
+h4. Running the LXDE based image
 
-The Gnome based image is expected to provide a _desktop-like_ experience, as such it is recommended to use an HDMI monitor, as well as USB keyboard and mouse.
+The LXDE based image is expected to provide a _desktop-like_ experience, as such it is recommended to use an HDMI monitor, as well as USB keyboard and mouse.
 
-The default bootargs embedded in the released boot image will intentionally prevent the graphical login manager (GDM) to start, since trying to start graphical environment without the proprietary firmware installed will lead to various boot errors. To prevent GDM to start, the keyword @text@ was added into the bootargs. If you have properly installed and flashed into eMMC the proprietary firmware blobs and want to use the graphical interface, you can either start the login manager from the serial console, or alternatively you can change the bootargs.
+The default bootargs embedded in the released boot image will intentionally prevent the graphical login manager (lightdm) to start, since trying to start graphical environment without the proprietary firmware installed will lead to various boot errors. To prevent lightdm from starting, the keyword @systemd.unit=multi-user.target@ was added into the bootargs. If you have properly installed and flashed into eMMC the proprietary firmware blobs and want to use the graphical interface, you can either start the login manager from the serial console, or alternatively you can change the bootargs.
 
 To boot to the serial console and get a root prompt, you can simply run:
 
@@ -221,9 +224,9 @@ Note: The default bootargs enable the kernel messages to be displayed on the ser
 
 Once you have a root prompt on the serial console, you have a functional Ubuntu system. If you want to start the login manager to see the graphical interface on the HDMI monitor, from the serial console simply run
 
-bc. start gdm
+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 @text@). 
+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:
 
@@ -290,7 +293,7 @@ h4. Configuring and using Bluetooth and WLAN
 
 Firmware are required for Bluetooth and WLAN to work properly. If you have followed the instructions so far, the firmware have been installed. For both WLAN and Bluetooth appropriate mainline drivers are used, respectively ath6kl and ar3k.
 
-WLAN should be up and running out of the box, using the releases images. If you are building your own kernel, please be aware that the WLAN driver and some mac802.11 drivers are compiled as modules, and need to be deployed into the root file system. WLAN can be configured either on the command line, or using the graphical Gnome applet once the desktop is started.
+WLAN should be up and running out of the box, using the releases images. If you are building your own kernel, please be aware that the WLAN driver and some mac802.11 drivers are compiled as modules, and need to be deployed into the root file system. WLAN can be configured either on the command line, or using the graphical desktop applet once the desktop is started.
 
 For Bluetooth, it is for now not enabled by default in the image, and you need to run the following command on the root prompt to properly start and configure the Bluetooth chip:
 
@@ -315,27 +318,20 @@ bc. hcitool scan
 Scanning ...
         BC:5F:BC:44:FB:AC       Nexus 5
 
-If you configure the Bluetooth chip before starting the graphical desktop (e.g. Gnome), then you should be able to use the Gnome Bluetooth applet to connect to any device and use Bluetooth functions.
+If you configure the Bluetooth chip before starting the graphical desktop, then you should be able to use the Desktop Bluetooth application/applet to connect to any device and use Bluetooth functions.
 
 Note that if you are using the developer image you might need to install the Bluez applications and librairies:
 
 bc. sudo apt-get update
 sudo apt-get install bluez
 
-If you are using the Gnome image, and connect a Bluetooth headset (audio), you will need to install the following packages for pulseaudio to work with your headset:
-
-bc. sudo apt-get update
-sudo apt-get install pulseaudio-module-bluetooth
-
-In the Gnome sounds settings application, the Bluetooth headeset will show up, make sure to choose AD2P profile, since the HFP profile is not supported at the moment.
-
 h4. How to get and customize the kernel source code
 
 The Linux kernel used in this release is available via tags in the "Linaro Qualcomm Landing Team git repository":https://git.linaro.org/landing-teams/working/qualcomm/kernel.git:
 
 bc. git: http://git.linaro.org/landing-teams/working/qualcomm/kernel.git
 tag: ubuntu-qcom-snapdragon-##RELEASE##
-defconfig: qcom_defconfig
+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.
 
@@ -348,7 +344,7 @@ cd kernel
 git checkout -b kernel-##RELEASE## ubuntu-qcom-snapdragon-##RELEASE##
 export ARCH=arm
 export CROSS_COMPILE=<path to your GCC cross compiler>/arm-linux-gnueabihf-
-make qcom_defconfig
+make qcom_defconfig distro.config
 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 
@@ -393,9 +389,9 @@ h4. How to install the root filesystem on external storage
 
 The root file system can be installed on SD card, external USB drive or external (m)SATA drive instead of being flashed to the eMMC. The method is to extract the content of the root file system image from the release, and copy it onto a proper partition on an SD card or USB drive, then boot the target platform with the proper @root=@ argument in the bootargs.  The root file system image file is using an Android sparse image format to optimize the file size. To convert a sparse image into a mountable _raw_ image file, and mount it on your host, run:
 
-bc. simg2img linaro-##UBUNTU_REL_NICK##-gnome-qcom-snapdragon-##VERSION##.img linaro-##UBUNTU_REL_NICK##-gnome-qcom-snapdragon-##VERSION##.img.raw
+bc. simg2img linaro-##UBUNTU_REL_NICK##-alip-qcom-snapdragon-##VERSION##.img linaro-##UBUNTU_REL_NICK##-alip-qcom-snapdragon-##VERSION##.img.raw
 mkdir rootfs
-sudo mount -o loop linaro-##UBUNTU_REL_NICK##-gnome-qcom-snapdragon-##VERSION##.img.raw rootfs
+sudo mount -o loop linaro-##UBUNTU_REL_NICK##-alip-qcom-snapdragon-##VERSION##.img.raw rootfs
 
 Note that @simg2img@ is available in most standard Linux distribution; simply install the package using your Linux distribution methods. If you are using Ubuntu on your PC, simply run @sudo apt-get install android-tools-fsutils@. Assuming the SD card or USB drive that should contain the root file system is properly formatted as ext4 partition and mounted on your host as @/mnt/disk@, you can copy the content of the image with:
 
@@ -427,7 +423,11 @@ This plugin can decode MPEG4 and H264 videos, and it generates raw video using a
 In order to install all the required Gstreamer dependencies on your board, please run the following commands:
 
 bc. sudo apt-get update
-sudo apt-get install gstreamer1.0-tools gstreamer1.0-plugins-ugly gstreamer1.0-plugins-bad gstreamer1.0-plugin-qcvideo
+sudo apt-get install gstreamer1.0-tools gstreamer1.0-plugins-ugly gstreamer1.0-plugins-bad
+
+If you are running the developer image, you need to install the following additional packages:
+
+bc. sudo apt-get install xserver-xorg xserver-xorg-video-freedreno gstreamer1.0-plugins-good
 
 Also, to use video acceleration, a specific kernel must be used for now. Hence you need to download, install and boot the kernel from the Linaro 14.10 release:
 
@@ -447,17 +447,25 @@ Finally, you need to reboot the board, and boot with the Linaro 14.10 kernel, yo
 
 bc. sudo fastboot boot boot-ifc6410-20141024-37.img
 
+You now need to rebuild the plugin from source, you can fetch the source code, and rebuild on your board directly:
+
+bc. sudo apt-get install build-essential git autotools-dev autoconf libtool libdrm-dev libgstreamer-plugins-base1.0-dev
+git clone http://git.linaro.org/landing-teams/working/qualcomm/gst-plugin-qcvideo.git
+cd gst-plugin-qcvideo/
+./autogen.sh
+make
+sudo make install
+
 Once the plugin is installed and the board booted with the 3.4 kernel from Linaro 14.10, you can use the plugin:
 
 bc. export DISPLAY=:0
+export GST_PLUGIN_PATH=/usr/local/lib/gstreamer-1.0/
 X&
-metacity&
-pulseaudio &
 gst-launch-1.0 playbin uri=http://mirrorblender.top-ix.org/peach/bigbuckbunny_movies/big_buck_bunny_720p_surround.avi
 
 Note that depending on your network bandwidth, it is probably better to download the video file and play it locally.
 
-If you are running the Gnome image, you can also login into Gnome shell with the @linaro@ user, and from the terminal console, you can run:
+If you are running the desktop image, you can also login with the @linaro@ user, and from the terminal console, you can run:
 
 bc. gst-launch-1.0 playbin uri=http://mirrorblender.top-ix.org/peach/bigbuckbunny_movies/big_buck_bunny_720p_surround.avi
 
@@ -472,29 +480,19 @@ bc. gst-launch-1.0 videotestsrc ! video/x-raw,format=NV12_64Z32,width=1280,heigh
 
 Firefox is using Gstreamer as its main media framework, as a consequence, if you try to open a web page with HTML video, such as Video.js:"http://www.videojs.com/", then the video will be decoded using hardware acceleration. If @GST_DEBUG@ is set before you start Firefox, you will be able to see the plugin debug messages in the terminal.
 
-Note that if you want to rebuild the plugin from source, you can fetch the source code, and rebuild on your board directly:
-
-bc. sudo apt-get install build-essential git autotools-dev autoconf libtool libgstreamer-plugins-base1.0-dev
-git clone http://git.linaro.org/landing-teams/working/qualcomm/gst-plugin-qcvideo.git
-cd gst-plugin-qcvideo/
-./autogen.sh
-make
-sudo make install
-
 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.
-* 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@.
+* 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@
-* The developer image does not include the the Linaro Qualcomm overlay by default, unlike the Gnome image. If you need to install packages overlaid by Linaro, once you have booted the developer image, you need to create the file @/etc/apt/sources.list.d/linaro-maintainers-qcom-##UBUNTU_REL_NICK##.list@ with the following content:
-
-bc. deb http://ppa.launchpad.net/linaro-maintainers/qcom-overlay/ubuntu ##UBUNTU_REL_NICK## main
-deb-src http://ppa.launchpad.net/linaro-maintainers/qcom-overlay/ubuntu ##UBUNTU_REL_NICK## main
 
 h4. Feedback and Support
 
-For general question or support request, please go to "mydragonboard.org":http://mydragonboard.org/community/hw-sw-8064/ Community.
+For general question or support request, please use:
+* "Inforce Techweb":http://inforcecomputing.com/techweb/ or "Inforce Forums":http://forums.inforcecomputing.com/
+* "Compulab Developer Resources":http://www.compulab.co.il/support/developer-resources/
+* Linaro IRC: #linaro on irc.freenode.net
+* "Linaro mailing list":https://lists.linaro.org/mailman/listinfo/linaro-dev
 
 For any bug related to the Linaro Member Build, please submit issues to the "Linaro bug tracking system":https://bugs.linaro.org/. To submit a bug, select "File a Bug", then Product: "Qualcomm LT", or simply follow this "link":https://bugs.linaro.org/enter_bug.cgi?product=Qualcomm%20LT.
 
diff --git a/ubuntu/boards/snapdragon/README.textile.vars b/ubuntu/boards/snapdragon/README.textile.vars
index 4035040..4a49e92 100644
--- a/ubuntu/boards/snapdragon/README.textile.vars
+++ b/ubuntu/boards/snapdragon/README.textile.vars
@@ -1,8 +1,8 @@
-export RELEASE="15.04"
-export VERSION="20150417-100"
-export UBUNTU_REL="14.10"
+export RELEASE="15.07"
+export VERSION="20150724-117"
+export UBUNTU_REL="15.04"
 export KERNEL_VER="3.19.0"
-export UBUNTU_REL_NICK="utopic"
+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"
 export INFORCE_STRIP="--strip-components 8 proprietary/prebuilt/target/product/msm8960/system/etc/firmware/"