[PATCH] detect conflicting zreladdrs
Russell King - ARM Linux
linux at arm.linux.org.uk
Wed Aug 17 05:02:39 EDT 2011
On Tue, Aug 16, 2011 at 08:46:14AM +0200, Sascha Hauer wrote:
> On Wed, Aug 10, 2011 at 02:44:55PM +0200, Sascha Hauer wrote:
> > With CONFIG_ARM_PATCH_PHYS_VIRT and CONFIG_AUTO_ZRELADDR the kernel
> > is ready to calculate zreladdr at runtime. Currently the boards specify
> > zreladdr using := in their Makefile.boot. This means the value maybe
> > overwritten silently if multiple zreladdr-y exist. This series changes
> > the := into += so that we have multiple words in zreladdr instead.
> > This makes it possible to catch conflicting zreladdrs during build.
> >
> > Without CONFIG_AUTO_ZRELADDR=y multiple zreladdrs are not allowed for
> > zImages, so we bail out if we detect it.
> >
> > uImages are generally incompatible with multiple zreladdrs, so we
> > bail out if we detect it. In this case an uImage can still be built
> > by specifying LOADADDR= on the command line.
> >
> > Sascha
> >
> > Sascha Hauer (3):
> > ARM: Check for multiple zreladdrs
> > ARM: Check for multiple load addresses before building a uImage
> > ARM: allow to detect conflicting zreladdrs
>
> Russell, any comments to this series? Ok to check into the patch system?
No, and yes.
More information about the linux-arm-kernel
mailing list