All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: 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: Mon, 01 Apr 2002 10:09:37 -0500	[thread overview]
Message-ID: <3CA87831.974F719D@mvista.com> (raw)
In-Reply-To: 20020401152507.GB6360@opus.bloom.county


Tom Rini wrote:

> OK.  The problem is that the original PPC location of the bi_recs was

Acutally, my problem was that I misread his respone.  I thought he was trying to
say the find_bootinfo was in the bootloader or something like that.

> 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?

Mark


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-04-01 15:09 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 [this message]
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
  -- 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=3CA87831.974F719D@mvista.com \
    --to=mgreer@mvista.com \
    --cc=linux-galileo@source.mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.