Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sunil at amarulasolutions.com <sunil@amarulasolutions.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] Fix ATF v2.2 build for rk3399, add roc-rk3399-pc board
Date: Thu, 13 Feb 2020 11:22:27 +0530	[thread overview]
Message-ID: <1581573151-18943-1-git-send-email-sunil@amarulasolutions.com> (raw)

From: Suniel Mahesh <sunil@amarulasolutions.com>

This patch set does the following:
Fix ATF v2.2 build for rk3399 SoC's.
Add arm-gnu-a-toolchain package, which acts as a secondary bare metal toolchain
to build ATF. The required pre-built toolchain is taken from ARM developers site and
installed in host filesystem only.
Add rk3399 support for building ATF.
Add new defconfig file for roc-rk3399-pc.

The patch set is tested on roc-rk3399-pc, a rk3399 based target. 

Jagan Teki (1):
  boot/arm-trusted-firmware: Disable bin copy for rk3399

Suniel Mahesh (3):
  package/arm-gnu-a-toolchain: new package
  boot/arm-trusted-firmware: add support for rockchip rk3399
  configs/roc-rk3399-pc: new defconfig

 .gitlab-ci.yml                                     |  1 +
 DEVELOPERS                                         |  4 ++
 board/firefly/roc-rk3399-pc/extlinux.conf          |  4 ++
 board/firefly/roc-rk3399-pc/genimage.cfg           | 22 +++++++++
 board/firefly/roc-rk3399-pc/post-build.sh          |  5 ++
 board/firefly/roc-rk3399-pc/readme.txt             | 17 +++++++
 boot/arm-trusted-firmware/Config.in                |  2 +-
 boot/arm-trusted-firmware/arm-trusted-firmware.mk  |  4 ++
 configs/roc_pc_rk3399_defconfig                    | 53 ++++++++++++++++++++++
 .../arm-gnu-a-toolchain/arm-gnu-a-toolchain.hash   |  3 ++
 package/arm-gnu-a-toolchain/arm-gnu-a-toolchain.mk | 27 +++++++++++
 11 files changed, 141 insertions(+), 1 deletion(-)
 create mode 100644 board/firefly/roc-rk3399-pc/extlinux.conf
 create mode 100644 board/firefly/roc-rk3399-pc/genimage.cfg
 create mode 100644 board/firefly/roc-rk3399-pc/post-build.sh
 create mode 100644 board/firefly/roc-rk3399-pc/readme.txt
 create mode 100644 configs/roc_pc_rk3399_defconfig
 create mode 100644 package/arm-gnu-a-toolchain/arm-gnu-a-toolchain.hash
 create mode 100644 package/arm-gnu-a-toolchain/arm-gnu-a-toolchain.mk

-- 
2.7.4

             reply	other threads:[~2020-02-13  5:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13  5:52 sunil at amarulasolutions.com [this message]
2020-02-13  5:52 ` [Buildroot] [PATCH 1/4] boot/arm-trusted-firmware: Disable bin copy for rk3399 sunil at amarulasolutions.com
2020-02-13  7:23   ` Sergey Matyukevich
2020-02-13  8:06     ` Jagan Teki
2020-02-14  4:20       ` Thomas Petazzoni
2020-02-14  6:55         ` Jagan Teki
2020-02-14  7:26           ` Thomas Petazzoni
2020-02-14  7:34             ` Jagan Teki
2020-02-14 10:57             ` Sunil Kumar Mahesh
2020-02-14 12:33               ` Sunil Kumar Mahesh
2020-02-13  5:52 ` [Buildroot] [PATCH 2/4] package/arm-gnu-a-toolchain: new package sunil at amarulasolutions.com
2020-02-13  7:34   ` Sergey Matyukevich
2020-02-13  8:10     ` Jagan Teki
2020-02-13  9:20       ` Sergey Matyukevich
2020-02-13  9:43         ` Jagan Teki
2020-02-13 10:01         ` Sunil Kumar Mahesh
2020-02-14  4:19           ` Thomas Petazzoni
2020-02-14  4:17         ` Thomas Petazzoni
2020-02-13  5:52 ` [Buildroot] [PATCH 3/4] boot/arm-trusted-firmware: add support for rockchip rk3399 sunil at amarulasolutions.com
2020-02-14  8:25   ` Sergey Matyukevich
2020-02-14  9:35     ` Sunil Kumar Mahesh
2020-02-13  5:52 ` [Buildroot] [PATCH 4/4] configs/roc-rk3399-pc: new defconfig sunil at amarulasolutions.com
2020-02-13  8:22   ` Jagan Teki

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=1581573151-18943-1-git-send-email-sunil@amarulasolutions.com \
    --to=sunil@amarulasolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox