From: Scott Wood <scottwood@freescale.com>
To: mjw@linux.vnet.ibm.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] change where the kernel loads
Date: Tue, 15 Jan 2008 15:09:50 -0600 [thread overview]
Message-ID: <478D211E.6050209@freescale.com> (raw)
In-Reply-To: <478D2038.4090205@linux.vnet.ibm.com>
Mike Wolf wrote:
> When netbooting a kernel with an initrd or initramfs that makes
> the image larger than 8 meg the firmware will kick out the kernel
> and go to the second boot device. However when the mkzimage
> script is used to create the image instead of 'make zImage' then
> the kernel/initrd will netboot. So this patch changes boot/zImage.lds
> to load the kernel at the same location that the mkzimage would set.
>
> This has been boot tested on POWER5, POWER5+, blades and POWER6
> systems successfully.
This will fail on any platform without a vmlinux_alloc(), as there will
be insufficient room for the kernel at address zero.
-Scott
prev parent reply other threads:[~2008-01-15 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 21:06 [PATCH] change where the kernel loads Mike Wolf
2008-01-15 21:09 ` Scott Wood [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=478D211E.6050209@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mjw@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).