14.06: complete overhaul of Juno notesjuno

Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>

10 files changed, 1003 insertions, 125 deletions

diff --git a/android/juno-lsk/HOWTO_flashfirmware.txt b/android/juno-lsk/HOWTO_flashfirmware.txt
index db74211..afc7c90 100644
--- a/android/juno-lsk/HOWTO_flashfirmware.txt
+++ b/android/juno-lsk/HOWTO_flashfirmware.txt
@@ -1,6 +1,150 @@
-Instructions supplied by Linaro (based on information from the Connected Community site), explaining how to build (where appropriate) and install firmware images.
+h2. Disclaimer
 
-Includes:
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/android/juno-lsk/#tabs-5.
 
-* Prominent disclaimer: “The use of Juno software is subject to the terms of the Juno "End User License Agreement":http://community.arm.com/docs/DOC-8402”.  <the link should point to the EULA tab>
-* List of prerequisites (mainly tools etc)
+*Getting Started Tab*
+
+ 
+
+*Juno ports*
+
+ 
+
+*Back panel*
+
+!Linaro_Release_Notes_v1_files/image001.png!
+
+*Front panel*
+
+!Linaro_Release_Notes_v1_files/image002.png!
+
+There are 4 UARTs on the Juno board:
+
+<table>
+<col width="20%" />
+<col width="20%" />
+<col width="20%" />
+<col width="20%" />
+<col width="20%" />
+<tbody>
+<tr class="odd">
+<td align="left"> 
+
+SoC UART0
+
+SoC UART1
+
+FPGA UART0
+
+FPGA UART1
+</td>
+<td align="left">Location
+
+"back panel":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel, top slot.
+
+"back panel":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel, bottom slot.
+
+Corresponds to the J55 header on the board. Please contact ARM for more information about this type of header.
+
+Corresponds to J56 header on the board. Please contact ARM for more information about this type of header
+</td>
+<td align="left">Used by
+
+The motherboard, UEFI and the Linux kernel.
+
+SCP firmware
+
+AP Trusted Firmware
+
+Unused at the moment
+</td>
+<td align="left">Baud
+
+115200
+
+115200
+
+115200
+
+-
+</td>
+<td align="left">Data bits
+
+8
+
+8
+
+8
+
+-
+</td>
+</tr>
+</tbody>
+</table>
+
+ 
+
+*Quick Start*
+
+If you have just unpacked a new Juno board and would like to get it booting straight away, you may wish to skip ahead to the “Set up and boot the Juno board” section.  &lt;make this a link&gt;
+
+ 
+
+*Juno software stack overview*
+
+There are several pieces of software that make up the complete Juno software stack, and a description of each one follows below.
+
+*Juno MCC Microcontroller Firmware*
+
+The MCC is a microcontroller on the motherboard that takes care of early setup before the SCP or applications processors are powered on. The MCC is also responsible for managing firmware upgrades.
+
+*System Control Processor (SCP) Firmware*
+
+The Juno System Control Processor (SCP) is an on-chip Cortex-M3 that provides low level power management and system control for the Juno platform.
+
+*Application Processor (AP) Trusted Firmware*
+
+The Juno AP Trusted Firmware provides low-level Trusted World support for the Juno platform.
+
+*Unified Extensible Firmware Interface (UEFI)*
+
+The Juno UEFI implementation provides Linux loader support for the Juno platform. It is based on the open source EFI Development Kit 2 (EDK2) implementation from the Tianocore sourceforge project.
+
+*Linux Kernel*
+
+The Linaro Stable Kernel (LSK) for Juno.
+
+*Linux filesystem*
+
+An Openembedded filesystem from Linaro can be mounted via USB (recommended) or NFS over Ethernet.
+
+*Android kernel and AOSP*
+
+The LSK image contains Android patches and has a unified defconfig, so the same kernel binary will work with a Linux filesystem or an AOSP filesystem (available from Linaro).
+
+ 
+
+*Software preloaded on new Juno boards*
+
+New Juno boards arrive preloaded with MCC firmware, SCP firmware, AP trusted firmware, UEFI, and a Linux kernel. The Juno board does not contain a Linux filesystem anywhere in onboard storage.
+
+*Please note* that early batches of Juno boards contained an SCP firmware image that limits the CPU clock to 50 MHz. ARM strongly recommends that you immediately upgrade to the latest "firmware image":http://community.arm.com/docs/DOC-8396#jive_content_id_Juno_Board_Recovery_Image hosted on this website.  &lt;link should point to firmware tab&gt;
+
+When the power is first turned on, it should boot straight through to Linux. UEFI offers a 10 second window during which you can interrupt the boot sequence by pressing a key on the serial terminal, otherwise the Linux kernel will be launched. In order to reach the Linux shell you must attach a Linux "filesystem":http://community.arm.com/docs/DOC-8396#jive_content_id_Deploying_a_root_filesystem via USB. If no filesystem is attached then Linux will boot as far as it can and then announce that it is waiting for a filesystem to be attached.
+
+New Juno boards do not contain any Android software pre-installed.
+
+ 
+
+*Set up and boot the Juno board*
+
+You are strongly recommended to update to the latest firmware before doing anything productive with your Juno board.
+
+The steps to set up and boot the board are:
+
+# Connect a serial terminal to the "UART0":http://community.arm.com/docs/DOC-8396#jive_content_id_Setting_up_the_board connector ("settings":http://community.arm.com/docs/DOC-8396#jive_content_id_Setting_up_the_board). &lt;UART0 link should point to the back panel picture, settings link should point to the UART table below it&gt;
+# Connect the 12 volt power, then press the red "ON/OFF button":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel on the back panel. &lt;link should point to the back panel picture&gt;
+
+*Getting Juno to boot to the Linux shell*
+
+If you have just received a new board and powered it on for the first time, you will not reach the Linux shell. Juno will boot Linux to the point where it looks for a filesystem, and when it can't find one it will sit and wait for one to be attached. To boot all the way to the Linux shell you will need to "attach a root filesystem":http://community.arm.com/docs/DOC-8396#jive_content_id_Deploying_a_root_filesystem.  &lt;the link should point to the relevant section in the “Binary Image Installation” tab&gt;
diff --git a/android/juno-lsk/HOWTO_getsourceandbuild.txt b/android/juno-lsk/HOWTO_getsourceandbuild.txt
index 3d3e2f4..b31b4ee 100644
--- a/android/juno-lsk/HOWTO_getsourceandbuild.txt
+++ b/android/juno-lsk/HOWTO_getsourceandbuild.txt
@@ -1,7 +1,103 @@
-Instructions supplied by Linaro (based on information from the Connected Community site), explaining how to obtain and build source files
+h2. Disclaimer
 
-Includes:
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/android/juno-lsk/#tabs-5.
 
-* Prominent disclaimer: “The use of Juno software is subject to the terms of the Juno "End User License Agreement":http://community.arm.com/docs/DOC-8402”.  &lt;the link should point to the EULA tab&gt;
-* List of prerequisites (mainly tools etc)
-* How to enable big.LITTLE support
+h1. Accessing Source Code
+
+h2. Linaro Android Source Code
+
+Run the "linaro_android_build_cmds.sh":http://releases.linaro.org/14.06/android/juno-lsk/linaro_android_build_cmds.sh script, it will download the entire source code for both Android and the kernel and attempt to build it.
+
+The pinned and source manifests can be found here:
+
+* "Pinned Manifest":http://releases.linaro.org/14.06/android/juno-lsk/pinned-manifest.xml ("?":https://wiki.linaro.org/Platform/Android/ReproduceABuildExactly)
+* "Source Manifest":http://releases.linaro.org/14.06/android/juno-lsk/source-manifest.xml
+
+h2. Kernel Source Code
+
+Obtain the exact *kernel source code* for this cycle by using the "linaro_kernel_build_cmds.sh":http://releases.linaro.org/14.06/android/juno-lsk/linaro_kernel_build_cmds.sh script to download the source and build it. You can get the kernel configuration from "here":http://releases.linaro.org/14.06/android/juno-lsk/kernel_config (listed above)
+
+h2. Compiling Linaro Android RootFS+Kernel
+
+The following simple steps download, install and compile a complete Linaro Android distribution
+
+* Download and install Ubuntu 12.04 64 bit or newer ("download":http://www.ubuntu.com)
+* Install the following packages:
+
+bc. sudo apt-get install zip curl flex bison build-essential git-core gnupg gperf zlib1g-dev libx11-dev x11proto-core-dev \
+gcc-multilib g++-multilib libc6-dev-i386 ia32-libs lib32z-dev gcc-4.5 g++-4.5 cpp-4.5 gcc-4.5-multilib g++-4.5-multilib \
+uuid-dev openjdk-6-jdk ant lib32ncurses5-dev xsltproc
+
+* Download the Android building script for this release from "here":http://releases.linaro.org/14.06/android/juno-lsk/linaro_android_build_cmds.sh or from the list of artifacts listed above.
+
+* Run the script
+
+bc. chmod a+x linaro_android_build_cmds.sh
+./linaro_android_build_cmds.sh
+
+h3. Installing Android on your board
+
+* Insert a USB drive and note the assigned @'/dev/sdX'@ or @'/dev/mmcblk0'@
+
+bc. dmesg | less
+
+Look for a line that looks like the following at the end of the log
+
+@[288582.790722] sdc: sdc1 sdc2 sdc3 sdc4 <sdc5 sdc6 >@
+
+Or, if your machine uses '/dev/mmcblkX', you may see a line line this:
+
+@[10770.938042]  mmcblk0: p1 p2 p3 p4 < p5 p6 >@
+
+*WARNING:* In the next step, make sure you use /dev/"whatever you see above". *You can erase your hard drive* with the wrong parameter.
+
+* Create media
+
+bc. cd android/out/target/product/
+sudo linaro-android-media-create --mmc /dev/sdX --dev juno --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2
+
+* Insert the USB drive into your board and reboot it
+
+p. You must configure UEFI exach time you create a new disk image.
+
+h2. Compiling and installing your Kernel
+
+h3. Prerequisites
+
+* Download and install Ubuntu 12.04 64 bit or newer ("download":http://www.ubuntu.com)
+* Install the following packages by typing:
+
+bc. sudo apt-get install build-essential git curl
+
+* toolchain
+
+bc. mkdir -p ~/bin
+cd ~/bin
+wget http://releases.linaro.org/13.11/components/toolchain/binaries/gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux.tar.xz
+tar xf gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux.tar.xz
+PATH=$PATH:~/bin/gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux/bin
+
+* Create a working subdirectory
+* Download the auto build script for this release from the list of artifacts above (the kernel configuration will be automatically downloaded).
+* Run the build script
+
+bc. chmod a+x linaro_kernel_build_cmds.sh
+./linaro_kernel_build_cmds.sh
+
+h1. Installing your kernel
+
+This section is common for both Android and OpenEmbedded
+
+* Create the Device Tree blob if you don’t have one in your Linaro image (note, the A9 Core Tile boots using an ATAGS kernel):
+
+bc. make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- dtbs
+
+* Insert the USB drive containing the Linaro disk image
+* Copy the kernel onto the memory card
+
+bc. cp arch/arm64/boot/Image /media/boot/
+cp arch/arm64/boot/dts/juno.dtb /media/boot
+
+* Eject the USB drive @eject /media/boot@
+
+* Insert the USB drive into the board and power it on
diff --git a/android/juno-lsk/HOWTO_install.txt b/android/juno-lsk/HOWTO_install.txt
index 3673e3e..c136a95 100644
--- a/android/juno-lsk/HOWTO_install.txt
+++ b/android/juno-lsk/HOWTO_install.txt
@@ -1,155 +1,105 @@
-Instructions supplied by Linaro (based on information from the Connected Community site), explaining how to install binary images.
+h2. Disclaimer
 
-Includes:
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/android/juno-lsk/#tabs-5.
 
-* Prominent disclaimer: “The use of Juno software is subject to the terms of the Juno "End User License Agreement":http://community.arm.com/docs/DOC-8402”.  &lt;the link should point to the EULA tab&gt;
-* List of prerequisites (mainly tools etc)
+h2. Installation
 
+Linaro Android releases are made up of the following components.
 
+| *.img.bz2 | pre-built Android disk image |
+| kernel | kernel binary |
+| bl1.bin | ARM Trused Firmware BL1 binary |
+| fip.bin | ARM Trused Firmware Firmware Image Package (FIP) binary |
+| juno.dtb | Device Tree Binary |
+| ramdisk.img | Ramdisk image |
+| linaro_android_build_cmds.sh | Build script for the complete Android release |
+| linaro_kernel_build_cmds.sh | Build script for the Linux kernel |
 
-*Getting Started Tab*
+Other files such as *manifest*, *.txt and *.html provide information such as package contents or MD5SUMs about the files they share a common filename with.
 
- 
+Linaro provides two methods for installing Linaro binary builds:
 
-*Juno ports*
+# Using a pre-built image, which you can download
+# Assembling your own image using provided components
 
- 
+h2. Pre-Installation Steps
 
-*Back panel*
+Before any installation begins, it is important that you ensure your board has the latest firmware and boot loader installed. Please check the "Firmware Update tab":https://releases.linaro.org/14.06/android/juno-lsk/#tabs-4 on this page for the latest updates and installation instructions.
 
-!Linaro_Release_Notes_v1_files/image001.png!
+h2. Using pre-built image
 
-*Front panel*
+h3. Prerequisites
 
-!Linaro_Release_Notes_v1_files/image002.png!
+* Ubuntu 12.04 64 bit or newer on your desktop PC, which you can download from "www.ubuntu.com":http://www.ubuntu.com
+* 4GB USB drive or larger
+* Latest firmware installed onto the board. Please see "Firmware Update tab":https://releases.linaro.org/14.06/android/juno-lsk/#tabs-4
+* This release pre-built image (vexpress.img.bz2), which you can downloaded from the above list of artifacts or just click "here":http://releases.linaro.org/14.06/android/juno-lsk/vexpress.img.bz2
 
-There are 4 UARTs on the Juno board:
+h3. Installation Steps
 
-<table>
-<col width="20%" />
-<col width="20%" />
-<col width="20%" />
-<col width="20%" />
-<col width="20%" />
-<tbody>
-<tr class="odd">
-<td align="left"> 
+* Unzip the downloaded pre-built image
+* Insert USB drive into your PC and note the assigned @'/dev/sdX'@
 
-SoC UART0
+bc. dmesg
+DRIVE=/dev/sdX # USB drive found from dmesg above
+bzcat vexpress.img.bz2 | sudo dd bs=64k of=$DRIVE
 
-SoC UART1
+When the image is created, skip down to the section "Booting the image".
 
-FPGA UART0
+*Note:* Windows users may use the "Image Writer for Windows":https://launchpad.net/win32-image-writer/+download
 
-FPGA UART1
-</td>
-<td align="left">Location
+<hr>
 
-"back panel":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel, top slot.
+h2. Building a custom image using pre-built components.
 
-"back panel":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel, bottom slot.
+Sometimes, you may wish to build your own custom image for your board. Perhaps you wish to use a more recent snapshot of the "hardware pack":https://wiki.linaro.org/HardwarePacks or take the latest Android build. Whatever the reason, you will want to use the "Linaro Image Tools":https://wiki.linaro.org/Linaro-Image-Tools to create a custom image.
 
-Corresponds to the J55 header on the board. Please contact ARM for more information about this type of header.
+Using components to generate the image will yield the same functionality found in the pre-built image of the same release.
 
-Corresponds to J56 header on the board. Please contact ARM for more information about this type of header
-</td>
-<td align="left">Used by
+h3. Prerequisites
 
-The motherboard, UEFI and the Linux kernel.
+* Ubuntu 12.04 64 bit or newer on your desktop PC, which you can download from "www.ubuntu.com":http://www.ubuntu.com
+* Download Artifacts from above or use the following command in your terminal
 
-SCP firmware
+bc. wget http://releases.linaro.org/14.06/android/juno-lsk/boot.tar.bz2
+wget http://releases.linaro.org/14.06/android/juno-lsk/system.tar.bz2
+wget http://releases.linaro.org/14.06/android/juno-lsk/userdata.tar.bz2
 
-AP Trusted Firmware
+* Download "Linaro image tools":https://wiki.linaro.org/Linaro-Image-Tools which can be obtained in two ways:
 
-Unused at the moment
-</td>
-<td align="left">Baud
+** Method 1: Install them from the Linaro Image Tools "PPA":https://launchpad.net/~linaro-maintainers/+archive/tools
 
-115200
+bc. sudo add-apt-repository ppa:linaro-maintainers/tools
+sudo apt-get update
+sudo apt-get install linaro-image-tools
 
-115200
+** Method 2: Building from source
 
-115200
+bc. wget http://releases.linaro.org/14.06/components/platform/linaro-image-tools/linaro-image-tools-2014.06.tar.gz
 
--
-</td>
-<td align="left">Data bits
+* Insert the USB drive and note the assigned @'/dev/sdX'@ or @'/dev/mmcblk0'@
 
-8
+bc. dmesg | less
 
-8
+Look for a line that looks like the following at the end of the log
 
-8
+@[288582.790722] sdc: sdc1 sdc2 sdc3 sdc4 <sdc5 sdc6 >@
 
--
-</td>
-</tr>
-</tbody>
-</table>
+Or, if your machine uses @'/dev/mmcblkX'@, you may see a line line this:
 
- 
+@[10770.938042]  mmcblk0: p1 p2 p3 p4 < p5 p6 >@
 
-*Quick Start*
+*WARNING:* In the next step, make sure you use @/dev/"whatever you see above"@. *You can erase your hard drive* with the wrong parameter.
 
-If you have just unpacked a new Juno board and would like to get it booting straight away, you may wish to skip ahead to the “Set up and boot the Juno board” section.  &lt;make this a link&gt;
+* Create media
 
- 
+bc. linaro-android-media-create --mmc /dev/sdX --dev juno --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2
 
-*Juno software stack overview*
+h2. Booting the image
 
-There are several pieces of software that make up the complete Juno software stack, and a description of each one follows below.
+After the media create tool has finished executing, remove the USB drive from your PC and insert it into the board.
 
-*Juno MCC Microcontroller Firmware*
+Before you can boot the image you will need to update the UEFI Boot Device configuration using the UEFI menu system.  Please see the 
 
-The MCC is a microcontroller on the motherboard that takes care of early setup before the SCP or applications processors are powered on. The MCC is also responsible for managing firmware upgrades.
+The instructions on the "Firmware Update tab":https://releases.linaro.org/14.06/android/juno-lsk/#tabs-4 provide information on how to configure UEFI to specify the USB drive as a boot device.
 
-*System Control Processor (SCP) Firmware*
-
-The Juno System Control Processor (SCP) is an on-chip Cortex-M3 that provides low level power management and system control for the Juno platform.
-
-*Application Processor (AP) Trusted Firmware*
-
-The Juno AP Trusted Firmware provides low-level Trusted World support for the Juno platform.
-
-*Unified Extensible Firmware Interface (UEFI)*
-
-The Juno UEFI implementation provides Linux loader support for the Juno platform. It is based on the open source EFI Development Kit 2 (EDK2) implementation from the Tianocore sourceforge project.
-
-*Linux Kernel*
-
-The Linaro Stable Kernel (LSK) for Juno.
-
-*Linux filesystem*
-
-An Openembedded filesystem from Linaro can be mounted via USB (recommended) or NFS over Ethernet.
-
-*Android kernel and AOSP*
-
-The LSK image contains Android patches and has a unified defconfig, so the same kernel binary will work with a Linux filesystem or an AOSP filesystem (available from Linaro).
-
- 
-
-*Software preloaded on new Juno boards*
-
-New Juno boards arrive preloaded with MCC firmware, SCP firmware, AP trusted firmware, UEFI, and a Linux kernel. The Juno board does not contain a Linux filesystem anywhere in onboard storage.
-
-*Please note* that early batches of Juno boards contained an SCP firmware image that limits the CPU clock to 50 MHz. ARM strongly recommends that you immediately upgrade to the latest "firmware image":http://community.arm.com/docs/DOC-8396#jive_content_id_Juno_Board_Recovery_Image hosted on this website.  &lt;link should point to firmware tab&gt;
-
-When the power is first turned on, it should boot straight through to Linux. UEFI offers a 10 second window during which you can interrupt the boot sequence by pressing a key on the serial terminal, otherwise the Linux kernel will be launched. In order to reach the Linux shell you must attach a Linux "filesystem":http://community.arm.com/docs/DOC-8396#jive_content_id_Deploying_a_root_filesystem via USB. If no filesystem is attached then Linux will boot as far as it can and then announce that it is waiting for a filesystem to be attached.
-
-New Juno boards do not contain any Android software pre-installed.
-
- 
-
-*Set up and boot the Juno board*
-
-You are strongly recommended to update to the latest firmware before doing anything productive with your Juno board.
-
-The steps to set up and boot the board are:
-
-# Connect a serial terminal to the "UART0":http://community.arm.com/docs/DOC-8396#jive_content_id_Setting_up_the_board connector ("settings":http://community.arm.com/docs/DOC-8396#jive_content_id_Setting_up_the_board). &lt;UART0 link should point to the back panel picture, settings link should point to the UART table below it&gt;
-# Connect the 12 volt power, then press the red "ON/OFF button":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel on the back panel. &lt;link should point to the back panel picture&gt;
-
-*Getting Juno to boot to the Linux shell*
-
-If you have just received a new board and powered it on for the first time, you will not reach the Linux shell. Juno will boot Linux to the point where it looks for a filesystem, and when it can't find one it will sit and wait for one to be attached. To boot all the way to the Linux shell you will need to "attach a root filesystem":http://community.arm.com/docs/DOC-8396#jive_content_id_Deploying_a_root_filesystem.  &lt;the link should point to the relevant section in the “Binary Image Installation” tab&gt;
diff --git a/android/juno-lsk/HOWTO_releasenotes.txt b/android/juno-lsk/HOWTO_releasenotes.txt
index 5e51707..951d818 100644
--- a/android/juno-lsk/HOWTO_releasenotes.txt
+++ b/android/juno-lsk/HOWTO_releasenotes.txt
@@ -2,7 +2,7 @@
 
 *License*
 
-The use of Juno software is subject to the terms of the Juno "End User License Agreement":http://community.arm.com/docs/DOC-8402.Top of Form  &lt;link should point to EULA tab&gt;**
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/android/juno-lsk/#tabs-5.
 
 * *
 
@@ -18,7 +18,7 @@ h1. About the Linaro Stable Kernel (LSK)
 
 The Linaro Stable Kernel (LSK) is produced, validated and released by Linaro and is based on the linux stable kernel tree. The LSK focuses on quality and stability and is therefore a great foundation for product development. It also includes backports of commonly desired features, provided they meet the quality requirements, and also any bug fixes.
 
-LSK releases appear monthly. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/14.05/openembedded/vexpress-lsk/#tabs-3 tab).  &lt;link should point to the “building from sources” tab&gt;
+LSK releases appear monthly. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/14.06/android/juno-lsk/#tabs-3 tab).  &lt;link should point to the “building from sources” tab&gt;
 
  
 
diff --git a/openembedded/juno-lsk/EULA.txt b/openembedded/juno-lsk/EULA.txt
new file mode 100644
index 0000000..55e813f
--- /dev/null
+++ b/openembedded/juno-lsk/EULA.txt
@@ -0,0 +1,269 @@
+THIS END USER LICENCE AGREEMENT (“LICENCE”) IS A LEGAL AGREEMENT BETWEEN YOU (EITHER A SINGLE INDIVIDUAL, OR SINGLE LEGAL ENTITY) AND ARM LIMITED (&quot;ARM&quot;) FOR THE USE OF THE DELIVERABLES ACCOMPANYING THIS LICENCE. ARM IS ONLY WILLING TO LICENSE THE DELIVERABLES TO YOU ON CONDITION THAT YOU ACCEPT ALL OF THE TERMS IN THIS LICENCE. BY CLICKING “I AGREE” OR BY INSTALLING OR OTHERWISE USING OR COPYING THE DELIVERABLES YOU INDICATE THAT YOU AGREE TO BE BOUND BY ALL THE TERMS OF THIS LICENCE. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENCE, ARM IS UNWILLING TO LICENSE THE DELIVERABLES TO YOU AND YOU MAY NOT INSTALL, USE OR COPY THE DELIVERABLES, BUT YOU SHOULD PROMPTLY RETURN THE DELIVERABLES TO YOUR SUPPLIER AND ASK FOR A REFUND OF ANY LICENCE FEE PAID.
+
+ 
+
+“ARM Versatile Express Development Board” means a hardware development board purchased directly from ARM or its authorised distributors.
+
+ 
+
+&quot;Deliverables&quot; means any software, firmware, boardfiles, data and documentation accompanying this Licence, any printed, electronic or online documentation supplied with it, and any updates, patches and modifications ARM may make available to you under the terms of this Licence, in all cases relating to the supporting deliverables for the ARM Versatile Express Development Board.
+
+ 
+
+“Separate Files” means the separate files identified in Part D of the Schedule.
+
+ 
+
+1.  LICENCE GRANTS.
+
+(i)  DELIVERABLES: ARM hereby grants to you, subject to the terms and conditions of this Licence, a non-exclusive, non-transferable licence solely for use on an ARM Versatile Express Development Board and only for the purposes of your internal development, testing and debugging of software applications that are designed to run solely on microprocessors manufactured under licence from ARM, to:
+
+ 
+
+(a)     use and copy the Deliverables identified in Part A of the Schedule;
+
+ 
+
+(b)     use, copy and modify the Deliverables identified in Part B and Part C of the Schedule;
+
+ 
+
+(c)     distribute and sub-license to third parties the right to use, copy and modify the Deliverables identified in Part C(i) of the Schedule, or your derivatives thereof, as part of your own products (“Licensed Products”) provided you comply with the terms of Clause 1(ii);
+
+ 
+
+(d)     permit either or both your customers and your authorised distributors to redistribute the Deliverables identified in Part C(i) of the Schedule, or your derivatives thereof, solely as part of Licensed Products developed by you or your permitted users (identified in clause 2 paragraph three below).
+
+ 
+
+Except as permitted by clause 1(i)(b) above, you shall not modify the Deliverables.  Except as permitted by clauses 1(i)(c) and 1(i)(d) above, you shall not redistribute any of the Deliverables.
+
+ 
+
+(ii)  FURTHER CONDITIONS APPLICABLE TO REDISTRIBUTION AND SUB-LICENSING: If you choose to redistribute the Deliverables identified in Part C(i) of the Schedule (“Example Code”) you agree: (a) to ensure that they are licensed for use only as part of Licensed Products and only on microprocessors manufactured or simulated under licence from ARM; (b) not to use ARM's or any of its licensors names, logos or trademarks to market the Licensed Products; (c) to include valid copyright notices on the Licensed Products, and preserve any copyright notices which are included with, or in, the Example Code; (d) to comply with all the other terms of this Licence; and (e) to ensure that any further redistribution is limited to redistribution by either or both your customers and your authorised distributors only as part of Licensed Products developed by you or your permitted users and only for use on microprocessors manufactured or simulated under licence from ARM and  that your customers  and authorised distributors comply with the terms of this clause 1(ii).
+
+ 
+
+2.  RESTRICTIONS ON USE OF THE DELIVERABLES.
+
+COPYING: You shall not use or copy the Deliverables except as expressly authorised in this Licence. You may make one additional copy of the delivered Deliverables media or image for backup or archival purposes.
+
+PERMITTED USERS: The Deliverables shall be used only by your employees, or by your bona fide sub-contractors for whose acts and omissions you hereby agree to be responsible to ARM to the same extent as you are for any acts and omissions of your employees, and provided always that such sub-contractors; (i) work only onsite at your premises; (ii) comply with the terms of this Licence; (iii) are contractually obligated to use the Deliverables only for your benefit, and (iv) agree to assign all their work product and any rights they create therein in the supply of such work to you. Only the single individual, company or other legal entity to whom ARM is supplying this Licence may use the Deliverables. Except as provided in this clause, you shall not allow third parties (including but not limited to any subsidiary, parent or affiliated companies, or offsite contractors you may have) to use the Deliverables unless ARM specifically agrees otherwise with you on a case by case basis.
+
+ 
+
+NO REMOTE USE: The Deliverables shall only be used onsite at your premises and only for your benefit.
+
+MULTIPLE VERSIONS: The media on which the Deliverables resides may contain more than one version of the Deliverables, each of which is compatible with a different operating system (such as Microsoft Windows XP Professional and Red Hat Linux).
+
+ 
+
+ACADEMIC OR EDUCATIONAL USERS ONLY: If you or your employer or institution paid academic or educational pricing for the Deliverables, or the Deliverables are identified as an academic or educational version (together “Academic Software”), then notwithstanding anything else in this Licence, YOU AGREE TO USE THE ACADEMIC SOFTWARE ONLY FOR ACADEMIC, NON-COMMERCIAL PURPOSES, AND ARM DOES NOT GRANT YOU ANY RIGHTS TO DISTRIBUTE OR SUB-LICENSE ANY APPLICATIONS DEVELOPED USING THE ACADEMIC SOFTWARE UNDER THIS LICENCE.
+
+ 
+
+REVERSE ENGINEERING: Except to the extent that such activity is permitted by applicable law you shall not reverse engineer, decompile or disassemble any of the Deliverables. If the Deliverables were provided to you in Europe you shall not reverse engineer, decompile or disassemble any of the Deliverables for the purposes of error correction.
+
+ 
+
+BENCHMARKING: This licence does not prevent you from using the Deliverables for internal benchmarking purposes. However, you shall treat any and all benchmarking data, and any other results of your use or testing of the Deliverables which are indicative of performance, efficacy, reliability or quality, as confidential information and you shall not disclose such information to any third party without the express written permission of ARM.
+
+ 
+
+RESTRICTIONS ON TRANSFER OF LICENSED RIGHTS: The rights granted to you under this Licence may not be assigned, sublicensed or otherwise transferred by you to any third party without the prior written consent of ARM. An assignment shall be deemed to include, without limitation; (i) any transaction or series of transactions whereby a third party acquires, directly or indirectly, the power to control the management and policies of you, whether through the acquisition of voting securities, by contract or otherwise; or (ii) the sale of more than fifty percent (50%) of the your assets whether in a single transaction or series of transactions.  You shall not rent or lease the Deliverables. You shall not share the Deliverables with contractors (except as identified in the ‘PERMITTED USERS' clause above) or other third parties.
+
+ 
+
+COPYRIGHT AND RESERVATION OF RIGHTS: The Deliverables are owned by ARM or its licensors and are protected by copyright and other intellectual property laws and international treaties. The Deliverables are licensed not sold. You acquire no rights to the Deliverables other than as expressly provided by this Licence. You shall not remove from the Deliverables any copyright notice or other notice and shall ensure that any such notice is reproduced in any copies of the whole or any part of the Deliverables made by you or your permitted users.
+
+ 
+
+3.  SUPPORT AND MAINTENANCE.
+
+If you purchased the Deliverables directly from ARM, and you are not receiving them as an update or upgrade or as Academic Software (defined in Clause 2), you are entitled to reasonable support and maintenance for the Deliverables for the period of one (1) year from the date of purchase. The support will be provided on any version of the Deliverables which, at the date of your support request, are either; (a) the current version made generally available by ARM; or (b) the previous version made generally available by ARM at some time during the previous ninety (90) days.
+
+ 
+
+Support will be provided by telephone, email or other written format designated by ARM, prioritised at ARM's discretion, and may not be used as a substitute for training or as additional resource for your programming projects.  Maintenance will be provided in the form of upgrades, updates and patch releases to the Deliverables as and when they are made generally available from ARM. 
+
+ 
+
+ARM's obligation under this Clause 3 is limited to the provision of support and maintenance to you and ARM is under no obligation to provide any support and maintenance to any third parties under this Licence. If you purchase support and maintenance for additional years it will be provided pursuant to this Clause 3 and will be subject to the terms and conditions of this Licence.
+
+ 
+
+If; (i) you obtained the Deliverables from an ARM authorised reseller or other third party; (ii) Deliverables were provided free of charge or for evaluation; or (iii) it is Academic Software, you are not entitled to any support for the Deliverables from ARM, but ARM may, at its sole discretion provide limited support to you. The vendor of the Deliverables may or may not offer support to you for the Deliverables. Please refer to the Technical Support area of http://www.arm.com for contact details for ARM's support service and (if applicable) other authorised support channels.  ARM shall be under no obligation to provide support in respect of any modifications (where permitted) to the Deliverables.
+
+ 
+
+4.  CONFIDENTIALITY.
+
+You acknowledge that the Deliverables and any benchmarking data and related information mentioned in Clause 2 contains trade secrets and confidential material, and you agree to maintain all such information in confidence and apply security measures no less stringent than the measures which you apply to protect your own like information, but not less than a reasonable degree of care, to prevent their unauthorised disclosure and use. Subject to any restrictions imposed by applicable law, the period of confidentiality shall be indefinite. You agree that you shall not use any such information other than in normal use of the Deliverables under the licences granted in this Licence.
+
+ 
+
+Notwithstanding the foregoing you may disclose the Deliverables identified in Part C(i) of the Schedule to third parties solely in exercise of the licence rights contained in Clause 1(i)(c) of this Licence.
+
+ 
+
+5.  LIMITED WARRANTIES.
+
+For the period of ninety (90) days from the date of receipt by you of the Deliverables, ARM warrants to you that (i) the media on which the Deliverables are provided shall be free from defects in materials and workmanship under normal use; and (ii) the Deliverables will perform substantially in accordance with the accompanying documentation (if any). ARM's total liability and your exclusive remedy for breach of these limited warranties shall be limited to ARM, at ARM's option; (a) replacing the defective Deliverables; or (b) using reasonable efforts to correct material, documented, reproducible defects in the Deliverables and delivering such corrected Deliverables to you. Any replacement Deliverables will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is the longer.
+
+ 
+
+EXCEPT AS PROVIDED ABOVE, YOU AGREE THAT THE DELIVERABLES ARE LICENSED “AS IS”, AND THAT ARM EXPRESSLY DISCLAIMS ALL REPRESENTATIONS, WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF NON- INFRINGEMENT, SATISFACTORY QUALITY, AND FITNESS FOR A PARTICULAR PURPOSE.
+
+ 
+
+YOU EXPRESSLY ASSUME ALL LIABILITIES AND RISKS, FOR USE OR OPERATION OF SOFTWARE APPLICATIONS, INCLUDING WITHOUT LIMITATION, APPLICATIONS DESIGNED OR INTENDED FOR MISSION CRITICAL APPLICATIONS, SUCH AS PACEMAKERS, WEAPONARY, AIRCRAFT NAVIGATION, FACTORY CONTROL SYSTEMS, ETC. SHOULD THE DELIVERABLES PROVE DEFECTIVE, YOU ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 
+
+6.  LIMITATION OF LIABILITY.
+
+TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL ARM BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING LOSS OF PROFITS) ARISING OUT OF THE USE OR INABILITY TO USE THE DELIVERABLES WHETHER BASED ON A CLAIM UNDER CONTRACT, TORT OR OTHER LEGAL THEORY, EVEN IF ARM WAS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+ARM does not seek to limit or exclude liability for death or personal injury arising from ARM's negligence or ARM's fraud and because some jurisdictions do not permit the exclusion or limitation of liability for consequential or incidental damages the above limitation relating to liability for consequential damages may not apply to you.
+
+ 
+
+NOTWITHSTANDING ANYTHING TO THE CONTRARY CONTAINED IN THIS LICENCE, THE MAXIMUM LIABILITY OF ARM TO YOU IN AGGREGATE FOR ALL CLAIMS MADE AGAINST ARM IN CONTRACT TORT OR OTHERWISE UNDER OR IN CONNECTION WITH THE SUBJECT MATTER OF THIS LICENCE SHALL NOT EXCEED THE GREATER OF; (I) THE TOTAL OF SUMS PAID BY YOU TO ARM (IF ANY) FOR THIS LICENCE; AND (II) $10 USD.
+
+THE EXISTENCE OF MORE THAN ONE CLAIM WILL NOT ENLARGE OR EXTEND THE LIMIT.
+
+ 
+
+7.  THIRD PARTY RIGHTS.
+
+The Separate Files are delivered subject to and your use is governed by their own separate licence agreements. This Licence does not apply to such Separate Files and they are not included in the term “Deliverables” under this Licence. You agree to comply with all terms and conditions imposed on you in respect of such Separate Files including those identified in the Schedule (“Third Party Terms”). 
+
+ 
+
+ARM HEREBY DISCLAIMS ANY AND ALL WARRANTIES EXPRESS OR IMPLIED FROM ANY THIRD PARTIES REGARDING ANY SEPARATE FILES, ANY THIRD PARTY MATERIALS INCLUDED IN THE DELIVERABLES, ANY THIRD PARTY MATERIALS FROM WHICH THE DELIVERABLES ARE DERIVED (COLLECTIVELY “OTHER CODE”), AND THE USE OF ANY OR ALL THE OTHER CODE IN CONNECTION WITH THE DELIVERABLES, INCLUDING (WITHOUT LIMITATION) ANY WARRANTIES OF SATISFACTORY QUALITY OR FITNESS FOR A PARTICULAR PURPOSE.
+
+ 
+
+NO THIRD PARTY LICENSORS OF OTHER CODE SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND WHETHER MADE UNDER CONTRACT, TORT OR OTHER LEGAL THEORY, ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE OTHER CODE OR THE EXERCISE OF ANY RIGHTS GRANTED UNDER EITHER OR BOTH THIS LICENCE AND THE LEGAL TERMS APPLICABLE TO ANY SEPARATE FILES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+ 
+
+8.  GOVERNMENT END USERS.
+
+US Government Restrictions: Use, duplication, reproduction, release, modification, disclosure or transfer of the Deliverables is restricted in accordance with the terms of this Licence.
+
+ 
+
+9.  TERM AND TERMINATION.
+
+This Licence shall remain in force until terminated by you or by ARM. Without prejudice to any of its other rights if you are in breach of any of the terms and conditions of this Licence then ARM may terminate this Licence immediately upon giving written notice to you. You may terminate this Licence at any time. Upon termination of this Licence by you or by ARM you shall stop using the Deliverables and confidential information and destroy all copies of the Deliverables and confidential information in your possession together with all documentation and related materials. Notwithstanding the foregoing, except where ARM has terminated this Licence for your breach, your rights to distribute the Example Code as part of Licensed Products developed prior to termination shall survive termination of this Licence, subject to the terms of this Licence. The provisions of Clauses 4, 6, 7, 8, 9 and 10 shall survive termination of this Licence.
+
+ 
+
+10.  GENERAL.
+
+This Licence is governed by English Law. Except where ARM agrees otherwise in; (i) a written contract signed by you and ARM; or (ii) a written contract provided by ARM and accepted by you, this is the only agreement between you and ARM relating to the Deliverables and it may only be modified by written agreement between you and ARM. This Licence may not be modified by purchase orders, advertising or other representation by any person. If any clause or sentence in this Licence is held by a court of law to be illegal or unenforceable the remaining provisions of this Licence shall not be affected thereby. The failure by ARM to enforce any of the provisions of this Licence, unless waived in writing, shall not constitute a waiver of ARM's rights to enforce such provision or any other provision of this Licence in the future.
+
+ 
+
+The Deliverables provided under this Licence are subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. You agree to comply fully with all laws and regulations of the United States and other countries (&quot;Export Laws&quot;) to assure that the Deliverables, are not (1) exported, directly or indirectly, in violation of Export Laws, either to any countries that are subject to U.S.A. export restrictions or to any end user who has been prohibited from participating in the U.S.A. export transactions by any federal agency of the U.S.A. government; or (2) intended to be used for any purpose prohibited by Export Laws, including, without limitation, nuclear, chemical, or biological weapons proliferation.
+
+ 
+
+To the extent that the provisions contained in this Licence conflict with any provisions of any other licence you have entered with ARM governing the Deliverables the provisions contained in this Licence shall prevail over and shall supersede any such conflicting provisions.  
+
+ 
+
+SCHEDULE
+
+h5{margin-top:0cm;text-align:justify}.  
+
+h5{margin-top:0cm;text-align:justify}. Part A
+
+*Hardware Binaries:*
+
+FPGA bitstream file for any or all of the Hardware Source identified below in this Part A
+
+ 
+
+*Software Binaries:*
+
+Motherboard configuration controller
+
+Daughterboard configuration controller
+
+Daughterboard Application note SelfTest
+
+SCP firmware
+
+Mali GPU Driver
+
+* *
+
+*Documentation:*
+
+Documentation, provided as PDF
+
+ 
+
+*Hardware Source:*
+
+Hardware netlists of the ARM CoreLink peripheral technology and components known as TLX-400, NIC-400, and PL330
+
+ 
+
+*Header Files:*
+
+Provided as part of and with the Mali GPU Driver
+
+ 
+
+*Part B*
+
+*Wrapper:*
+
+Application Note wrapper file provided as hardware source files and netlists.
+
+ 
+
+*Part C: Example Code*
+
+(i)            Platform specific libraries and source code.
+
+(ii)           ARM source code of Application note SelfTest.
+
+* *
+
+*Part D: Separate Files*
+
+ 
+
+A.     UEFI firmware, including drivers for third party components licensed to you under BSD 3-Clause.
+
+ 
+
+B.     Linux kernel licensed to you under the GNU General Public License version 2.0
+
+ 
+
+To the extent that ARM is obliged to do so, ARM hereby offers to supply the files which are subject to the GNU General Public Licence version 2 (identified above), in source code form, subject to the terms of the GNU General Public License version 2, upon request. This offer is valid for three (3) years from the date of your acceptance of this Licence.
+
+ 
+
+C.    AP Trusted Firmware licensed to you under BSD 3-Clause.
+
+ 
+
+D.    ARM Gator Profile driver and daemon licensed to you under the GNU General Public License version 2.0
+
+ 
+
+To the extent that ARM is obliged to do so, ARM hereby offers to supply the files which are subject to the GNU General Public Licence version 2 (identified above), in source code form, subject to the terms of the GNU General Public License version 2, upon request. This offer is valid for three (3) years from the date of your acceptance of this Licence.
+
+ 
+
+/end
+
+ 
+
+ARM contract references: LES-PRE-20435 JUNO ARM DEVELOPMENT PLATFORM DELIVERABLES  
diff --git a/openembedded/juno-lsk/FIRMWARE.textile b/openembedded/juno-lsk/FIRMWARE.textile
new file mode 100644
index 0000000..bb54dd9
--- /dev/null
+++ b/openembedded/juno-lsk/FIRMWARE.textile
@@ -0,0 +1,151 @@
+h2. Disclaimer
+
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-5.
+
+*Getting Started Tab*
+
+ 
+
+*Juno ports*
+
+ 
+
+*Back panel*
+
+!Linaro_Release_Notes_v1_files/image001.png!
+
+*Front panel*
+
+!Linaro_Release_Notes_v1_files/image002.png!
+
+There are 4 UARTs on the Juno board:
+
+<table>
+<col width="20%" />
+<col width="20%" />
+<col width="20%" />
+<col width="20%" />
+<col width="20%" />
+<tbody>
+<tr class="odd">
+<td align="left"> 
+
+SoC UART0
+
+SoC UART1
+
+FPGA UART0
+
+FPGA UART1
+</td>
+<td align="left">Location
+
+"back panel":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel, top slot.
+
+"back panel":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel, bottom slot.
+
+Corresponds to the J55 header on the board. Please contact ARM for more information about this type of header.
+
+Corresponds to J56 header on the board. Please contact ARM for more information about this type of header
+</td>
+<td align="left">Used by
+
+The motherboard, UEFI and the Linux kernel.
+
+SCP firmware
+
+AP Trusted Firmware
+
+Unused at the moment
+</td>
+<td align="left">Baud
+
+115200
+
+115200
+
+115200
+
+-
+</td>
+<td align="left">Data bits
+
+8
+
+8
+
+8
+
+-
+</td>
+</tr>
+</tbody>
+</table>
+
+ 
+
+*Quick Start*
+
+If you have just unpacked a new Juno board and would like to get it booting straight away, you may wish to skip ahead to the “Set up and boot the Juno board” section.  &lt;make this a link&gt;
+
+ 
+
+*Juno software stack overview*
+
+There are several pieces of software that make up the complete Juno software stack, and a description of each one follows below.
+
+*Juno MCC Microcontroller Firmware*
+
+The MCC is a microcontroller on the motherboard that takes care of early setup before the SCP or applications processors are powered on. The MCC is also responsible for managing firmware upgrades.
+
+*System Control Processor (SCP) Firmware*
+
+The Juno System Control Processor (SCP) is an on-chip Cortex-M3 that provides low level power management and system control for the Juno platform.
+
+*Application Processor (AP) Trusted Firmware*
+
+The Juno AP Trusted Firmware provides low-level Trusted World support for the Juno platform.
+
+*Unified Extensible Firmware Interface (UEFI)*
+
+The Juno UEFI implementation provides Linux loader support for the Juno platform. It is based on the open source EFI Development Kit 2 (EDK2) implementation from the Tianocore sourceforge project.
+
+*Linux Kernel*
+
+The Linaro Stable Kernel (LSK) for Juno.
+
+*Linux filesystem*
+
+An Openembedded filesystem from Linaro can be mounted via USB (recommended) or NFS over Ethernet.
+
+*Android kernel and AOSP*
+
+The LSK image contains Android patches and has a unified defconfig, so the same kernel binary will work with a Linux filesystem or an AOSP filesystem (available from Linaro).
+
+ 
+
+*Software preloaded on new Juno boards*
+
+New Juno boards arrive preloaded with MCC firmware, SCP firmware, AP trusted firmware, UEFI, and a Linux kernel. The Juno board does not contain a Linux filesystem anywhere in onboard storage.
+
+*Please note* that early batches of Juno boards contained an SCP firmware image that limits the CPU clock to 50 MHz. ARM strongly recommends that you immediately upgrade to the latest "firmware image":http://community.arm.com/docs/DOC-8396#jive_content_id_Juno_Board_Recovery_Image hosted on this website.  &lt;link should point to firmware tab&gt;
+
+When the power is first turned on, it should boot straight through to Linux. UEFI offers a 10 second window during which you can interrupt the boot sequence by pressing a key on the serial terminal, otherwise the Linux kernel will be launched. In order to reach the Linux shell you must attach a Linux "filesystem":http://community.arm.com/docs/DOC-8396#jive_content_id_Deploying_a_root_filesystem via USB. If no filesystem is attached then Linux will boot as far as it can and then announce that it is waiting for a filesystem to be attached.
+
+New Juno boards do not contain any Android software pre-installed.
+
+ 
+
+*Set up and boot the Juno board*
+
+You are strongly recommended to update to the latest firmware before doing anything productive with your Juno board.
+
+The steps to set up and boot the board are:
+
+# Connect a serial terminal to the "UART0":http://community.arm.com/docs/DOC-8396#jive_content_id_Setting_up_the_board connector ("settings":http://community.arm.com/docs/DOC-8396#jive_content_id_Setting_up_the_board). &lt;UART0 link should point to the back panel picture, settings link should point to the UART table below it&gt;
+# Connect the 12 volt power, then press the red "ON/OFF button":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel on the back panel. &lt;link should point to the back panel picture&gt;
+
+*Getting Juno to boot to the Linux shell*
+
+If you have just received a new board and powered it on for the first time, you will not reach the Linux shell. Juno will boot Linux to the point where it looks for a filesystem, and when it can't find one it will sit and wait for one to be attached. To boot all the way to the Linux shell you will need to "attach a root filesystem":http://community.arm.com/docs/DOC-8396#jive_content_id_Deploying_a_root_filesystem.  &lt;the link should point to the relevant section in the “Binary Image Installation” tab&gt;
+
diff --git a/openembedded/juno-lsk/HACKING.textile b/openembedded/juno-lsk/HACKING.textile
new file mode 100644
index 0000000..2968e94
--- /dev/null
+++ b/openembedded/juno-lsk/HACKING.textile
@@ -0,0 +1,55 @@
+h2. Disclaimer
+
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-5.
+
+h2. Building the Linaro Kernel
+
+h3. Prerequisites
+
+* Ubuntu 12.04 64 bit system. You can download Ubuntu from ubuntu.com
+* git
+
+bc. sudo apt-get install build-essential git
+
+* toolchain
+
+bc. mkdir -p ~/bin
+cd ~/bin
+wget http://releases.linaro.org/13.11/components/toolchain/binaries/gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux.tar.xz
+tar xf gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux.tar.xz
+PATH=$PATH:~/bin/gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux/bin
+
+h3. Get the Linaro Kernel Source
+
+bc. git clone https://git.linaro.org/landing-teams/working/arm/kernel-release.git
+cd kernel
+git checkout <release tag>
+
+h3. Create a kernel config
+
+Do not use the arm64 defconfig, instead, build a config from the config fragments that Linaro provides:
+
+bc. ARCH=arm64 scripts/kconfig/merge_config.sh \
+linaro/configs/linaro-base.conf \
+linaro/configs/distribution.conf \
+linaro/configs/vexpress64.conf \
+
+Note: the config fragments are part of the git repository and the source tarball.
+
+h3. Build the kernel
+
+To build the kernel Image and juno.dtb files, use the following command:
+
+bc. make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- Image dtbs
+
+h3. Install your kernel
+
+Copy the kernel Image and the juno.dtb files to the BOOT partition on the USB drive created in the "Binary Installation tab":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-2.
+
+bc. cp arch/arm64/boot/Image /media/BOOT/Image
+cp arch/arm64/boot/dts/juno.dtb /media/BOOT/juno/juno.dtb
+
+h2. Building UEFI
+
+To rebuild the UEFI binaries, see the "UEFI Wiki":https://wiki.linaro.org/LEG/Engineering/Kernel/UEFI and specifically the "UEFI build page":https://wiki.linaro.org/LEG/Engineering/Kernel/UEFI/build.
+
diff --git a/openembedded/juno-lsk/INSTALL.textile b/openembedded/juno-lsk/INSTALL.textile
new file mode 100644
index 0000000..6f419b7
--- /dev/null
+++ b/openembedded/juno-lsk/INSTALL.textile
@@ -0,0 +1,99 @@
+h2. Disclaimer
+
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-5.
+
+h2. Installation
+
+Linaro OpenEmbedded releases are made up of the following components.
+
+| *.img.gz | pre-built images for minimal, LAMP and LEG root filesystems |
+| hwpack_*.tar.gz | hardware pack |
+| linaro-image-*.rootfs.tar.gz | a choice of Root file system (RootFS) images |
+| Image | kernel used by UEFI |
+| juno_bl1.bin | ARM Trused Firmware BL1 binary |
+| juno_fip.bin | ARM Trused Firmware Firmware Image Package (FIP) binary |
+| juno.dtb | Device Tree Binary |
+
+Other files such as *.manifest, *.txt and *.html provide information such as package contents or MD5SUMs about the files they share a common filename with.
+
+Linaro OpenEmbedded images are made up of two components. The "Hardware Pack":https://wiki.linaro.org/HardwarePacks, which contains the kernel, boot loader and/or Device Tree blob and a Root file system (RootFS) of your choice to generate an image.
+
+Linaro provides two methods for installing Linaro binary builds:
+
+# Using a pre-built image, which you can download
+# Assembling your own image using provided components
+
+h2. Pre-Installation Steps
+
+Before any installation begins, it is important that you ensure your board has the latest firmware installed. Please check the "Firmware Update tab":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-4 on this page for the latest updates and installation instructions.  The 14.06 release has been tested with Firmware version 0.7.1, but we always recommend that users install the latest version available.
+
+h2. Using pre-built image
+
+h3. Prerequisites
+
+* Ubuntu 12.04 64 bit or newer on your desktop PC ("www.ubuntu.com":http://www.ubuntu.com)
+* 2GB USB drive or larger
+* Latest firmware installed onto the board. Please see "Firmware Update tab":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-4.
+* Download the pre-built image for this release
+bc. wget http://releases.linaro.org/14.06/openembedded/juno-lsk/*minimal*.img.gz
+
+h3. Installation Steps
+
+* Unzip the downloaded pre-built image
+* Insert USB drive into your PC and note the assigned @'/dev/sdX'@
+
+bc. dmesg
+DISK=/dev/sdX # USB drive found from dmesg above
+zcat http://releases.linaro.org/14.06/openembedded/juno-lsk/*minimal*.img.gz | sudo dd bs=64k of=$DISK
+
+When the image is created, skip down to the section "Booting the image".
+
+*Note:* Windows users may use the "Image Writer for Windows.":https://launchpad.net/win32-image-writer/+download
+
+<hr>
+
+h2. Building a custom image using pre-built components
+
+Sometimes, you may wish to build your own custom image for a board. Perhaps you wish to use a more recent snapshot of the "hardware pack":https://wiki.linaro.org/HardwarePacks or take the latest Android build. Whatever the reason, you will want to use the "Linaro Image Tools":https://wiki.linaro.org/Linaro-Image-Tools to create a custom image.
+
+Using components to generate the image will yield the same functionality found in the pre-built image of the same release.
+
+h3. Prerequisites
+
+* Ubuntu 12.04 64 bit or newer on your desktop PC ("www.ubuntu.com":http://www.ubuntu.com)
+* Download Artifacts from above
+* Get "Linaro image tools":https://wiki.linaro.org/Linaro-Image-Tools. There are multiple ways you can get the latest Linaro Image Tools:
+
+** Method 1: Install them from the Linaro Image Tools "PPA":https://launchpad.net/~linaro-maintainers/+archive/tools
+
+bc. sudo add-apt-repository ppa:linaro-maintainers/tools
+sudo apt-get update
+sudo apt-get install linaro-image-tools
+
+** Method 2: Building from source
+
+bc. wget http://releases.linaro.org/14.06/components/platform/linaro-image-tools/linaro-image-tools-2014.06.tar.gz
+
+* Insert USB drive and note the assigned @'/dev/sdX'@ or @'/dev/mmcblk0'@
+
+bc. dmesg | less
+
+Look for a line that looks like the following at the end of the log
+
+@[288582.790722] sdc: sdc1 sdc2 sdc3 sdc4 <sdc5 sdc6 >@
+
+Or, if your machine uses '/dev/mmcblkX', you may see a line line this:
+
+@[10770.938042]  mmcblk0: p1 p2 p3 p4 < p5 p6 >@
+
+*WARNING:* In the next step, make sure you use /dev/"whatever you see above". *You can erase your hard drive* with the wrong parameter.
+
+* Create media
+
+bc. sudo linaro-media-create --mmc /dev/sdX --dev juno --hwpack <hwpack filename> --binary <rootfs filename>
+
+h2. Booting the image
+
+After the media create tool has finished executing, remove the USB drive from your PC and insert it into the board.
+
+Before you can boot the image you will need to install the latest firmware on the board. The instructions on the Firmware Update tab provide information on how to do this and how to configure UEFI to specify the USB drive as a boot device.
diff --git a/openembedded/juno-lsk/README.textile b/openembedded/juno-lsk/README.textile
new file mode 100644
index 0000000..e0550d0
--- /dev/null
+++ b/openembedded/juno-lsk/README.textile
@@ -0,0 +1,114 @@
+* *
+
+*License*
+
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-5.
+
+* *
+
+*About Juno*
+
+Juno is the first 64-bit development platform from ARM, featuring a dual Cortex-A57 &quot;big&quot; cluster, a quad Cortex-A53 &quot;little&quot; cluster, and a Mali T624 GPU cluster with four shader cores.
+
+This board is lead-free (it does not contain Pb).
+
+ 
+
+h1. About the Linaro Stable Kernel (LSK)
+
+The Linaro Stable Kernel (LSK) is produced, validated and released by Linaro and is based on the linux stable kernel tree. The LSK focuses on quality and stability and is therefore a great foundation for product development. It also includes backports of commonly desired features, provided they meet the quality requirements, and also any bug fixes.
+
+LSK releases appear monthly. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/14.06/openembedded/vexpress-lsk/#tabs-3 tab).  &lt;link should point to the “building from sources” tab&gt;
+
+ 
+
+*Support*
+
+Please send any support enquiries to "juno-support&#64;arm.com":mailto:juno-support@arm.com?subject=Juno%20support%20request
+
+ 
+
+*Functionality in this release*
+
+The current release supports the following:
+
+* Full cold boot support to Linux shell or Android homescreen
+* Multicore support in Linux, all six CPUs enabled.
+* Experimental big.LITTLE support, disabled by default but can be "enabled":http://community.arm.com/docs/DOC-8664#biglittleenable.  &lt;link should point to “enabling big.LITTLE” in the “building from source” tab&gt;
+* Full USB driver support in Linux, for access to mass storage and input devices.
+* There is no GPU support for Linux in this release.
+* GPU support in Android, functional but *not performant*. The performance issues will be addressed in the next release.
+* HDLCD is fully supported, but is not performant on Android. This will be addressed in the next release.
+* Thermal protection is enabled. If the SoC reaches 85C it will shut down. Linux will receive a warning at 75C.
+* Stable operating points are enabled for nominal (Cortex-A57 800MHz, Cortex-A53 700MHz, Mali T624 600MHz) and overdrive (Cortex-A57 1100MHz, Cortex-A53 850MHz).
+* DVFS is supported in the SCP firmware and the Linux CPUFreq driver.
+* Android patches and defconfig have been merged to unify the Linux and Android kernels.
+* There is no idle power management support in this release.
+* There is no PCIe support in this release.
+
+*Functionality listed by software component*
+
+*SCP Firmware*
+
+* System configuration
+* DDR initialization
+* Basic power state management
+* SCPI commands (Ready, Set/Get Clocks, Set/Get CPU power states)
+* Thermal protection (shutdown at 85C)
+* DVFS support
+
+*AP Trusted Firmware*
+
+* Send the SCP firmware to SCP
+* Initialize the Trusted World before transitioning into Normal World.
+* Service CPU hotplug requests coming from Normal World
+
+*UEFI*
+
+* Booting an Operating System from NOR Flash or USB mass storage
+* Support for Ethernet and PXE boot
+
+*Linux Kernel*
+
+* Enable Juno Compute Subsystem comprised of a dual A57 core cluster and a quad A53 core cluster.
+* Enable a limited set of peripherals present on the Juno development board: on-chip USB, non-secure UART, HDMI output, keyboard and mouse functionality over PS/2 connector, Ethernet support via on-board SMSC ethernet chip.
+* Experimental big.LITTLE support
+* Unified kernel and kernel config for Android and Linux.
+
+ 
+
+*Limitations listed by software component*
+
+*SCP Firmware*
+
+* A number of SCPI commands are not yet implemented or are incomplete.
+
+*AP Trusted Firmware*
+
+* Does not support changing the primary core using SCC General Purpose Register 1.
+* Does not support bringing up secondary cores using PSCI CPU&#95;ON when they have been enabled at boot time by SCP using SCC General Purpose Register 1.
+* Does not support Secure-EL1 Payload (i.e. BL3-2)
+* Does not support CPU suspend
+
+*UEFI*
+
+* No PCI Express support included
+* No display controller support
+* No low and full speed USB support
+
+*Linux Kernel*
+
+* No PCI Express support included
+* No support for MALI graphics
+* big.LITTLE support is experimental and there are no guarantees of performance. This support is disabled by default and must be "enabled":http://community.arm.com/docs/DOC-8664#biglittleenable before it can be used.
+
+ 
+
+h2. Resolved in this release
+
+h2. This is the initial release.
+
+h2. Known Issues
+
+&lt;insert list of Juno bugs tracked by landing team&gt;
+
diff --git a/openembedded/vexpress-lsk/INSTALL.textile b/openembedded/vexpress-lsk/INSTALL.textile
index fa9803c..5b5df5c 100644
--- a/openembedded/vexpress-lsk/INSTALL.textile
+++ b/openembedded/vexpress-lsk/INSTALL.textile
@@ -7,7 +7,7 @@ Linaro provides two methods for installing Linaro binary builds:
 
 h2. Pre-Installation Steps
 
-Before any installation begins, it is important that you ensure you Versatile Express board has the latest firmware and boot loader installed. Please check the "Firmware Update" tab on this page for the latest updates and installation instructions.
+Before any installation begins, it is important that you ensure your Versatile Express board has the latest firmware and boot loader installed. Please check the "Firmware Update" tab on this page for the latest updates and installation instructions.
 
 h2. Using pre-built image
 
@@ -82,5 +82,5 @@ h2. Booting the image
 
 After the media create tool has finished executing, remove the SD card from your PC and insert it into the Versatile Express board.
 
-Before you can boot the image you will need to install the UEFI boot loader into NOR flash and update the Versatile MMC card configuration files. The instructions on the Firmware Update tab provide information on how to do this and how to configure UEFI to specify the SD card as a boot device.
+Before you can boot the image you will need to install the UEFI boot loader into NOR flash and update the Versatile Express motherboard's configuration files. The instructions on the Firmware Update tab provide information on how to do this and how to configure UEFI to specify the SD card as a boot device.