On Mon, Aug 14, 2017 at 09:36:35PM +0200, Wolfgang Denk wrote:
Dear Max,
In message 1502572898.17070.11.camel@gmail.com you wrote:
Ok, will do. The issue is that linking the standalone application to have its text segment at a hardcoded address is less likely to work than using an address provided by the board
This may (or may not) be the case - but no matter how youlook at it, chosing CONFIG_LOADADDR is definitely the wrong approach, as the LOAD address has nothing to do with the ENTRY point address, so it must in no case ever play a role when linking an image.
configuration as a possible load address.
You are confused in your wording, and I'm afraid in your thinking, too.
load address != entry point.
But we're talking about CONFIG_STANDALONE_LOAD_ADDR not CONFIG_STANDALONE_ENTRY_POINT. What we've been doing in arch/arm/config.mk has been on my to fix list for a long time, because it's been wrong for so many boards. Setting this to CONFIG_LOADADDR is a reasonable default value.