From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 3/3] nios2: add 3c120 and 10m50 devboards MAINTAINERS
Date: Wed, 11 Nov 2015 02:41:15 +0100 [thread overview]
Message-ID: <201511110241.15419.marex@denx.de> (raw)
In-Reply-To: <56429762.5070306@wytron.com.tw>
On Wednesday, November 11, 2015 at 02:18:26 AM, Thomas Chou wrote:
> Hi Marek,
Hi!
> On 2015?11?11? 08:27, Marek Vasut wrote:
> > On Wednesday, November 11, 2015 at 01:06:15 AM, Thomas Chou wrote:
> >> Add 3c120 and 10m50 devboards MAINTAINERS
> >>
> >> Signed-off-by: Thomas Chou <thomas@wytron.com.tw>
> >
> > All is good with this series.
> >
> > Acked-by: Marek Vasut <marex@denx.de>
> >
> > And thanks for all your good work, it's amazing!
> >
> > Best regards,
> > Marek Vasut
>
> Thanks a lot for your constant help and reviews, too. The work on nios2
> for the v2016.01 release is almost done. I will send a PR to Tom tomorrow.
Cool!
> Now is the fun time for buildman. I fetched some toolchains with
> buildman, and realized that it is better to copy the toolchains from the
> download directory to somewhere like /toolchains, eg,
>
> $ mv /home/sjg/.buildman-toolchains/gcc-4.5.1-nolibc/or32-linux
> /toolchains/
>
> so that they can be detected correctly later.
>
> I still miss some toolchains, like bfin. I can not find them on the
> internet. I will need to search my old HDDs. However, most others works.
> Do you have better results?
I gave up on buildman. I want some builder where I can stop the builds if
something goes wrong, but instead of this, buildman spawns multiple processes
somewhere on my machine at random and I have no control over that. I'd like
to reevaluate buildman eventually, but now I don't have the time or interest
to dig in it.
> List of available toolchains (35):
> aarch64 : /toolchains/aarch64-linux/bin/aarch64-linux-gcc
> alpha : /toolchains/alpha-linux/bin/alpha-linux-gcc
> am33_2.0 : /toolchains/am33_2.0-linux/bin/am33_2.0-linux-gcc
> arm :
> /toolchains/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-gcc
> avr : /usr/bin/avr-gcc
> avr32 : /toolchains/avr32-linux/bin/avr32-linux-gcc
> bfin : /toolchains/bfin-uclinux/bin/bfin-uclinux-gcc
> c89 : /usr/bin/c89-gcc
> c99 : /usr/bin/c99-gcc
> cris : /toolchains/cris-linux/bin/cris-linux-gcc
> crisv32 : /toolchains/crisv32-linux/bin/crisv32-linux-gcc
> frv : /toolchains/frv-linux/bin/frv-linux-gcc
> h8300 : /toolchains/h8300-elf/bin/h8300-elf-gcc
> hppa : /toolchains/hppa-linux/bin/hppa-linux-gcc
> hppa64 : /toolchains/hppa64-linux/bin/hppa64-linux-gcc
> i386 : /toolchains/i386-linux/bin/i386-linux-gcc
> ia64 : /toolchains/ia64-linux/bin/ia64-linux-gcc
> m32r : /toolchains/m32r-linux/bin/m32r-linux-gcc
> m68k : /toolchains/m68k-linux/bin/m68k-linux-gcc
> microblaze: /toolchains/microblaze-linux/bin/microblaze-linux-gcc
> mips : /toolchains/mips-linux/bin/mips-linux-gcc
> mips64 : /toolchains/mips64-linux/bin/mips64-linux-gcc
> nds32le : /toolchains/nds32le-linux-glibc-v1/bin/nds32le-linux-gcc
> nios2 : /opt/sourceryg++-2015.05/bin/nios2-linux-gnu-gcc
> or32 : /toolchains/or32-linux/bin/or32-linux-gcc
> powerpc : /toolchains/powerpc-linux/bin/powerpc-linux-gcc
> powerpc64 : /toolchains/powerpc64-linux/bin/powerpc64-linux-gcc
> ppc64le : /toolchains/ppc64le-linux/bin/ppc64le-linux-gcc
> s390x : /toolchains/s390x-linux/bin/s390x-linux-gcc
> sandbox : /usr/bin/gcc
> sh4 : /toolchains/sh4-linux/bin/sh4-linux-gcc
> sparc : /toolchains/sparc-linux/bin/sparc-linux-gcc
> sparc64 : /toolchains/sparc64-linux/bin/sparc64-linux-gcc
> tilegx : /toolchains/tilegx-linux/bin/tilegx-linux-gcc
> x86_64 : /usr/bin/x86_64-linux-gnu-gcc
>
> $ ./tools/buildman/buildman -b master -s
> boards.cfg is up to date. Nothing to do.
> Summary of 15 commits for 1067 boards (8 threads, 1 job per thread)
> 01: ARM64: zynqmp: Sync zynq_sdhci_init() declaration
> blackfin: + cm-bf561 blackstamp bf537-minotaur bct-brettl2
> cm-bf527 bf506f-ezkit ip04 bf527-sdp pr1 bf609-ezkit bf537-stamp
> bf527-ezkit-v2 cm-bf537e tcm-bf518 cm-bf537u bf527-ezkit cm-bf533
> bf533-ezkit ibf-dsp561 bf537-pnav bf537-srv1 cm-bf548 bf538f-ezkit
> bf548-ezkit bf525-ucr2 blackvme tcm-bf537 bf533-stamp bf518f-ezbrd
> bf527-ad7160-eval bf526-ezbrd bf561-ezkit br4
> aarch64: + hikey xilinx_zynqmp_ep
> avr32: + atngw100mkii grasshopper atstk1002 atngw100
> powerpc: + TQM834x katmai
> sandbox: + sandbox
> sh: + sh7753evb rsk7269 rsk7264 shmin ms7720se mpr2
> sh7785lcr_32bit sh7785lcr rsk7203
> nios2: + 10m50 3c120
> arm: + chromebook_jerry firefly-rk3288 x600
>
>
> Best regards,
> Thomas
next prev parent reply other threads:[~2015-11-11 1:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 12:37 [U-Boot] [PATCH 1/2] nios2: rename board nios2-generic to 3c120_devboard Thomas Chou
2015-11-10 12:37 ` [U-Boot] [PATCH 2/2] nios2: add 3c120 and 10m50 devboards MAINTAINERS Thomas Chou
2015-11-10 13:47 ` [U-Boot] [PATCH 1/2] nios2: rename board nios2-generic to 3c120_devboard Marek Vasut
2015-11-10 14:48 ` [U-Boot] [PATCH v2 " Thomas Chou
2015-11-10 14:48 ` [U-Boot] [PATCH v2 2/2] nios2: add 3c120 and 10m50 devboards MAINTAINERS Thomas Chou
2015-11-10 14:52 ` [U-Boot] [PATCH v2 1/2] nios2: rename board nios2-generic to 3c120_devboard Marek Vasut
2015-11-11 0:06 ` [U-Boot] [PATCH v3 1/3] " Thomas Chou
2015-11-11 0:06 ` [U-Boot] [PATCH v3 2/3] nios2: change README.nios2 to use 10m50 as template Thomas Chou
2015-11-11 0:06 ` [U-Boot] [PATCH v3 3/3] nios2: add 3c120 and 10m50 devboards MAINTAINERS Thomas Chou
2015-11-11 0:27 ` Marek Vasut
2015-11-11 1:18 ` Thomas Chou
2015-11-11 1:41 ` Marek Vasut [this message]
2015-11-11 2:55 ` Thomas Chou
2015-11-11 3:02 ` Marek Vasut
2015-11-11 5:06 ` Thomas Chou
2016-01-06 13:43 ` Marek Vasut
2015-11-11 1:48 ` Thomas Chou
2015-11-11 2:27 ` Marek Vasut
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=201511110241.15419.marex@denx.de \
--to=marex@denx.de \
--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 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.