On Fri, Mar 08, 2013 at 04:46:11PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 16:06 Fri 08 Mar , Sascha Hauer wrote: > > On Fri, Mar 08, 2013 at 03:48:43PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote: > > > > > > + .boot_data.size = 192 * 1024, > > > > > barebox_image_size > > > > > > > > ok. This btw will not work with CONFIG_RELOCATABLE as is since the > > > > linker cannot generate this value then. > > > why? > > > > Absolute values will be zero when you link with -pie. They get fixed > > during relocation. > > > > The image size is a relative value, when doing a > > > > .word __barebox_image_end - start > > > > in assembly it works correctly, but doing the same in C does not work. > > > > > > > > otherwise we need to update it via ld as done in the kernel as example > > > > Can you give me a pointer what the kernel does? > > we create the symbol at compilation > via --defsym It just turned out --defsym also does not work together with -pie. The value in the image is still 0x0. 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
