Hi
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.
I am running little endian on DBAU1200.
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:
How can we determine that?
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.
CROSS_COMPILE could be set to anything. It could be: - mipsel-linux - 4kc_le-linux - mips-little-linux - ... Is this true?
BR, Matej