From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] board/friendlyarm: Add support for friendlyarm nanopi neo4 board
Date: Wed, 5 Jun 2019 10:57:05 -0400 [thread overview]
Message-ID: <20190605145705.GS7705@bill-the-cat> (raw)
In-Reply-To: <20190604084705.15607-1-shyam.saini@amarulasolutions.com>
On Tue, Jun 04, 2019 at 02:17:03PM +0530, Shyam Saini wrote:
> This initial support includes:
> Linux v5.2-rc1
> Custom U-Boot
> Arm Trusted Firmware v2.0
> Buildroot default packages
>
> Signed-off-by: Shyam Saini <shyam.saini@amarulasolutions.com>
> ---
> .gitlab-ci.yml | 1 +
> DEVELOPERS | 2 ++
> board/friendlyarm/nanopi-neo4/extlinux.conf | 4 +++
> board/friendlyarm/nanopi-neo4/genimage.cfg | 22 ++++++++++++
> board/friendlyarm/nanopi-neo4/post-build.sh | 9 +++++
> board/friendlyarm/nanopi-neo4/readme.txt | 53 +++++++++++++++++++++++++++
> configs/nanopi_neo4_defconfig | 55 +++++++++++++++++++++++++++++
> 7 files changed, 146 insertions(+)
> create mode 100644 board/friendlyarm/nanopi-neo4/extlinux.conf
> create mode 100644 board/friendlyarm/nanopi-neo4/genimage.cfg
> create mode 100755 board/friendlyarm/nanopi-neo4/post-build.sh
> create mode 100644 board/friendlyarm/nanopi-neo4/readme.txt
> create mode 100644 configs/nanopi_neo4_defconfig
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 5ed1b8f4d5..2f41bcf7c6 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -181,6 +181,7 @@ nanopi_m1_defconfig: { extends: .defconfig }
> nanopi_m1_plus_defconfig: { extends: .defconfig }
> nanopi_m4_defconfig: { extends: .defconfig }
> nanopi_neo_defconfig: { extends: .defconfig }
> +nanopi_neo4_defconfig: { extends: .defconfig }
> nexbox_a95x_defconfig: { extends: .defconfig }
> nitrogen6sx_defconfig: { extends: .defconfig }
> nitrogen6x_defconfig: { extends: .defconfig }
We don't have gitlab-ci setup in mainline, so this won't apply as-is. I
would however very much like to see what you have as I'd posted
elsewhere my gitlab-ci file that converts what we do in travis to
gitlab. Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190605/2ea71be0/attachment.sig>
next prev parent reply other threads:[~2019-06-05 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 8:47 [U-Boot] [PATCH 1/3] board/friendlyarm: Add support for friendlyarm nanopi neo4 board Shyam Saini
2019-06-04 8:47 ` [U-Boot] [PATCH 2/3] board/radxa: Add support for Radxa Rock Pi4 board Shyam Saini
2019-06-04 8:47 ` [U-Boot] [PATCH 3/3] board/pine64: Add support for Pine64 RockPro64 board Shyam Saini
2019-06-04 8:51 ` Shyam Saini
2019-06-05 14:57 ` Tom Rini [this message]
2019-06-06 6:17 ` [U-Boot] [PATCH 1/3] board/friendlyarm: Add support for friendlyarm nanopi neo4 board Shyam Saini
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=20190605145705.GS7705@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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