summaryrefslogtreecommitdiff
path: root/ubuntu
diff options
context:
space:
mode:
authorNicolas Dechesne <nicolas.dechesne@linaro.org>2015-01-05 11:03:39 +0100
committerNicolas Dechesne <nicolas.dechesne@linaro.org>2015-01-05 11:03:39 +0100
commit73a274e87dcda3fa8faaa23c1201bf4608f65082 (patch)
treea31797d53fffe84e98664875bdcd0df08c255a6c /ubuntu
parent4e4a82848186d4f2ac860f0b5c418c071c1e91b1 (diff)
ubuntu: add better description for the RPM downgrade workaround
as per suggestion on mydragonboard forum, see: http://mydragonboard.org/community/hw-sw-8064/ifc6410-starting-gdm-without-serial-cableconsole-with-linaro-14-12/#p2994 Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Diffstat (limited to 'ubuntu')
-rw-r--r--ubuntu/boards/snapdragon/README.textile.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/ubuntu/boards/snapdragon/README.textile.in b/ubuntu/boards/snapdragon/README.textile.in
index b0bbdf4..2341dc3 100644
--- a/ubuntu/boards/snapdragon/README.textile.in
+++ b/ubuntu/boards/snapdragon/README.textile.in
@@ -353,7 +353,7 @@ 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.
-* 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.
+* 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@