From: sunil at amarulasolutions.com <sunil@amarulasolutions.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/2] Add support for rockpro64 and oragepi-rk3399 targets
Date: Sun, 3 May 2020 14:41:15 +0530 [thread overview]
Message-ID: <1588497077-27220-1-git-send-email-sunil@amarulasolutions.com> (raw)
In-Reply-To: <20200502233409.4a90d4b2@windsurf.home>
From: Suniel Mahesh <sunil@amarulasolutions.com>
This patch series adds two new defconfigs based on RK3399 SOC.
Merged http://patchwork.ozlabs.org/project/buildroot/list/?series=174156 and
http://patchwork.ozlabs.org/project/buildroot/list/?series=174242 individual
patches into this two patch series.
Suniel Mahesh (2):
configs/rockpro64: new defconfig
configs/orangepi_rk3399: new defconfig
---
Changes for v2:
- new patch series
- change contact for the respective target.
- As suggested by Thomas Pettazzoni, rk3399 targets does not need
pylibfdt or pyelftools, but only a host Python interpreter. Remove
them and add python, python3 in defconfig.
---
.gitlab-ci.yml | 2 +
DEVELOPERS | 4 ++
board/orangepi/orangepi-rk3399/extlinux.conf | 4 ++
board/orangepi/orangepi-rk3399/genimage.cfg | 39 ++++++++++++++++++
board/orangepi/orangepi-rk3399/post-build.sh | 5 +++
board/orangepi/orangepi-rk3399/readme.txt | 56 ++++++++++++++++++++++++++
board/pine64/rockpro64/extlinux.conf | 4 ++
board/pine64/rockpro64/genimage.cfg | 39 ++++++++++++++++++
board/pine64/rockpro64/post-build.sh | 5 +++
board/pine64/rockpro64/readme.txt | 60 ++++++++++++++++++++++++++++
configs/orangepi_rk3399_defconfig | 56 ++++++++++++++++++++++++++
configs/rockpro64_defconfig | 56 ++++++++++++++++++++++++++
12 files changed, 330 insertions(+)
create mode 100644 board/orangepi/orangepi-rk3399/extlinux.conf
create mode 100644 board/orangepi/orangepi-rk3399/genimage.cfg
create mode 100755 board/orangepi/orangepi-rk3399/post-build.sh
create mode 100644 board/orangepi/orangepi-rk3399/readme.txt
create mode 100644 board/pine64/rockpro64/extlinux.conf
create mode 100644 board/pine64/rockpro64/genimage.cfg
create mode 100755 board/pine64/rockpro64/post-build.sh
create mode 100644 board/pine64/rockpro64/readme.txt
create mode 100644 configs/orangepi_rk3399_defconfig
create mode 100644 configs/rockpro64_defconfig
--
2.7.4
next prev parent reply other threads:[~2020-05-03 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 18:33 [Buildroot] [PATCH] configs/orangepi_rk3399: new defconfig sunil at amarulasolutions.com
2020-05-02 21:34 ` Thomas Petazzoni
2020-05-03 6:34 ` Suniel Mahesh
2020-05-03 9:11 ` sunil at amarulasolutions.com [this message]
2020-05-03 9:11 ` [Buildroot] [PATCH v2 1/2] configs/rockpro64: " sunil at amarulasolutions.com
2020-05-03 9:11 ` [Buildroot] [PATCH v2 2/2] configs/orangepi_rk3399: " sunil at amarulasolutions.com
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=1588497077-27220-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