[PATCH 4/6] ARM: mxc: don't allow to compile together i.MX51 and i.MX53

[Uwe Kleine-König]

On Wed, May 04, 2011 at 10:48:40AM -0500, Matt Sealey wrote:
> 2011/4/13 Uwe Kleine-König <u.kleine-koenig at pengutronix.de>:
> > Hi Shawn,
> >
> > On Wed, Apr 13, 2011 at 08:25:04PM +0800, Shawn Guo wrote:
> >> On Sun, Apr 10, 2011 at 09:49:01PM +0200, Uwe Kleine-König wrote:
> >> [...]
> >> > +     This enables support for machines using Freescale's i.MX50 and i.MX51
> >> s/MX51/MX53/
> > yeah, thanks, as you're not the first one to point this out I already
> > sent a fixup to Sascha.
> 
> Can someone confirm the following for me (Uwe probably as it's his
> patch most recently)
> 
> CONFIG_RUNTIME_PHYS_OFFSET
RUNTIME_PHYS_OFFSET didn't made it into mainline and is superseded by
ARM_PATCH_PHYS_VIRT.

> CONFIG_ARM_PATCH_PHYS_VIRT
> 
> These two config options, with absolutely no bootloader changes, will
> basically mask off some address (instruction pointer?) at the time of
> the check and therefore derive a perfectly good PHYS_OFFSET at runtime
> and make sure it is in use... within some limits (first 128MB, assumes
> that start of memory is at some particular alignment)?
> 
> I am confused about Nicolas' CONFIG_AUTO_ZRELADDR comment and how this
> applies. I am working out a way to have U-Boot ignore the hardcoded
> image entry point in a uImage to enable the above.
ARM_PATCH_PHYS_VIRT is a feature of the Image, AUTO_ZRELADDR is a
feature of the zImage. It solves more or less the same thing (and IIRC
RUNTIME_PHYS_OFFSET did both). So AUTO_ZRELADDR is only needed when
booting a zImage.

And IIRC U-Boot can boot zImages directly nowerdays. So this is probably
the better way to test that hacking it to ignore the image headers.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |