In message c166aa9f0508091623642cef58@mail.gmail.com you wrote:
I think the board linker scripts also need to be modified to work with either big or little endian toolchains like below. The third argument to OUTPUT_FORMAT is only used for explicitly little endian compilation.
Thanks for pointing out. I was only able to compile the code, not to actually run it.
The test that decides which endianess to build is not going to work for toolchains other than Denx ones, lots of them have prefixes that don't include 4KCle (they may not build u-boot very well, but that's another issue)
I am aware of this problem. This is one of the reasons why I started this discussion - I need input from users of other tool chains here.
I would suggest doing it by config name and putting ENDIANNESS in config.mk something like so (untested):
I disagree. This is IMHO not a good idea. I think the tool chain should "know" which endian mode it is. I don;t ike the ide to encode this in a build target name:
dbau1550_config \ dbau1550_el_config : unconfig
Why do we need two build targets at all? I think there should be just one "dbau1550" target, and your setting of CROSS_COMPILE determines if this is a little or a big endian build.
Comments?
Best regards,
Wolfgang Denk