| Message ID | 1447200375-20544-3-git-send-email-thomas@wytron.com.tw |
|---|---|
| State | Accepted, archived |
| Delegated to: | Thomas Chou |
| Headers | show |
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
Hi Marek, 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. 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? 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
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
Hi Marek, On 2015年11月11日 09:18, Thomas Chou wrote: > 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 look at sourceforge again. And the bfin toolchains is back. Best regards, Thomas
On Wednesday, November 11, 2015 at 02:48:04 AM, Thomas Chou wrote: > Hi Marek, > > On 2015年11月11日 09:18, Thomas Chou wrote: > > 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 look at sourceforge again. And the bfin toolchains is back. Hopefully they don't come with some additional ad-ware :-) Best regards, Marek Vasut
Hi Marek, On 2015年11月11日 09:41, Marek Vasut wrote: > 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. I'd use "killall python" on another terminal to stop the builder. I setup it in around an hour including download toolchains from kernel.org. 1. Create ~/.buildman from the template in buildman/README # Buildman settings file [toolchain] root: / rest: /toolchains/* eldk: /opt/eldk-4.2 arm: /opt/linaro/gcc-linaro-arm-linux-gnueabihf-4.8-2013.08_linux aarch64: /opt/linaro/gcc-linaro-aarch64-none-elf-4.8-2013.10_linux [toolchain-alias] x86: i386 blackfin: bfin sh: sh4 nds32: nds32le openrisc: or32 2. Fetch the toolchains from kernel.org $ for i in aarch64 arm avr32 i386 m68k microblaze mips or32 powerpc sh4 sparc sparc64 do ./tools/buildman/buildman --fetch-arch $i done $ mv ~/.buildman-toolchains/*/* /toolchains/ # arc: https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases # blackfin: http://sourceforge.net/projects/adi-toolchain/files/ # nds32: http://osdk.andestech.com/packages/ # nios2: https://sourcery.mentor.com/GNUToolchain/subscription42545 # sh: http://sourcery.mentor.com/public/gnu_toolchain/sh-linux-gnu nds32: http://osdk.andestech.com/packages/nds32le-linux-glibc-v1.tgz Best regards, Thomas
On Wednesday, November 11, 2015 at 03:55:10 AM, Thomas Chou wrote: > Hi Marek, > > On 2015年11月11日 09:41, Marek Vasut wrote: > > 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. > > I'd use "killall python" on another terminal to stop the builder. I absolutelly don't want to do killall python, it'd bring down much more than this buildman ;-) > I setup it in around an hour including download toolchains from kernel.org. > > 1. Create ~/.buildman from the template in buildman/README > > # Buildman settings file > > [toolchain] > root: / > rest: /toolchains/* > eldk: /opt/eldk-4.2 > arm: /opt/linaro/gcc-linaro-arm-linux-gnueabihf-4.8-2013.08_linux > aarch64: /opt/linaro/gcc-linaro-aarch64-none-elf-4.8-2013.10_linux > > [toolchain-alias] > x86: i386 > blackfin: bfin > sh: sh4 > nds32: nds32le > openrisc: or32 > > 2. Fetch the toolchains from kernel.org > > $ for i in aarch64 arm avr32 i386 m68k microblaze mips or32 powerpc sh4 > sparc sparc64 > do > ./tools/buildman/buildman --fetch-arch $i > done > $ mv ~/.buildman-toolchains/*/* /toolchains/ > > # arc: > https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases > # blackfin: http://sourceforge.net/projects/adi-toolchain/files/ > # nds32: http://osdk.andestech.com/packages/ > # nios2: https://sourcery.mentor.com/GNUToolchain/subscription42545 > # sh: http://sourcery.mentor.com/public/gnu_toolchain/sh-linux-gnu > > nds32: http://osdk.andestech.com/packages/nds32le-linux-glibc-v1.tgz OK, so can I use it in some blocking way ? How do I for example build board "foo" and obtain the result of the build? Best regards, Marek Vasut
Hi Marek, On 2015年11月11日 11:02, Marek Vasut wrote: >> I'd use "killall python" on another terminal to stop the builder. > > I absolutelly don't want to do killall python, it'd bring down much more than > this buildman ;-) > It does depend. On my desktop, there is no other python running as user. I would suggest that a "kill" option could be added to buildman. > OK, so can I use it in some blocking way ? > > How do I for example build board "foo" and obtain the result of the build? What do you mean by "some blocking way"? To build a board "foo", $ ./tools/buildman/buildman foo If you want binary, eg u-boot-dtb.bin, you can add "-k" flag. You may find such usage at the last section of buildman/README, "How to change from MAKEALL". Best regards, Thomas
On Wednesday, November 11, 2015 at 06:06:21 AM, Thomas Chou wrote: > Hi Marek, Hi! > On 2015年11月11日 11:02, Marek Vasut wrote: > >> I'd use "killall python" on another terminal to stop the builder. > > > > I absolutelly don't want to do killall python, it'd bring down much more > > than this buildman ;-) > > It does depend. On my desktop, there is no other python running as user. > I would suggest that a "kill" option could be added to buildman. > > > OK, so can I use it in some blocking way ? > > > > How do I for example build board "foo" and obtain the result of the > > build? > > What do you mean by "some blocking way"? > > To build a board "foo", > > $ ./tools/buildman/buildman foo > > If you want binary, eg u-boot-dtb.bin, you can add "-k" flag. > > You may find such usage at the last section of buildman/README, "How to > change from MAKEALL". I finally got buildman operational, it's pretty nice. Thanks :) Best regards, Marek Vasut
diff --git a/board/altera/nios2/MAINTAINERS b/board/altera/nios2/MAINTAINERS new file mode 100644 index 0000000..aff618b --- /dev/null +++ b/board/altera/nios2/MAINTAINERS @@ -0,0 +1,13 @@ +3C120 DEVBOARD +M: Thomas Chou <thomas@wytron.com.tw> +S: Maintained +F: arch/nios2/dts/3c120_devboard.dts +F: configs/3c120_defconfig +F: include/configs/3c120_devboard.h + +10M50 DEVBOARD +M: Thomas Chou <thomas@wytron.com.tw> +S: Maintained +F: arch/nios2/dts/10m50_devboard.dts +F: configs/10m50_defconfig +F: include/configs/10m50_devboard.h
Add 3c120 and 10m50 devboards MAINTAINERS Signed-off-by: Thomas Chou <thomas@wytron.com.tw> --- board/altera/nios2/MAINTAINERS | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 board/altera/nios2/MAINTAINERS