From mboxrd@z Thu Jan 1 00:00:00 1970 From: Max Krummenacher Date: Sat, 12 Aug 2017 23:21:38 +0200 Subject: [U-Boot] [PATCH 1/2] arm: use $loadaddr as the standalone entry point In-Reply-To: <20170812182951.D4D52120203@gemini.denx.de> References: <20170812090346.7887-1-max.krummenacher@toradex.com> <20170812182951.D4D52120203@gemini.denx.de> Message-ID: <1502572898.17070.11.camel@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: u-boot@lists.denx.de Dear Wolfgang Am Samstag, den 12.08.2017, 20:29 +0200 schrieb Wolfgang Denk: > Dear Max, > > In message <20170812090346.7887-2-max.krummenacher@toradex.com> you wrote: > > > > Different SoCs have different RAM layouts, so providing > > $(CONFIG_LOADADDR) instead of the constant 0xc100000 for > > CONFIG_STANDALONE_LOAD_ADDR is probably more appropriate. > > At least the wording of the Subject should be fixed. 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 configuration as a possible load address. Will reword the commit message in a v2 series accordingly. Max > > It is fundamentaaly broken to associate the names "loadaddr" and > "entry point" with each other.  Both are completely independent > entities which mean totally different things. It is pure chance if > the entry point of some loaded image should be at the very beginning > of this image, but this is almost never the case. > > Best regards, > > Wolfgang Denk >