From: Paul Mackerras <paulus@samba.org>
To: "Dale Farnsworth" <dale@farnsworth.org>
Cc: Tom Rini <trini@kernel.crashing.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Patch boot/common/relocate.S to start kernel at 0x000c
Date: Wed, 5 Mar 2003 11:47:45 +1100 [thread overview]
Message-ID: <15973.18737.651334.824024@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <20030305000708.GD4683@rover.farnsworth.org>
Dale Farnsworth writes:
> Since __secondary_hold writes to 0x4 and only reads 0x0 looking for
> it's cpu id, I still like the "b __start" at 0x0.
Why are we still using locations 0 and 4 if that is causing trouble?
Why not change to 0xf0 and 0xf4 or something else out of the way? We
can do the change simultaneously in the boot wrapper and in head.S, so
there are no compatibility issues.
Just a suggestion. :)
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-05 0:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 19:16 Patch boot/common/relocate.S to start kernel at 0x000c Dale Farnsworth
2003-03-04 19:24 ` Dan Malek
2003-03-04 20:13 ` Dale Farnsworth
2003-03-04 20:21 ` Dan Malek
2003-03-04 23:08 ` Dale Farnsworth
2003-03-04 23:21 ` Dan Malek
2003-03-04 23:35 ` Dale Farnsworth
2003-03-04 23:42 ` Tom Rini
2003-03-05 0:07 ` Dale Farnsworth
2003-03-05 0:47 ` Paul Mackerras [this message]
2003-03-05 1:01 ` Wolfgang Denk
2003-03-05 1:03 ` Wolfgang Denk
[not found] ` <20030305022134.GR24171@kalmia.hozed.org>
2003-03-05 4:40 ` Dale Farnsworth
2003-03-05 17:07 ` Tom Rini
2003-03-05 17:24 ` Dan Malek
[not found] ` <15973.24544.124365.553602@argo.ozlabs.ibm.com>
2003-03-05 4:28 ` Dale Farnsworth
2003-03-05 9:54 ` Benjamin Herrenschmidt
2003-03-05 17:10 ` Tom Rini
2003-03-11 18:45 ` Dale Farnsworth
2003-03-13 22:38 ` Dale Farnsworth
2003-03-14 11:43 ` Gabriel Paubert
2003-03-14 17:52 ` Dale Farnsworth
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=15973.18737.651334.824024@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=dale@farnsworth.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).