On Tue, May 07, 2019 at 06:25:16PM +0200, Wolfgang Grandegger wrote:
Am 06.05.19 um 19:55 schrieb Marek Vasut:
On 5/6/19 5:45 PM, Wolfgang Grandegger wrote:
Re-add support for Aries Embedded MCV SoM, which is CycloneV based and the associated MCVEVK baseboard. The board can boot from eMMC. Ethernet and USB is supported.
[snip]
diff --git a/.travis.yml b/.travis.yml index 8bd49ef..714b92e 100644 --- a/.travis.yml +++ b/.travis.yml @@ -230,7 +230,7 @@ matrix: - BUILDMAN="sun50i" - name: "buildman catch-all ARM" env:
- BUILDMAN="arm -x arm11,arm7,arm9,aarch64,at91,freescale,kirkwood,mvebu,siemens,tegra,uniphier,mx,samsung,sunxi,am33xx,omap,pxa,rockchip,toradex,socfpga,k2,xilinx"
- BUILDMAN="arm -x arm11,arm7,arm9,aarch64,aries,at91,freescale,kirkwood,mvebu,siemens,tegra,uniphier,mx,samsung,sunxi,am33xx,omap,pxa,rockchip,toradex,socfpga,k2,xilinx"What's this about ?
I don't know ;). That's from the original U-Boot support.
Since there's some confusion here, I'll explain so it can be handled correctly in any future re-inclusions. Due to a restriction on wall-clock job time in Travis-CI for open source projects, we split building the world up into a large number of jobs. We have lots of "build this vendor" type jobs, which in some cases means "everything from Toradex" and in other cases means "Everything that's an nvidia-provided SoC". There was a job for aries-produced boards and then they were also excluded from other jobs, so that for example we wouldn't build this platform under both "build all aries boards" and "build all socfpga boards". Since we're talking about just adding back this one socfpga board, we don't need to make a "build all aries boards" job, and can just build it in the general "build all socfpga boards" job.
Confusing and error-prone? Yes. This is one of the things that's why I'm looking at GitLab CI (which will have its own downsides, sadly).