Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 01/11] board: Add Bananapi M1 support
Date: Sat, 21 Oct 2017 22:37:50 +0200	[thread overview]
Message-ID: <20171021223750.3c598d1e@windsurf> (raw)
In-Reply-To: <1508406333-27138-2-git-send-email-jagan@amarulasolutions.com>

Hello,

On Thu, 19 Oct 2017 11:45:23 +0200, Jagan Teki wrote:
> Add initial support for bananapi M1 board with below features:
> - U-Boot 2017.09
> - Linux 4.17
> - Default packages from buildroot
> 
> Cc: Jason <manager@sinovoip.com.cn>
> Cc: hailymei at banana-pi.com <hailymei@banana-pi.com>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
>  .gitlab-ci.yml                          |  1 +
>  DEVELOPERS                              |  2 ++
>  board/bananapi/bananapi-m1/boot.cmd     |  7 +++++++
>  board/bananapi/bananapi-m1/genimage.cfg | 33 +++++++++++++++++++++++++++++
>  board/bananapi/bananapi-m1/readme.txt   | 37 +++++++++++++++++++++++++++++++++
>  configs/bananapi_m1_defconfig           | 37 +++++++++++++++++++++++++++++++++
>  6 files changed, 117 insertions(+)
>  create mode 100644 board/bananapi/bananapi-m1/boot.cmd
>  create mode 100644 board/bananapi/bananapi-m1/genimage.cfg
>  create mode 100644 board/bananapi/bananapi-m1/readme.txt
>  create mode 100644 configs/bananapi_m1_defconfig

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2017-10-21 20:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19  9:45 [Buildroot] [PATCH v3 00/11] board: Add Allwinner A64/H5 boards Jagan Teki
2017-10-19  9:45 ` [Buildroot] [PATCH v3 01/11] board: Add Bananapi M1 support Jagan Teki
2017-10-19 10:38   ` Baruch Siach
2017-10-19 10:56     ` Jagan Teki
2017-10-21 20:37   ` Thomas Petazzoni [this message]
2017-10-19  9:45 ` [Buildroot] [PATCH v3 02/11] support/scripts: Add sunxi64-post-build.sh Jagan Teki
2017-10-21 21:06   ` Thomas Petazzoni
2017-10-22 10:15     ` Jagan Teki
     [not found]       ` <4cb45577-1f4a-ce9c-7204-74934272b789@arm.com>
2017-10-22 12:29         ` Thomas Petazzoni
2017-10-26 11:20           ` Jagan Teki
2017-10-26 18:13             ` Jagan Teki
     [not found]               ` <e73be7ab-6435-5d11-41b5-37f3bf4053ee@arm.com>
2017-10-27 11:46                 ` Jagan Teki
2017-10-19  9:45 ` [Buildroot] [PATCH v3 03/11] board: Add Bananapi M64 support Jagan Teki
2017-10-19  9:45 ` [Buildroot] [PATCH v3 04/11] board: Add Pine64 support Jagan Teki
2017-10-19  9:45 ` [Buildroot] [PATCH v3 05/11] board: Add SoPine support Jagan Teki
2017-10-19  9:45 ` [Buildroot] [PATCH v3 06/11] board: Add FriendlyARM Nanopi A64 support Jagan Teki
2017-10-19  9:45 ` [Buildroot] [PATCH v3 07/11] board: Add FriendlyARM Nanopi NEO2 support Jagan Teki
2017-10-19  9:45 ` [Buildroot] [PATCH v3 08/11] board: Add Olimex A64-OLinuXino support Jagan Teki
2017-10-19  9:45 ` [Buildroot] [PATCH v3 09/11] board: Add Orangepi Win/Win Plus support Jagan Teki
2017-10-19  9:45 ` [Buildroot] [PATCH v3 10/11] board: Add Orangepi Prime support Jagan Teki
2017-10-19  9:45 ` [Buildroot] [PATCH v3 11/11] board: Add Orangepi Zero Plus2 support 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=20171021223750.3c598d1e@windsurf \
    --to=thomas.petazzoni@free-electrons.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