diff options
| author | Ryan Harkin <ryan.harkin@linaro.org> | 2014-06-24 16:49:27 +0100 |
|---|---|---|
| committer | Ryan Harkin <ryan.harkin@linaro.org> | 2014-06-24 16:49:27 +0100 |
| commit | a1132a757ee032380d8d3672f22c6cb55c34dec2 (patch) | |
| tree | 7742911a6e5826a70d713d6f62bd099eef30ea80 /android/images | |
| parent | 9b299667ef7d58b7f2c0da5a31379113cb385541 (diff) | |
14.06: fix < and >
Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>
Diffstat (limited to 'android/images')
6 files changed, 34 insertions, 34 deletions
diff --git a/android/images/armv8-android-juno-lsk/HOWTO_getsourceandbuild.txt b/android/images/armv8-android-juno-lsk/HOWTO_getsourceandbuild.txt index 84ce296..6689cff 100644 --- a/android/images/armv8-android-juno-lsk/HOWTO_getsourceandbuild.txt +++ b/android/images/armv8-android-juno-lsk/HOWTO_getsourceandbuild.txt @@ -122,7 +122,7 @@ The following tools and environment are required: * The instructions on this page below assume that the environment variable $JUNO_ROOT_DIR has been initialised to a working directory. -bc. $ export JUNO_ROOT_DIR=<path-to-working-dir>/<name-of-working-dir> +bc. $ export JUNO_ROOT_DIR=<path-to-working-dir>;/<name-of-working-dir>; @@ -159,7 +159,7 @@ h3. Configuration Set the compiler path -bc. $ export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf- +bc. $ export CROSS_COMPILE=<path-to-aarch64-gcc>;/bin/aarch64-none-elf- h3. Building @@ -177,17 +177,17 @@ bc. $ make PLAT=juno DEBUG=1 V=1 all The build process creates products in a `build` directory tree, building the objects for each boot loader stage in separate sub-directories. The following boot loader binary files are created: - `build/juno/<build-type>/bl1.bin` + `build/juno/<build-type>;/bl1.bin` - `build/juno/<build-type>/bl2.bin` + `build/juno/<build-type>;/bl2.bin` - `build/juno/<build-type>/bl31.bin` + `build/juno/<build-type>;/bl31.bin` - `build/juno/<build-type>/bl32.bin` + `build/juno/<build-type>;/bl32.bin` -... where `<build-type>` is either `debug` or `release`. +... where `<build-type>;` is either `debug` or `release`. @@ -216,7 +216,7 @@ h3. Configuration 1. Define the AArch64 GCC toolchain: -bc. $ export GCC48_AARCH64_PREFIX=<path-to-aarch64-gcc>/bin/aarch64-none-elf- +bc. $ export GCC48_AARCH64_PREFIX=<path-to-aarch64-gcc>;/bin/aarch64-none-elf- 2. Configure Tianocore environment: @@ -240,7 +240,7 @@ To build RELEASE version of UEFI firmware: bc. $ make -f ArmPlatformPkg/ArmJunoPkg/Makefile EDK2_BUILD=RELEASE -Use the release binary $JUNO_ROOT_DIR/edk2>/Build/ArmJuno/RELEASE_GCC48/FV/BL32_AP_UEFI.fd as bl33.bin when generating the Firmware Image Package binary. +Use the release binary $JUNO_ROOT_DIR/edk2>;/Build/ArmJuno/RELEASE_GCC48/FV/BL32_AP_UEFI.fd as bl33.bin when generating the Firmware Image Package binary. To clean EDK2 source tree: @@ -281,7 +281,7 @@ bc. $ export PATH=$JUNO_ROOT_DIR/arm-trusted-firmware/tools/fip_crea bc. $ cd $JUNO_ROOT_DIR $ mkdir fip $ cd fip -$ cp <path to prebuilt binary>/bl30.bin . +$ cp <path to prebuilt binary>;/bl30.bin . $ cp $JUNO_ROOT_DIR/arm-trusted-firmware/build/juno/release/bl2.bin . $ cp $JUNO_ROOT_DIR/arm-trusted-firmware/build/juno/release/bl31.bin . $ cp $JUNO_ROOT_DIR/edk2/Build/ArmJuno/RELEASE_GCC48/FV/BL32_AP_UEFI.fd bl33.bin diff --git a/android/images/armv8-android-juno-lsk/HOWTO_gettingstarted.txt b/android/images/armv8-android-juno-lsk/HOWTO_gettingstarted.txt index 04e12c4..ba8355d 100644 --- a/android/images/armv8-android-juno-lsk/HOWTO_gettingstarted.txt +++ b/android/images/armv8-android-juno-lsk/HOWTO_gettingstarted.txt @@ -157,11 +157,11 @@ The Mali GPU in Juno is able to use a variety of texture compression formats, ma 3. Connect the 12 volt power supply to the board. -The serial terminal will show the command prompt Cmd> +The serial terminal will show the command prompt Cmd>; -4. At the Cmd> prompt on the serial terminal, issue the command usb_on +4. At the Cmd>; prompt on the serial terminal, issue the command usb_on -bc. Cmd> usb_on +bc. Cmd>; usb_on The configuration flash memory should now be visible on the host computer as a mass storage device. @@ -171,7 +171,7 @@ The configuration flash memory should now be visible on the host computer as a m 7. In the [SCC REGISTERS] section, below the “TOTALSCCS” line, insert the following line: -SCC: 0x05C <value from step 6 above> ;Optional comment to explain which texture you have enabled +SCC: 0x05C <value from step 6 above>; ;Optional comment to explain which texture you have enabled 8. Update the TOTALSCCS count (increment it by one) so that it now reflects the total number of SCC registers that are programmed. diff --git a/android/images/armv8-android-juno-lsk/HOWTO_install.txt b/android/images/armv8-android-juno-lsk/HOWTO_install.txt index 1ef5ca4..57bb67a 100644 --- a/android/images/armv8-android-juno-lsk/HOWTO_install.txt +++ b/android/images/armv8-android-juno-lsk/HOWTO_install.txt @@ -141,11 +141,11 @@ To carry out a system recovery or update the MCC firmware, follow these steps: 3. Connect the 12 volt power supply to the board. -The serial terminal will show the command prompt Cmd> +The serial terminal will show the command prompt Cmd>; -4. At the Cmd> prompt on the serial terminal, issue the command usb_on +4. At the Cmd>; prompt on the serial terminal, issue the command usb_on -bc. Cmd> usb_on +bc. Cmd>; usb_on The configuration flash memory should now be visible on the host computer as a mass storage device. diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_getsourceandbuild.txt b/android/images/armv8-juice-juno-lsk/HOWTO_getsourceandbuild.txt index 705efcc..968f437 100644 --- a/android/images/armv8-juice-juno-lsk/HOWTO_getsourceandbuild.txt +++ b/android/images/armv8-juice-juno-lsk/HOWTO_getsourceandbuild.txt @@ -122,7 +122,7 @@ The following tools and environment are required: * The instructions on this page below assume that the environment variable $JUNO_ROOT_DIR has been initialised to a working directory. -bc. $ export JUNO_ROOT_DIR=<path-to-working-dir>/<name-of-working-dir> +bc. $ export JUNO_ROOT_DIR=<path-to-working-dir>;/<name-of-working-dir>; @@ -159,7 +159,7 @@ h3. Configuration Set the compiler path -bc. $ export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf- +bc. $ export CROSS_COMPILE=<path-to-aarch64-gcc>;/bin/aarch64-none-elf- h3. Building @@ -177,17 +177,17 @@ bc. $ make PLAT=juno DEBUG=1 V=1 all The build process creates products in a `build` directory tree, building the objects for each boot loader stage in separate sub-directories. The following boot loader binary files are created: - `build/juno/<build-type>/bl1.bin` + `build/juno/<build-type>;/bl1.bin` - `build/juno/<build-type>/bl2.bin` + `build/juno/<build-type>;/bl2.bin` - `build/juno/<build-type>/bl31.bin` + `build/juno/<build-type>;/bl31.bin` - `build/juno/<build-type>/bl32.bin` + `build/juno/<build-type>;/bl32.bin` -... where `<build-type>` is either `debug` or `release`. +... where `<build-type>;` is either `debug` or `release`. @@ -216,7 +216,7 @@ h3. Configuration 1. Define the AArch64 GCC toolchain: -bc. $ export GCC48_AARCH64_PREFIX=<path-to-aarch64-gcc>/bin/aarch64-none-elf- +bc. $ export GCC48_AARCH64_PREFIX=<path-to-aarch64-gcc>;/bin/aarch64-none-elf- 2. Configure Tianocore environment: @@ -240,7 +240,7 @@ To build RELEASE version of UEFI firmware: bc. $ make -f ArmPlatformPkg/ArmJunoPkg/Makefile EDK2_BUILD=RELEASE -Use the release binary $JUNO_ROOT_DIR/edk2>/Build/ArmJuno/RELEASE_GCC48/FV/BL32_AP_UEFI.fd as bl33.bin when generating the Firmware Image Package binary. +Use the release binary $JUNO_ROOT_DIR/edk2>;/Build/ArmJuno/RELEASE_GCC48/FV/BL32_AP_UEFI.fd as bl33.bin when generating the Firmware Image Package binary. To clean EDK2 source tree: @@ -281,7 +281,7 @@ bc. $ export PATH=$JUNO_ROOT_DIR/arm-trusted-firmware/tools/fip_crea bc. $ cd $JUNO_ROOT_DIR $ mkdir fip $ cd fip -$ cp <path to prebuilt binary>/bl30.bin . +$ cp <path to prebuilt binary>;/bl30.bin . $ cp $JUNO_ROOT_DIR/arm-trusted-firmware/build/juno/release/bl2.bin . $ cp $JUNO_ROOT_DIR/arm-trusted-firmware/build/juno/release/bl31.bin . $ cp $JUNO_ROOT_DIR/edk2/Build/ArmJuno/RELEASE_GCC48/FV/BL32_AP_UEFI.fd bl33.bin diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_gettingstarted.txt b/android/images/armv8-juice-juno-lsk/HOWTO_gettingstarted.txt index b489db4..2163c25 100644 --- a/android/images/armv8-juice-juno-lsk/HOWTO_gettingstarted.txt +++ b/android/images/armv8-juice-juno-lsk/HOWTO_gettingstarted.txt @@ -157,11 +157,11 @@ The Mali GPU in Juno is able to use a variety of texture compression formats, ma 3. Connect the 12 volt power supply to the board. -The serial terminal will show the command prompt Cmd> +The serial terminal will show the command prompt Cmd>; -4. At the Cmd> prompt on the serial terminal, issue the command usb_on +4. At the Cmd>; prompt on the serial terminal, issue the command usb_on -bc. Cmd> usb_on +bc. Cmd>; usb_on The configuration flash memory should now be visible on the host computer as a mass storage device. @@ -171,7 +171,7 @@ The configuration flash memory should now be visible on the host computer as a m 7. In the [SCC REGISTERS] section, below the “TOTALSCCS” line, insert the following line: -SCC: 0x05C <value from step 6 above> ;Optional comment to explain which texture you have enabled +SCC: 0x05C <value from step 6 above>; ;Optional comment to explain which texture you have enabled 8. Update the TOTALSCCS count (increment it by one) so that it now reflects the total number of SCC registers that are programmed. diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_install.txt b/android/images/armv8-juice-juno-lsk/HOWTO_install.txt index bb84abd..7d97a57 100644 --- a/android/images/armv8-juice-juno-lsk/HOWTO_install.txt +++ b/android/images/armv8-juice-juno-lsk/HOWTO_install.txt @@ -141,11 +141,11 @@ To carry out a system recovery or update the MCC firmware, follow these steps: 3. Connect the 12 volt power supply to the board. -The serial terminal will show the command prompt Cmd> +The serial terminal will show the command prompt Cmd>; -4. At the Cmd> prompt on the serial terminal, issue the command usb_on +4. At the Cmd>; prompt on the serial terminal, issue the command usb_on -bc. Cmd> usb_on +bc. Cmd>; usb_on The configuration flash memory should now be visible on the host computer as a mass storage device. |