From: Wolfgang Denk <wd@denx.muc.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: Wrong parameters for m8xx_gorom() in 2.2.5 / MPC8xx
Date: Thu, 10 Jun 1999 22:32:30 +0200 [thread overview]
Message-ID: <199906102032.WAA25167@denx.muc.de> (raw)
In-Reply-To: Your message of "Thu, 10 Jun 1999 22:24:11 +0200."
A small followup too my previous summary of my first experience
porting 2.2.5 to MPC8xx boards:
arch/ppc/kernel/setup.c says: extern void m8xx_gorom(void);
arch/ppc/kernel/head.S says:
r3 is the board info structure, r4 is the location for starting.
At least one of them is wrong. [BTW: the board info data is never
accessed, so why pass it?]
Wolfgang Denk
--
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"UNIX was not designed to stop you from doing stupid things, because
that would also stop you from doing clever things." - Doug Gwyn
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
reply other threads:[~1999-06-10 20:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199906102032.WAA25167@denx.muc.de \
--to=wd@denx.muc.de \
--cc=linuxppc-dev@lists.linuxppc.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).