From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Holler Date: Thu, 28 Oct 2010 13:46:01 +0200 Subject: [U-Boot] CONFIG_SKIP_RELOCATE_UBOOT still used? In-Reply-To: <4CC95B9E.3040108@emk-elektronik.de> References: <4CC914D8.4070101@denx.de> <20101028083950.20A74152451@gemini.denx.de> <4CC94F39.7050302@ahsoftware.de> <4CC95B9E.3040108@emk-elektronik.de> Message-ID: <4CC96279.3030901@ahsoftware.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Am 28.10.2010 13:16, schrieb Reinhard Meyer: >> CONFIG_SKIP_RELOCATE_UBOOT > > The old way in ARM before ELF relocation was introduced. A misnomer because it seemingly > skipped the *COPY* of the image from whereever it was loaded to the TEXT_BASE > location. There was no real *RELOCATION* done there. This define probably does not work > anymore. It was set on ARM boards where a preloader did load u-boot to the > TEXT_BASE address. > > In an up to date ARM system all those defines MUST NOT be set. Thanks for that explanation. In regard to CONFIG_SKIP_RELOCATE_UBOOT I've hit a typo in arch/arm/cpu/arm926ejs/start.S while trying to use this define to build a non relocatable u-boot. In line 383 there is ldr pc, r0 which seems to should be ldr pc, [r0] But after fixing that I've just run into other problems compiling u-boot with CONFIG_SKIP_RELOCATE_UBOOT defined. I don't send a patch, because I assume that code is just dead will be eliminated in the near future. Regards, Alexander