>> > > > > 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 _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
