All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] juno: Adding support for Juno r2
Date: Thu,  9 Jun 2016 11:40:30 +0100	[thread overview]
Message-ID: <01f8f69ba500ed01970fb600c6c5ae168669c88d.1465468621.git.jpinto@synopsys.com> (raw)
In-Reply-To: <cover.1465468621.git.jpinto@synopsys.com>

Add support for Juno r2.

Signed-off-by: Joao Pinto <jpinto@synopsys.com>
---
 board/arm/juno/readme.txt  | 17 ++++++++++++++++-
 configs/arm_juno_defconfig |  2 +-
 2 files changed, 17 insertions(+), 2 deletions(-)

diff --git a/board/arm/juno/readme.txt b/board/arm/juno/readme.txt
index 52fabf9..e1adb71 100644
--- a/board/arm/juno/readme.txt
+++ b/board/arm/juno/readme.txt
@@ -6,6 +6,7 @@ Intro
 These instructions apply to all models of the ARM Juno:
   - Juno r0 (does not support PCIe)
   - Juno r1 (supports PCIe)
+  - Juno r2 (Big Cluster with A72)
 
 Buildroot will generate the kernel image, device tree blob and a
 minimal root filesystem.
@@ -41,6 +42,7 @@ After building, you should obtain this tree:
     +-- rootfs.tar
     +-- juno.dtb (if Juno r0 is used)
     +-- juno-r1.dtb (if Juno r1 is used)
+    +-- juno-r2.dtb (if Juno r2 is used)
     +-- Image
 
 Preparing your rootfs
@@ -89,6 +91,19 @@ NOR3LOAD: 00000000               ;Image Load Address
 NOR3ENTRY: 00000000              ;Image Entry Point
 ......
 
+Configure *.dtb in the boot configuration for Juno r1
+=====================================================
+
+SITE1/HBI0262D/images.txt
+......
+NOR3UPDATE: AUTO                 ;Image Update:NONE/AUTO/FORCE
+NOR3ADDRESS: 0x02000000          ;Image Flash Address
+NOR3FILE: \SOFTWARE\juno-r2.dtb  ;Image File Name
+NOR3NAME: board.dtb              ;Specify target filename to preserve file extension
+NOR3LOAD: 00000000               ;Image Load Address
+NOR3ENTRY: 00000000              ;Image Entry Point
+......
+
 Installing kernel image and DTB
 ===============================
 
@@ -97,7 +112,7 @@ Installing kernel image and DTB
    A mass storage device should appear in your desktop.
 3. Open the software/ folder
 4. Copy the 'Image' file to software/
-5. Copy the 'juno-r1.dtb' (r1) or the 'juno.dtb' (r0) file to software/
+5. Copy the 'juno-r1.dtb' (r1), 'juno.dtb' (r0) or juno-r2.dtb (r2) file to software/
 6. Press the red button in the front pannel of ARM Juno
 
 At this time, the board will erase the Flash entry for each new item and
diff --git a/configs/arm_juno_defconfig b/configs/arm_juno_defconfig
index 87b6374..5ce882c 100644
--- a/configs/arm_juno_defconfig
+++ b/configs/arm_juno_defconfig
@@ -11,4 +11,4 @@ BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="linux-linaro-4.3-2015.11"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/arm/juno/linux-juno-defconfig"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
-BR2_LINUX_KERNEL_INTREE_DTS_NAME="arm/juno arm/juno-r1"
+BR2_LINUX_KERNEL_INTREE_DTS_NAME="arm/juno arm/juno-r1 arm/juno-r2"
-- 
1.8.1.5

  reply	other threads:[~2016-06-09 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 10:40 [Buildroot] [PATCH 0/2] juno: add support for Juno r2 and point to v4.6 mainline Joao Pinto
2016-06-09 10:40 ` Joao Pinto [this message]
2016-06-09 20:03   ` [Buildroot] [PATCH 1/2] juno: Adding support for Juno r2 Thomas Petazzoni
2016-06-13 16:55     ` Joao Pinto
2016-06-09 10:40 ` [Buildroot] [PATCH 2/2] configs/arm_juno: Point to 4.6 mainline kernel Joao Pinto
2016-06-09 20:07   ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01f8f69ba500ed01970fb600c6c5ae168669c88d.1465468621.git.jpinto@synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.