All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Chen <rickchen36@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] NDS32 toolchain?
Date: Mon, 14 May 2018 16:31:27 +0800	[thread overview]
Message-ID: <CAN5B=eLK3G6jTPK0=kTKgc==_B9vFSu4KL63KkDLUShMiNyj2g@mail.gmail.com> (raw)
In-Reply-To: <752D002CFF5D0F4FA35C0100F1D73F3F6B790012@ATCPCS16.andestech.com>

>> > > > > Related, is there a QEMU target for nds32 that we could leverage
>> > > > > so that once the toolchain issue is resolved we can update
>> > > > > .travis.yml to run
>> > > tests on it?
>> > > > > Thanks!
>> > > >
>> > > > I am applying the QEMU offering permit.
>> > > > If it is ok. I will prepare it for you.
>> > >
>> >
>> > Because I always verify NDS32 on board (AG101P or AE3XX).
>> > I never verify it on NDS32 QEMU.
>> > It seem still have some problems, maybe need some time to debug for work.
>> >
>> > But the RISC-V QEMU is available noe.
>> > Maybe I can give it to you for trying.
>>
>> Adding riscv to the test.py + QEMU section of .travis.yml would be great!
>>
>
> I find it seem get qemu from upstream in .travis.yml
> git clone git://git.qemu.org/qemu.git
> But I am not sure if Andes have any schedule to push qemu to upstream.
> I will keep study it and try to add.
>

Hi Tom

After studing test.py and find it will clone
git://github.com/swarren/uboot-test-hooks.git in travis flow.
It seem that I shall create some files (eq conf.qemu-nx25_na) in
uboot-test-hooks\bin\travis-ci\
May I ask how shall I submit these files into the uboot-test-hooks git repo ?

Rick

  reply	other threads:[~2018-05-14  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 20:17 [U-Boot] NDS32 toolchain? Tom Rini
2018-04-24  3:10 ` rick at andestech.com
2018-04-24 12:14   ` Tom Rini
2018-04-25  3:27     ` rick at andestech.com
2018-04-25 13:03       ` Tom Rini
2018-05-07  2:54         ` rick at andestech.com
2018-05-14  8:31           ` Rick Chen [this message]
2018-05-14 11:16             ` Tom Rini
2018-05-28  6:45               ` Rick Chen
2018-06-07  8:18                 ` Rick 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='CAN5B=eLK3G6jTPK0=kTKgc==_B9vFSu4KL63KkDLUShMiNyj2g@mail.gmail.com' \
    --to=rickchen36@gmail.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 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.