From: Paul Mackerras <paulus@samba.org>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: Tom Rini <trini@kernel.crashing.org>,
Michael Sokolov <msokolov@ivan.Harhan.ORG>,
linux-galileo@source.mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: [Linux-galileo] ev64260 bi_rec patch
Date: Tue, 2 Apr 2002 12:50:56 +1000 (EST) [thread overview]
Message-ID: <15529.7312.132845.46847@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <3CA87831.974F719D@mvista.com>
Mark A. Greer writes:
> > So the always-correct call for platform_init() is:
> > parse_bootinfo((struct bi_record *) (r3 + KERNELBASE));
>
> Is there a reason we shouldn't just fix find_bootinfo then?
The reason why I split the original parse_bootinfo into two pieces,
find_bootinfo and parse_bootinfo, was to allow for the case where the
bootloader passes in the address of the bi_recs. In other words,
if you know where the bi_recs are, you don't need to call
find_bootinfo, just parse_bootinfo.
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-02 2:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 23:59 [Linux-galileo] ev64260 bi_rec patch Michael Sokolov
2002-03-29 22:24 ` Mark A. Greer
2002-03-29 22:30 ` Mark A. Greer
2002-03-29 22:41 ` Mark A. Greer
2002-03-30 0:45 ` Michael Sokolov
2002-04-01 15:20 ` Tom Rini
2002-04-01 15:25 ` Tom Rini
2002-04-01 15:09 ` Mark A. Greer
2002-04-01 18:53 ` Tom Rini
2002-04-01 19:52 ` Michael Sokolov
2002-04-01 20:21 ` Tom Rini
2002-04-02 2:38 ` Paul Mackerras
2002-04-02 2:50 ` Paul Mackerras [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-30 0:42 Michael Sokolov
2002-04-01 19:31 Michael Sokolov
2002-04-01 18:03 ` Mark A. Greer
2002-04-01 20:09 Michael Sokolov
2002-04-02 3:35 Michael Sokolov
2002-04-03 5:09 ` Troy Benjegerdes
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=15529.7312.132845.46847@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linux-galileo@source.mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mgreer@mvista.com \
--cc=msokolov@ivan.Harhan.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).