On Fri, Mar 07, 2008 at 10:55:51AM -0600, Kumar Gala wrote:
Normally we assume kernel images will be loaded at offset 0. However
there are situations, like when the kernel itself is running at a non-zero
physical address, that we don't want to load it at 0.
Allow the wrapper to take an
On Mar 10, 2008, at 7:37 PM, David Gibson wrote:
On Fri, Mar 07, 2008 at 10:55:51AM -0600, Kumar Gala wrote:
Normally we assume kernel images will be loaded at offset 0. However
there are situations, like when the kernel itself is running at a
non-zero
physical address, that we don't want
On Mar 7, 2008, at 7:44 PM, Geoff Levand wrote:
On 03/07/2008 08:55 AM, Kumar Gala wrote:
Normally we assume kernel images will be loaded at offset 0. However
there are situations, like when the kernel itself is running at a
non-zero
physical address, that we don't want to load it at 0.
Normally we assume kernel images will be loaded at offset 0. However
there are situations, like when the kernel itself is running at a non-zero
physical address, that we don't want to load it at 0.
Allow the wrapper to take an offset. We use this when building u-boot images.
Signed-off-by:
On 03/07/2008 08:55 AM, Kumar Gala wrote:
Normally we assume kernel images will be loaded at offset 0. However
there are situations, like when the kernel itself is running at a non-zero
physical address, that we don't want to load it at 0.
Allow the wrapper to take an offset. We use this
