Switch to own builds S3 bucket

Author: philip-linaro

_posts/2015-11-07-15-10-alpha.md

@@ -41,7 +41,7 @@ LINK REMOVED
 
 A lot was accomplished during last month, and we're happy to announce that we're using a 4.3 based kernel for both HiKey and Dragonboard410c (Debian). The builds are still not sharing the same branch (due conflicts at the adv7511 driver), but we hope to be able to get this fixed over the next few weeks (and published as part of our next release).
 
-While the release supports many of the available hardware features for both Hikey and Dragonboard410c, it is in ALPHA state, so bugs are expected. For a better user experience, please use the previous releases available at [https://builds.96boards.org/releases/dragonboard410c/](https://builds.96boards.org/releases/dragonboard410c/) and [https://builds.96boards.org/releases/hikey/](https://builds.96boards.org/releases/hikey/).
+While the release supports many of the available hardware features for both Hikey and Dragonboard410c, it is in ALPHA state, so bugs are expected. For a better user experience, please use the previous releases available at [https://builds.96boards.org/dragonboard410c/](https://builds.96boards.org/dragonboard410c/) and [https://builds.96boards.org/hikey/](https://builds.96boards.org/hikey/).
 
 **Highlights for this release:**
 

_posts/2015-12-16-servo-motor-control.md

@@ -39,7 +39,7 @@ In order the be able to execute the Cobalt co-kernel, the Linux kernel needs to
 " The I-pipe inserts itself between the interrupt-management hardware and Linux. Any attempt from any Linux component to disable interrupts results in Linux's I-pipe stage to be stalled. While stalled, a pipeline stage will not receive interrupts. However, any pipeline stage of higher priority will continue receiving interrupts, unless it too stalled its own stage. It follows that interrupts are almost never disabled"
 
 The interrupt pipeline is delivered in the form of a kernel patch and maintained outside of the Linux kernel tree.
-For HiKey all that would be required is to replace the kernel from any of the [releases](https://builds.96boards.org/releases/hikey/linaro/debian/latest/) currently available with the I-PIPE aarch64 patched kernel for this board.
+For HiKey all that would be required is to replace the kernel from any of the [releases](https://builds.96boards.org/hikey/linaro/debian/latest/) currently available with the I-PIPE aarch64 patched kernel for this board.
 
 For 96Boards HiKey users it is enough with cloning the following repository checking out the hikey branch:
 
@@ -50,7 +50,7 @@ $ git checkout hikey
 
 ```
 
-Xenomai3  for aarch64 remains work in progress and it hasn’t been merged yet in the project’s master branch. Despite of this some effort was invested during our last Linaro Connect 2015 in SFO and support was added to both 96Boards: HiKey running kernel v3.18 (all Linaro HiKey releases to date) and Dragon 410c running kernel v4.0.0 (Linaro Release [15.07](http://builds.96boards.org/releases/dragonboard410c/linaro/debian/)).
+Xenomai3  for aarch64 remains work in progress and it hasn’t been merged yet in the project’s master branch. Despite of this some effort was invested during our last Linaro Connect 2015 in SFO and support was added to both 96Boards: HiKey running kernel v3.18 (all Linaro HiKey releases to date) and Dragon 410c running kernel v4.0.0 (Linaro Release [15.07](http://builds.96boards.org/dragonboard410c/linaro/debian/)).
 
 So in order to install the Cobalt co-kernel in the I-PIPE enabled kernel just do:
 ```bash

_posts/2016-07-27-96boards-openhours-11recap.md

@@ -106,7 +106,7 @@ WiFi works fine on Hikey with the latest Android Images
 
 Info
 
-[https://releases.linaro.org/96boards/dragonboard410c/qualcomm/](https://releases.linaro.org/96boards/dragonboard410c/qualcomm/)
+[https://builds.96boards.org/dragonboard410c/qualcomm/](https://builds.96boards.org/dragonboard410c/qualcomm/)
 
 A
 

_posts/2016-08-01-96boards-openhours-12-recap.md

@@ -140,7 +140,7 @@ NICE! :-d
 
 MB
 
-Is this the latest available? I notice ubuntu is much older than debian? [https://builds.96boards.org/releases/dragonboard410c/linaro/](https://builds.96boards.org/releases/dragonboard410c/linaro/)
+Is this the latest available? I notice ubuntu is much older than debian? [https://builds.96boards.org/dragonboard410c/linaro/](https://builds.96boards.org/dragonboard410c/linaro/)
 
 T
 

_posts/2016-08-08-96boards-openhours-13-recap.md

@@ -72,7 +72,7 @@ sudo hciconfig hci0 lestates`
 MB
 I don't know for sure, but I believe BLE would need hardware changes in the base design unless that was taken into account from the outset.
 RW
-[http://builds.96boards.org/releases/dragonboard410c/linaro/rescue/latest/](http://builds.96boards.org/releases/dragonboard410c/linaro/rescue/latest/)
+[http://builds.96boards.org/dragonboard410c/linaro/rescue/latest/](http://builds.96boards.org/dragonboard410c/linaro/rescue/latest/)
 AT
 [http://seeedstudio.com/depot/96Boards-UART-p-2525.html?cPath=122_163](http://seeedstudio.com/depot/96Boards-UART-p-2525.html?cPath=122_163)
 YZ

_posts/2016-11-02-diy-drone-featuring-gumstix-96boards-take-flight-openhours.md

@@ -105,7 +105,7 @@ Before we get started, there are a few things you’ll need to take care of.
 
 {% include image.html path="/assets/images/blog/diy-drone-img-2.png" alt="soldering highlight" class="img-fluid" %}
 
-- Make sure you’ve flashed your Dragonboard with Linux. [Linaro’s Debian 16.09](http://builds.96boards.org/releases/dragonboard410c/linaro/debian/16.09/) was used for this demo.
+- Make sure you’ve flashed your Dragonboard with Linux. [Linaro’s Debian 16.09](http://builds.96boards.org/dragonboard410c/linaro/debian/16.09/) was used for this demo.
 
 - Build QGroundControl.
 

_posts/2017-07-25-vulkan-hikey960.md

@@ -40,7 +40,7 @@ Google added native support for the Vulkan API and Libraries in AOSP starting wi
 # How to get Vulkan API on the Hikey960?
 As of now an official patch request has been made by me on android-review that enables support for the vulkan API on the hikey960. https://android-review.googlesource.com/#/c/433019/
 
-Prefered Method (Not-available Yet): Download prebuilt AODP images from: http://builds.96boards.org/snapshots/hikey960/linaro/aosp-master/latest/
+Prefered Method (Not-available Yet): Download prebuilt AODP images from: http://builds.96boards.org/hikey960/linaro/aosp-master/latest/
 
 Alternate Method 1: Compile From Source
 As of now you will need to compile AOSP on you own to get vulkan working on your device.

_posts/2017-07-29-boot-linux-from-sd-card-uboot.md

@@ -107,7 +107,7 @@ partition and RFS would be in **ext4** partition. But, we are going to place the
 After formatting SD card, download the OpenEmbedded RFS from 96Boards build, extract it and flash onto SD card's first partition. By
 the end of this step, the first partition of SD card should have entire Root File System populated.
 
-Now, build the Linux Kernel along with device tree using the instructions available in [release notes](https://releases.linaro.org/96boards/dragonboard410c/).
+Now, build the Linux Kernel along with device tree using the instructions available in [release notes](https://builds.96boards.org/dragonboard410c/).
 Then, convert the generated Kernel image to the format recognized by U-Boot(uImage) using **mkimage** tool.
 
 

_posts/2017-11-26-minecraft-dragonboard.md

@@ -23,7 +23,7 @@ Also, it is architecture independent, ie it can run on Arm... almost. Although t
   ![](https://i.imgur.com/h83jhs6.gif)
 
 ### **Step 1:** Operating systems
-  - You should be running Debian build **[17.09](https://builds.96boards.org/releases/dragonboard410c/linaro/debian/17.09/)**
+  - You should be running Debian build **[17.09](https://builds.96boards.org/dragonboard410c/linaro/debian/17.09/)**
   - Make sure it is updated:
   ```shell
   sudo apt update

_posts/2018-06-07-i2s-in-dragonboard410c.md

@@ -12,7 +12,7 @@ tags: 64-bit, 96Boards, aarch64, ARM, ARMv8, Consumer Edition, Kernel, Linux, Dr
 # Introduction
 
 When you look at the spec of [Dragonboard410c](/documentation/consumer/dragonboard/dragonboard410c/hardware-docs/hardware-user-manual.md.html), there will be 2 I2S ports mentioned.
-However, on the [release image](http://releases.linaro.org/96boards/dragonboard410c/linaro/debian/)
+However, on the [release image](http://builds.96boards.org/dragonboard410c/linaro/debian/)
 provided by Qualcomm Landing team, only one I2S will be used (for HDMI). The other
 one will be on the Low Speed Expansion header but since nothing is connected to those
 pins, the configuration for enabling the I2S is not provided in the release image(kernel).
@@ -88,7 +88,7 @@ $ cd kernel
 $ git checkout -b kernel-<RELEASE> debian-qcom-dragonboard410c-<RELEASE>
 ```
 > Note: Replace < RELEASE > with latest release version found
-[here](http://releases.linaro.org/96boards/dragonboard410c/linaro/debian/latest/)
+[here](http://builds.96boards.org/dragonboard410c/linaro/debian/latest/)
 
 2. Add LS I2S support