On Tue, Feb 24, 2015 at 12:15 AM, Arnd Bergmann <a...@arndb.de> wrote: > On Monday 23 February 2015 17:31:44 Andrew Bresticker wrote: >> Platforms which use raw zboot images may need to link the image at >> a fixed address if there is no other way to communicate the load >> address to the bootloader. Allow the per-platform Kbuild files >> to specify an optional zboot image load address (zload-y) and fall >> back to calc_vmlinuz_load_addr if unset. >> >> Signed-off-by: Andrew Bresticker <abres...@chromium.org> >> Cc: Lars-Peter Clausen <l...@metafoo.de> > > No objections to the patch, but have you considered doing the > same thing as ARM's AUTO_ZRELADDR, where we calculate the > address at runtime from the entry point? > > I assume this is the same kind of address you are talking > about here; if not, nevermind.
It is the same sort of issue, though I think the only way to solve it on MIPS would be to copy the image to the address it was linked at, which could be problematic if there's overlap. There's also the cache maintenance we'd have to do, which varies from CPU to CPU (and more so the ARM I believe). -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
