[U-Boot] [PATCH v2 10/10] boston: Introduce support for the MIPS Boston development board

[Paul Burton]

On 27/07/16 20:21, Daniel Schwierzeck wrote:
>> diff --git a/configs/boston_defconfig b/configs/boston_defconfig
>> new file mode 100644
>> index 0000000..381203a
>> --- /dev/null
>> +++ b/configs/boston_defconfig
>> @@ -0,0 +1,41 @@
>> +CONFIG_MIPS=y
>> +CONFIG_TARGET_BOSTON=y
>> +CONFIG_SYS_LITTLE_ENDIAN=y
>> +CONFIG_CPU_MIPS64_R6=y
>
> I've noticed that this defconfig with MIPS64r6 breaks buildman and
> TravisCI for me and likely a lot of other people because most available
> toolchains (ELDK, kernel.org, etc.) don't have gcc-5.x yet. And Imgtec
> provides two different toolchains for R6 and R1..R5 so this needs to be
> handled too in buildman.
>
> Does it make sense to add different defconfigs for Boston similar to
> Malta to have build coverage for MIPS32r2 and MIPS64r2 as well as
> BigEndian and LittleEndian? We can add the MIPS32r6 and MIPS64r6
> variants later when more toolchains with a recent gcc are available.
> What do you think?

Hi Daniel,

I don't mind so much - I'm happy to change the defconfig to R2 & have 
separate 32 & 64 bit ones if you prefer. I chose MIPS64r6 for it since 
that's what's being used primarily on real Boston boards. Would you like 
me to submit a v3?

FYI whilst the codescape toolchains on imgtec.com have a split between 
pre-R6 (MTI toolchain) & R6 (IMG toolchain) they only differ in the 
prebuilt libraries included with them, so since U-Boot (or Linux) don't 
link with those libraries you can build with either toolchain for any 
arch revision. For internal U-Boot releases I compile for all 
combinations of r2 & r6, 32 & 64 bit, big & little endian with the same 
toolchain (then bolt them all together into 1 binary with a bit of magic 
trampoline code at the start, which it'd be neat to get tidied & 
upstream some time!).

Thanks,
     Paul