Re: [PATCH 2/5] MIPS: Allow platforms to specify the decompressor load address

2015-02-24 Thread Ralf Baechle
On Tue, Feb 24, 2015 at 01:39:03PM -0800, Andrew Bresticker wrote: > 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

Re: [PATCH 2/5] MIPS: Allow platforms to specify the decompressor load address

2015-02-24 Thread Andrew Bresticker
On Tue, Feb 24, 2015 at 12:15 AM, Arnd Bergmann 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

Re: [PATCH 2/5] MIPS: Allow platforms to specify the decompressor load address

2015-02-24 Thread Arnd Bergmann
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

Re: [PATCH 2/5] MIPS: Allow platforms to specify the decompressor load address

2015-02-24 Thread Andrew Bresticker
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.

Re: [PATCH 2/5] MIPS: Allow platforms to specify the decompressor load address

2015-02-24 Thread Arnd Bergmann
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

Re: [PATCH 2/5] MIPS: Allow platforms to specify the decompressor load address

2015-02-24 Thread Ralf Baechle
On Tue, Feb 24, 2015 at 01:39:03PM -0800, Andrew Bresticker wrote: 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

[PATCH 2/5] MIPS: Allow platforms to specify the decompressor load address

2015-02-23 Thread Andrew Bresticker
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

[PATCH 2/5] MIPS: Allow platforms to specify the decompressor load address

2015-02-23 Thread Andrew Bresticker
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