Hi Pavel,
Hi, Detlev!
Altera Cyclone 5 board is very different board (big, rectangular, expensive) than EBV Socrates (small, circular, cheap) board. Different parts are used there, too, but same configuration of u-boot works on both. Nevertheless, printing wrong name confuses users. Virtual target is completely different, and board configured for it will not boot on physical targets.
Thanks for the initiative again.
I'm celebrating mainline u-boot on my target :-).
Yay!
--- a/boards.cfg +++ b/boards.cfg @@ -379,6 +379,8 @@ Active arm armv7 rmobile renesas lager Active arm armv7 s5pc1xx samsung goni s5p_goni - Przemyslaw Marczak p.marczak@samsung.com Active arm armv7 s5pc1xx samsung smdkc100 smdkc100 - Minkyu Kang mk7.kang@samsung.com Active arm armv7 socfpga altera socfpga socfpga_cyclone5 - - +Active arm armv7 socfpga altera socfpga socfpga_virtual - - +Active arm armv7 socfpga altera socfpga socfpga_socrates
As you correctly note, the socrates is sold by EBV and not Altera so I guess the 5th column needs to be changed. Will this still work?
That will result in:
CC arch/arm/lib/eabi_compat.o scripts/Makefile.build:64: /home/pavel/wagabuibui/u-boot/board/ebv/socfpga/Makefile: No such file or directory make[2]: *** No rule to make target `/home/pavel/wagabuibui/u-boot/board/ebv/socfpga/Makefile'. Stop.
I feared as much, so thats why I asked ;)
...and I don't think we want to do board/{altera,ebv} symlink. Are there any other options? Or is "altera" in the boards file simply acceptable?
This is a problem that will turn up in the future even more, so I propose to solve it correctly now. It will not be long before we want to have our own configuration for our MCV module and this will certainly be sold by DENX. I think we need an infrastructure to allow for boards sold by arbitrary manufacturers all using the Altera chip.
The situation as such is not uncommon, so maybe you can follow examples from different CPUs? I.e. how is the imx6 handled on the different base boards?
Cheers Detlev