On Tue, Mar 05, 2013 at 08:32:11AM +0400, Alexander Shiyan wrote: > > On Tue, Mar 05, 2013 at 12:10:02AM +0400, Alexander Shiyan wrote: > > > > For making the same binary executable on different SoCs which have > > > > different DRAM addresses we have to be independent of the compile > > > > time link address. > > > > > > > > This patch adds relocatable binary support for the ARM architecture. > > > > With this two new functions are available. relocate_to_current_adr > > > > will fixup the binary to continue executing from the current position. > > > > relocate_to_adr will copy the binary to a given address, fixup the > > > > binary and continue executing from there. > > > > > > > > For the PBL and the real image relocatable support can be enabled > > > > independently. This is done to (hopefully) better cope with setups > > > > where the PBL runs from SRAM or ROM and the real binary does not. > > > > > > > > Signed-off-by: Sascha Hauer <s.hauer@xxxxxxxxxxxxxx> > > > ... > > > > > > Hello. > > > > > > I just suggest put this new stuff under EXPERIMENTAL condition. > > > Thanks. > > > > I'm unsure this makes sense. In the kernel currently 388 options depend > > on EXPERIMENTAL and 433 out of 438 defconfigs have EXPERIMENTAL enabled. > > This recently led to the discussion whether this option should be > > removed from the Kernel. > > OK. > > One more thing. You are introduce "RELOCATABLE" symbol in arm/Kconfig, > but symbol with same name is already exist in common/Kconfig. On > my opinion this is no so good. Indeed. This was not intentional. I removed it from arch/arm/Kconfig Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
