summaryrefslogtreecommitdiff
path: root/ubuntu
diff options
context:
space:
mode:
authorNicolas Dechesne <nicolas.dechesne@linaro.org>2015-04-27 11:54:22 +0200
committerNicolas Dechesne <nicolas.dechesne@linaro.org>2015-04-27 12:09:03 +0200
commitd5f9ab4c741347d25a92138bd276caa7e137c8cc (patch)
tree1ef6da61c57b20ad4fe75e72896c205897893d6f /ubuntu
parentace19b5607654173c154fcff6474bec90a46ddf9 (diff)
ubuntu: do not hardcode mmc partition ids.
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Diffstat (limited to 'ubuntu')
-rw-r--r--ubuntu/boards/snapdragon/README.textile.in14
1 files changed, 7 insertions, 7 deletions
diff --git a/ubuntu/boards/snapdragon/README.textile.in b/ubuntu/boards/snapdragon/README.textile.in
index 1598f7d..64947e6 100644
--- a/ubuntu/boards/snapdragon/README.textile.in
+++ b/ubuntu/boards/snapdragon/README.textile.in
@@ -230,22 +230,22 @@ The login manager window should appear within a few seconds, and you can log wit
For Inforce IFC6410, you can run the following command:
-bc. sudo fastboot boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -c "console=ttyMSM0,115200n8 root=/dev/mmcblk0p13 rootwait rw"
+bc. sudo fastboot boot boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -c "console=ttyMSM0,115200n8 root=/dev/disk/by-partlabel/userdata rootwait rw"
For eInfochips ERAGON600, you can run the following command:
-bc. sudo fastboot boot boot-qcom-apq8064-eI_ERAGON600-qcom-snapdragon-##VERSION##.img -c "console=ttyMSM0,115200n8 root=/dev/mmcblk0p13 rootwait rw"
+bc. sudo fastboot boot boot-qcom-apq8064-eI_ERAGON600-qcom-snapdragon-##VERSION##.img -c "console=ttyMSM0,115200n8 root=/dev/disk/by-partlabel/userdata rootwait rw"
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
-bc. abootimg -u boot-qcom-apq8064-ifc6410-qcom-snapdragon-##VERSION##.img -c "cmdline=console=ttyMSM0,115200n8 root=/dev/mmcblk0p13 rootwait rw"
+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
for eInfochips ERAGON600
-bc. abootimg -u boot-qcom-apq8064-eI_ERAGON600-qcom-snapdragon-##VERSION##.img -c "cmdline=console=ttyMSM0,115200n8 root=/dev/mmcblk0p13 rootwait rw"
+bc. abootimg -u boot-qcom-apq8064-eI_ERAGON600-qcom-snapdragon-##VERSION##.img -c "cmdline=console=ttyMSM0,115200n8 root=/dev/disk/by-partlabel/userdata rootwait rw"
sudo fastboot flash boot boot-qcom-apq8064-eI_ERAGON600-qcom-snapdragon-##VERSION##.img
Note: @abootimg@ is a tool to read/write/update Android boot partition, and 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:
@@ -369,9 +369,9 @@ bc. cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-apq8064-eI_ERAGON600.dtb >
To boot a custom kernel image, you can run the following @fastboot@ command:
-bc. sudo fastboot boot -c "console=ttyMSM0,115200,n8 root=/dev/mmcblk0p13 rootwait rw text" -b 0x80200000 zImage-dtb
+bc. sudo fastboot boot -c "console=ttyMSM0,115200,n8 root=/dev/disk/by-partlabel/userdata rootwait rw text" -b 0x80200000 zImage-dtb
-If you have followed these instructions, the root file system was flashed into the @userdata@ partition which is known as @/dev/mmcblk0p13@ from Linux kernel. The @-c@ arguments represent the @bootargs@ that will be passed to the kernel during the boot.
+If you have followed these instructions, the root file system was flashed into the @userdata@ partition. The @-c@ arguments represent the @bootargs@ that will be passed to the kernel during the boot.
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,
@@ -488,7 +488,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.
* 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/ 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/mmcblk0p7@
+* 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