[PATCH 1/2] imx: Internal boot sources, handle all header offsets
Jean-Christophe PLAGNIOL-VILLARD
plagnioj at jcrosoft.com
Fri Oct 1 12:53:24 EDT 2010
On 14:58 Fri 01 Oct , Marc Reilly wrote:
> Hi,
>
> > > -#define __image_len_0x100 __section(.image_len_0x100)
> > > +#if defined(CONFIG_ARCH_IMX_INTERNAL_BOOT_NOR)
> > > + #define __flash_header_section __section(.flash_header_0x1000)
> > > + #define __dcd_entry_section __section(.dcd_entry_0x1000)
> > > + #define __image_len_section __section(.image_len_0x1000)
> > > + #define FLASH_HEADER_OFFSET 0x1000
> > > +#elif defined(CONFIG_ARCH_IMX_INTERNAL_BOOT_ONENAND)
> > > + #define __flash_header_section __section(.flash_header_0x0100)
> > > + #define __dcd_entry_section __section(.dcd_entry_0x0100)
> > > + #define __image_len_section __section(.image_len_0x0100)
> > > + #define FLASH_HEADER_OFFSET 0x0100
> >
> > nor and onenand are the same why duplicate them?
>
> They look similar but, NOR offset is at 4Kb (0x1000), OneNand is 256b (0x100).
>
> (The leading zero for 0x0100 doesn't help, but is necessary otherwise the
> blah_0x1000 matches the blah_0x100* linker section.)
why do we need specific section name?
Best Regards,
J.
More information about the barebox
mailing list