summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRyan Harkin <ryan.harkin@linaro.org>2015-07-27 14:59:43 +0100
committerRyan Harkin <ryan.harkin@linaro.org>2015-07-27 14:59:46 +0100
commit4c2b323eee0cc0a99e4bfc2de687c2c90b81a479 (patch)
tree73a19ed096133f9d7338ba8e9ac80ca7e65a74e6
parent3d7a7f37cae4a95858b9f7cc4d1c2112839be58b (diff)
15.07: oe: fix 15.06 refs to 15.07
note: the date has moved within the URL: < releases.linaro.org/YY.MM/<something>/ > releases.linaro.org/<something>/YY.MM/ Change-Id: Ib793f58aaf8f2fd57a0cdd4762c6fc109c97b39e Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>
-rw-r--r--members/arm/openembedded/aarch64/HACKING.textile6
-rw-r--r--members/arm/openembedded/aarch64/README.textile4
-rw-r--r--members/arm/openembedded/juno-lsk/GETTINGSTARTED.textile8
-rw-r--r--members/arm/openembedded/juno-lsk/HACKING.textile6
-rw-r--r--members/arm/openembedded/juno-lsk/INSTALL.textile6
-rw-r--r--members/arm/openembedded/juno-lsk/README.textile4
-rw-r--r--members/arm/openembedded/vexpress-lsk/HACKING.textile4
-rw-r--r--members/arm/openembedded/vexpress-lsk/README.textile6
8 files changed, 22 insertions, 22 deletions
diff --git a/members/arm/openembedded/aarch64/HACKING.textile b/members/arm/openembedded/aarch64/HACKING.textile
index fae870a..08e12db 100644
--- a/members/arm/openembedded/aarch64/HACKING.textile
+++ b/members/arm/openembedded/aarch64/HACKING.textile
@@ -4,9 +4,9 @@ h3. Initial setup
bc. mkdir openembedded
cd openembedded
-git clone git://git.linaro.org/openembedded/jenkins-setup.git
+git clone http://git.linaro.org/openembedded/jenkins-setup.git
cd jenkins-setup
-git checkout release-15.06
+git checkout master
cd ..
sudo bash jenkins-setup/pre-build-root-install-dependencies.sh
bash jenkins-setup/init-and-build.sh
@@ -75,7 +75,7 @@ Create the Device Tree blob if you don’t have one in your Linaro image:
bc. make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- dtbs
-Copy the kernel and the DTB file for your model to your fastmodel directory created in the "Binary Installation tab":https://releases.linaro.org/15.06/openembedded/aarch64/#tabs-2.
+Copy the kernel and the DTB file for your model to your fastmodel directory created in the "Binary Installation tab":https://releases.linaro.org/members/arm/openembedded/aarch64/15.07/#tabs-2.
bc. cp arch/arm64/boot/Image <fastmodel dir>
cp arch/arm64/boot/dts/*.dtb <fastmodel dir>
diff --git a/members/arm/openembedded/aarch64/README.textile b/members/arm/openembedded/aarch64/README.textile
index a77dc26..fe39aae 100644
--- a/members/arm/openembedded/aarch64/README.textile
+++ b/members/arm/openembedded/aarch64/README.textile
@@ -1,4 +1,4 @@
-h1. AArch64 OpenEmbedded ARM Fast Models 15.06 Release
+h1. AArch64 OpenEmbedded ARM Fast Models 15.07 Release
The AArch64 Open Embedded Engineering Build for "ARM Fast Models":http://www.arm.com/fvp for ARMv8 is produced, validated and released by Linaro, based on the latest AArch64 open source software from "Tianocore EDK2":http://sourceforge.net/apps/mediawiki/tianocore (UEFI), the "Linux kernel":http://kernel.org, "ARM Trusted Firmware":http://github.com/ARM-software/arm-trusted-firmware and OpenEmbedded. It is produced to enable software development for AArch64 prior to hardware availability, and facilitates development of software that is independent of the specific CPU implementation. This build focuses on availability of new features in order to provide a basis for ongoing and dependent software development.
@@ -17,7 +17,7 @@ This build has been tested to work on the following FVPs:
* FVP_Base_Cortex-A57x4-A53x4
* FVP_Base_Cortex-A57x1-A53x1
-The Foundation_v8 FVP is free to use (download from ARM "http://www.arm.com/fvp":http://www.arm.com/fvp), while the others are licensed from ARM. "More information":https://releases.linaro.org/15.06/openembedded/aarch64/#tabs-4 on these specific FVPs is included with this release documentation.
+The Foundation_v8 FVP is free to use (download from ARM "http://www.arm.com/fvp":http://www.arm.com/fvp), while the others are licensed from ARM. "More information":https://releases.linaro.org/members/arm/openembedded/aarch64/15.07/#tabs-4 on these specific FVPs is included with this release documentation.
The Base and Foundation FVPs use the following software for boot and runtime firmware services in this engineering build:
* ARM Trusted Firmware provides a reference implementation of secure world software for ARMv8-A, including Exception Level 3 (EL3) software
diff --git a/members/arm/openembedded/juno-lsk/GETTINGSTARTED.textile b/members/arm/openembedded/juno-lsk/GETTINGSTARTED.textile
index 8798973..3db1b68 100644
--- a/members/arm/openembedded/juno-lsk/GETTINGSTARTED.textile
+++ b/members/arm/openembedded/juno-lsk/GETTINGSTARTED.textile
@@ -1,6 +1,6 @@
h2. License
-The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/15.06/members/arm/openembedded/juno-lsk/#tabs-5.
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/members/arm/openembedded/juno-lsk/15.07/#tabs-5.
h2. Juno ports
@@ -68,9 +68,9 @@ h3. 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 or Android AOSP 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 hosted on this website by following the instructions in the section titled "Firmware update" on the "Binary Image Installation tab":https://releases.linaro.org/15.06/members/arm/openembedded/juno-lsk/#tabs-2.
+*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 hosted on this website by following the instructions in the section titled "Firmware update" on the "Binary Image Installation tab":https://releases.linaro.org/members/arm/openembedded/juno-lsk/15.07/#tabs-2.
-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":https://releases.linaro.org/15.06/members/arm/openembedded/juno-lsk/#tabs-2 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.
+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":https://releases.linaro.org/members/arm/openembedded/juno-lsk/15.07/#tabs-2 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.
@@ -87,7 +87,7 @@ The steps to set up and boot the board are:
h3. 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":https://releases.linaro.org/15.06/members/arm/openembedded/juno-lsk/#tabs-2.
+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":https://releases.linaro.org/members/arm/openembedded/juno-lsk/15.07/#tabs-2.
h3. Setting the Real Time Clock (required for Android)
diff --git a/members/arm/openembedded/juno-lsk/HACKING.textile b/members/arm/openembedded/juno-lsk/HACKING.textile
index bcaec00..6f13e13 100644
--- a/members/arm/openembedded/juno-lsk/HACKING.textile
+++ b/members/arm/openembedded/juno-lsk/HACKING.textile
@@ -1,6 +1,6 @@
h2. License
-The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/15.06/members/arm/openembedded/juno-lsk/#tabs-5.
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/members/arm/openembedded/juno-lsk/15.07/#tabs-5.
h2. Building the Linaro Kernel
@@ -44,7 +44,7 @@ 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/15.06/members/arm/openembedded/juno-lsk/#tabs-2.
+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/members/arm/openembedded/juno-lsk/15.07/#tabs-2.
bc. cp arch/arm64/boot/Image /media/BOOT/Image
cp arch/arm64/boot/dts/juno.dtb /media/BOOT/juno/juno.dtb
@@ -289,4 +289,4 @@ bc. $ fip_create --help
h2. Installing the binaries
-Please refer to the section titled "Firmware update" on the "Binary Image Installation tab":https://releases.linaro.org/15.06/members/arm/openembedded/juno-lsk/#tabs-2.
+Please refer to the section titled "Firmware update" on the "Binary Image Installation tab":https://releases.linaro.org/members/arm/openembedded/juno-lsk/15.07/#tabs-2.
diff --git a/members/arm/openembedded/juno-lsk/INSTALL.textile b/members/arm/openembedded/juno-lsk/INSTALL.textile
index 8a0e156..f32696d 100644
--- a/members/arm/openembedded/juno-lsk/INSTALL.textile
+++ b/members/arm/openembedded/juno-lsk/INSTALL.textile
@@ -1,6 +1,6 @@
h2. License
-The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/15.06/members/arm/openembedded/juno-lsk/#tabs-5.
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/members/arm/openembedded/juno-lsk/15.07/#tabs-5.
h2. Installation
@@ -137,7 +137,7 @@ The example below shows how a test system was configured. Please note: some of
Also take care that the USB partitions are showing in the menu before selecting a menu option. There is a known bug in UEFI where the partitions on USB drives may not show the first time the menu is displayed. To overcome this, as shown in the example below, the user should enter the menu option @"[1] Add Boot Device Entry"@, by pressing @1@ followed by the enter key. Then, when the list display and the USB partitions are missing, please press the @ESC@ key once. This will exit out of the current menu prompt and leave you back at the Boot Menu again. At this point, please press 1 again to re-enter the menu option @"[1] Add Boot Device Entry"@ and continue by selecting the partition named "boot" on the USB drive.
-UEFI outputs to UART0 on the board. UART0 uses 115200 baud with 8 bits and no stop bit. Please see the "UARTs" section on the "Getting Started tab":https://releases.linaro.org/15.06/members/arm/openembedded/juno-lsk/#tabs-4 for more details on the UART configuration of the board.
+UEFI outputs to UART0 on the board. UART0 uses 115200 baud with 8 bits and no stop bit. Please see the "UARTs" section on the "Getting Started tab":https://releases.linaro.org/members/arm/openembedded/juno-lsk/15.07/#tabs-4 for more details on the UART configuration of the board.
h3. Example UEFI Configuration
@@ -325,7 +325,7 @@ The configuration flash memory should now be visible on the host computer as a m
7. Extract the board recovery image ("board_recovery_image.tar.bz2":https://git.linaro.org/arm/vexpress-firmware.git/blob/bb4ca8b261484b8775b524bc9ab3af74598306fb:/board_recovery_image.tar.bz2) to the root directory of the configuration flash memory, preserving the directory structure.
-8. If you are performing a system recovery or installing an update from ARM then skip to step 9. Otherwise if you wish to install firmware images that you have "built yourself":https://releases.linaro.org/15.06/members/arm/openembedded/juno-lsk/#tabs-3 then delete the bl1.bin and fip.bin from the /SOFTWARE/ directory in the configuration flash memory, and copy your own bl1.bin and fip.bin images into that directory to replace them.
+8. If you are performing a system recovery or installing an update from ARM then skip to step 9. Otherwise if you wish to install firmware images that you have "built yourself":https://releases.linaro.org/members/arm/openembedded/juno-lsk/15.07/#tabs-3 then delete the bl1.bin and fip.bin from the /SOFTWARE/ directory in the configuration flash memory, and copy your own bl1.bin and fip.bin images into that directory to replace them.
9. Safely eject the mass storage device, giving it time to write the files to the internal storage.
diff --git a/members/arm/openembedded/juno-lsk/README.textile b/members/arm/openembedded/juno-lsk/README.textile
index ef265d1..9554920 100644
--- a/members/arm/openembedded/juno-lsk/README.textile
+++ b/members/arm/openembedded/juno-lsk/README.textile
@@ -22,11 +22,11 @@ h2. 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/15.06/members/arm/openembedded/juno-lsk/#tabs-3 tab).
+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/members/arm/openembedded/juno-lsk/15.07/#tabs-3 tab).
h2. License
-The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/15.06/members/arm/openembedded/juno-lsk/#tabs-5.
+The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/members/arm/openembedded/juno-lsk/15.07/#tabs-5.
h2. Support
diff --git a/members/arm/openembedded/vexpress-lsk/HACKING.textile b/members/arm/openembedded/vexpress-lsk/HACKING.textile
index 289a13a..23cb9dd 100644
--- a/members/arm/openembedded/vexpress-lsk/HACKING.textile
+++ b/members/arm/openembedded/vexpress-lsk/HACKING.textile
@@ -13,9 +13,9 @@ h2. Get the source
You can use GIT to obtain the kernel source code for this release:
-bc. git clone git://git.linaro.org/kernel/linux-linaro-stable.git
+bc. git clone http://git.linaro.org/kernel/linux-linaro-stable.git
cd linux-linaro-stable
-git checkout lsk-v3.10-15.06
+git checkout lsk-v3.10-15.07
h3. Create a kernel config
diff --git a/members/arm/openembedded/vexpress-lsk/README.textile b/members/arm/openembedded/vexpress-lsk/README.textile
index 9958e0f..83c0095 100644
--- a/members/arm/openembedded/vexpress-lsk/README.textile
+++ b/members/arm/openembedded/vexpress-lsk/README.textile
@@ -1,4 +1,4 @@
-h1. Linaro Stable Kernel (LSK) 15.06 Release for Versatile Express (OpenEmbedded)
+h1. Linaro Stable Kernel (LSK) 15.07 Release for Versatile Express (OpenEmbedded)
p. The Linaro Stable Kernel (LSK) is produced, validated and released by Linaro and is based on the linux stable kernel tree. It is produced to satisfy the requirements of Linaro members. The LSK focuses on quality and stability and is therefore a great basis for member products. It also includes backports of commonly desired features, provided they meet the quality requirements, and also any bug fixes.
@@ -6,7 +6,7 @@ p. Linaro releases monthly binary images for the ARM "Versatile Express":http://
p. For support matters related to ARM hardware or firmware images downloaded from ARM sites, please contact "ARM support":mailto:support@arm.com
-p. This release includes Linaro OpenEmbedded for both Versatile Express and Fast Models. The images are able to boot A5, A9 and TC2 using UEFI. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/15.06/members/arm/openembedded/vexpress-lsk/#tabs-3 tab).
+p. This release includes Linaro OpenEmbedded for both Versatile Express and Fast Models. The images are able to boot A5, A9 and TC2 using UEFI. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/members/arm/openembedded/vexpress-lsk/15.07/#tabs-3 tab).
h2. About the TC2 Engineering Build
@@ -16,7 +16,7 @@ The TC2 CoreTile is the first example of a big.LITTLE system shipped by ARM and
The release contains the big.LITTLE MP patchset developed by ARM. This patchset is hosted by Linaro and can be found in the linked "git repository":https://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=shortlog;h=refs/heads/big-LITTLE-MP-latest. These patches have been developed and rigorously tested in order to enable the ARM Versatile Express V2P-CA15_A7 CoreTile (TC2) to run in full MP mode. This functionality has been optimised for energy and performance bringing it close to the Cortex-A7 (LITTLE) in energy consumption with near Cortex-A15 (big) performance. The patchset also includes optimizations that provide a considerable performance uplift across a wide range of benchmarks. The functionality introduced by this patchset is stable and ready for use on other platforms. Note that at present this LSK release is the reference point for big.LITTLE MP functionality.
-The patches in the big.LITTLE MP patchset are generic and applicable to big.LITTLE systems with minimal porting effort. To ease porting, the patches are also available as an isolated package located "here":https://wiki.linaro.org/ARM/VersatileExpress?action=AttachFile&do=get&target=big-LITTLE-MP-scheduler-patchset-15.06-lsk.tar.bz2. This package may be used directly by partners interested in porting the big.LITTLE MP scheduler functionality to their custom platform. Please contact "ARM support":mailto:support-sw@arm.com?subject=Query%20about%20ARM%20big.LITTLE%20MP%20patchset%20package in case of any queries related to this package.
+The patches in the big.LITTLE MP patchset are generic and applicable to big.LITTLE systems with minimal porting effort. To ease porting, the patches are also available as an isolated package located "here":https://wiki.linaro.org/ARM/VersatileExpress?action=AttachFile&do=get&target=big-LITTLE-MP-scheduler-patchset-15.07-lsk.tar.bz2. This package may be used directly by partners interested in porting the big.LITTLE MP scheduler functionality to their custom platform. Please contact "ARM support":mailto:support-sw@arm.com?subject=Query%20about%20ARM%20big.LITTLE%20MP%20patchset%20package in case of any queries related to this package.
Also provided is optional configurable kernel support for an implementation of ARM's Power State Co-ordination Interface (PSCI). This support is disabled by default. To use PSCI support you will require secure firmware that is currently available to ARM licensees upon request to ARM. Please contact "ARM support":mailto:support-sw@arm.com?subject=Access%20to%20PSCI to get access to the firmware code.