From: Stuart MENEFY <stuart.menefy@st.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: Add CONFIG_PARAM_* to set boot parameters.
Date: Tue, 08 Dec 2009 13:14:00 +0000 [thread overview]
Message-ID: <4B1E5118.9000006@st.com> (raw)
In-Reply-To: <20091130170254.65d2a0ab.yoshii.takashi@renesas.com>
Folks
Paul Mundt wrote:
> On Tue, Dec 08, 2009 at 02:01:26PM +0900, yoshii.takashi@renesas.com wrote:
> zImage doesn't provide the way to know the location.
> Check your kernel configuration file to know where it is.
This is the bit which is nasty. Because we don't use the parameters which
are part of the zImage header (head.S) which are still set up for x86,
the boot loader has to know where empty zero page will end up.
> zImage's entry point is the top of the binary.
Are you sure, I thought was was the start?
>> Name: (Mode_flag?)
>> Address/size: empty_zero_page+0x18/long
>>
>> This is not a part of boot ABI.
>> In vmlinux, this field carries the value indicate 29bit/32bit.
>>
> Correct, this is the 32bit boot flag. It's provided as a hint to figure
> out whether the boot loader has entered from 32-bit boot or not.
> Presently we don't do anything with this however.
We intended this to be rather more than a hint. Because the transition
into SE mode is painful we always do it in the boot loader, and so the
boot loader can check whether the kernel it is loading was compiled
in expectation that SE would already be on.
The 'contract' between the boot loader and the kernel in this case also
has to include the state of the PMB. We did write something about this,
I'll see if I can dig it up...
next prev parent reply other threads:[~2009-12-08 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 8:02 [PATCH] sh: Add CONFIG_PARAM_* to set boot parameters yoshii.takashi
2009-12-02 1:35 ` Paul Mundt
2009-12-08 5:01 ` yoshii.takashi
2009-12-08 8:18 ` Paul Mundt
2009-12-08 13:14 ` Stuart MENEFY [this message]
2009-12-09 12:00 ` Magnus Damm
2009-12-10 5:00 ` yoshii.takashi
2009-12-10 7:01 ` yoshii.takashi
2009-12-10 8:48 ` yoshii.takashi
2009-12-14 2:10 ` Paul Mundt
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=4B1E5118.9000006@st.com \
--to=stuart.menefy@st.com \
--cc=linux-sh@vger.kernel.org \
/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).