All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nylon Chen <nylon7@andestech.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/3] Add prebuilt nds32 toolchain, ae3xx board and autobuild configs support
Date: Thu, 7 Mar 2019 10:11:22 +0800	[thread overview]
Message-ID: <20190307021125.8530-1-nylon7@andestech.com> (raw)

v3:
    1) DEVELOPERS file must be alphabetic ordering of developer names
    2) removed BR2_TOOLCHAIN_HAS_NATIVE_RPC option
    3) removed package modifications because we do not support building nds32 toolchain by Buildroot
    4) replace BR2_LINUX_KERNEL_CUSTOM_VERSION and BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE with BR2_LINUX_KERNEL_CUSTOM_VERSION and BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE
    5) add BR2_ANDES_NDS32_FPU option

v2:
    1) add BR2_GCC_TARGET_ARCH option
    2) add autobuild fragments
    3) replace BR2_LINUX_KERNEL_PATCH with BR2_GLOBAL_PATCH_DIR
    4) make savedefconfig  generate config file
    5) There can only be one author in DEVELOPERS file

Nylon Chen (3):
  arch: add support for Andes 32-bit (nds32) architecture
  configs/andes_nds32_ae3xx: new defconfig
  support/config-fragments: add Andes 32-bit (nds32) to autobuild
    configs

 DEVELOPERS                                    |  9 ++++++
 arch/Config.in                                | 13 ++++++++
 arch/Config.in.nds32                          | 31 +++++++++++++++++++
 board/andes/ae3xx/ae3xx.fragment              |  1 +
 ...0001-nds32-Fix-boot-messages-garbled.patch | 28 +++++++++++++++++
 configs/andes_ae3xx_defconfig                 | 14 +++++++++
 package/binutils/Config.in.host               |  2 ++
 package/gcc/Config.in.host                    |  4 +++
 package/linux-headers/Config.in.host          |  3 ++
 .../autobuild/br-andes-nds32-glibc.config     |  9 ++++++
 .../autobuild/toolchain-configs.csv           |  1 +
 11 files changed, 115 insertions(+)
 create mode 100644 arch/Config.in.nds32
 create mode 100644 board/andes/ae3xx/ae3xx.fragment
 create mode 100644 board/andes/patches/linux/0001-nds32-Fix-boot-messages-garbled.patch
 create mode 100644 configs/andes_ae3xx_defconfig
 create mode 100644 support/config-fragments/autobuild/br-andes-nds32-glibc.config

-- 
2.18.0

             reply	other threads:[~2019-03-07  2:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  2:11 Nylon Chen [this message]
2019-03-07  2:11 ` [Buildroot] [PATCH v3 1/3] arch: add support for Andes 32-bit(nds32) Nylon Chen
2019-03-14 22:22   ` Yann E. MORIN
2019-03-21  2:36     ` Nylon Chen
2019-03-21 11:18       ` Yann E. MORIN
2019-03-22  8:39         ` Nylon Chen
2019-03-22 11:40           ` Yann E. MORIN
2019-03-07  2:11 ` [Buildroot] [PATCH v3 2/3] configs/andes_nds32_ae3xx: new defconfig Nylon Chen
2019-03-14 22:31   ` Yann E. MORIN
2019-03-07  2:11 ` [Buildroot] [PATCH v3 3/3] upport/config-fragments/autobuild: test the Andes nds32 toolchain Nylon Chen
2019-03-14 22:42   ` Yann E. MORIN
2019-03-21  2:51     ` Nylon Chen
2019-03-21  7:51       ` Thomas Petazzoni
2019-03-21 11:12         ` Yann E. MORIN
2019-03-22  8:45           ` Nylon Chen
  -- strict thread matches above, loose matches on Subject: below --
2019-01-23 12:39 [Buildroot] [PATCH v2 0/3] Add prebuilt nds32 toolchain, ae3xx board and autobuild configs support Nylon Chen

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=20190307021125.8530-1-nylon7@andestech.com \
    --to=nylon7@andestech.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.