From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Sat, 01 Oct 2011 09:01:47 +0200 Subject: [U-Boot] [RFC PATCH] arm: provide a CONFIG flag for disabling relocation In-Reply-To: References: <4E79F2EC.6070002@ti.com> Message-ID: <4E86BADB.20707@aribaud.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Simon, Le 23/09/2011 18:04, Simon Glass a ?crit : >> Are you looking for CONFIG_SYS_SKIP_ARM_RELOCATION? I think Anthony is >> only fixing couple of issues uncovered by the original 'skip >> relocation' patch but I don't think CONFIG_SYS_SKIP_ARM_RELOCATION >> itself is getting accepted. > > I see. That is sad, because skipping relocation is very useful for > development. Why do we make things harder for devs than they need to > be? There is at least a possibility to avoid relocation without introducing the CONFIG_SYS_SKIP_ARM_RELOCATION flag; set CONFIG_SKIP_LOWLEVEL_INIT and adjust CONFIG_SYS_TEXT_BASE to be the base address where your code will be located. It is a two-round process (you need a first run with the 'wrong' CONFIG_SYS_TEXT_BASE in order to find its 'right' value) and will work only for a given board variant (same available RAM amount always) but might be enough to cover the use case(s) you are looking for? > Regards, > Simon Amicalement, -- Albert.