From: Dan Malek <dan@netx4.com>
To: Murray Jensen <Murray.Jensen@cmst.csiro.au>
Cc: Steve Tarr <tarr@lucent.com>,
LINUX-PPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Motorola MPC8260-ADS Boot hassel
Date: Fri, 02 Jun 2000 10:06:46 -0400 [thread overview]
Message-ID: <3937BF76.BB429A58@embeddededge.com> (raw)
In-Reply-To: 430.959920193@msa.cmst.csiro.au
Murray Jensen wrote:
> >relocated to: 00400000 0040B288
> >board data at: 00407140 00407164 <= this is within range on line above
> >relocated to: 00200100 00200124
> The secondary boot code is being relocated over the top of the board data
> (before it is relocated). Perhaps this is your problem?
This is telling you everything is fine. The initial board data in
this case is part of the first relocated image. This is moved to
the following address (0x200100). It's irrelevant in this case to
move the data, but to simplify the logic it is always done. In the
case where the initial board data is part of the flash rom or (the
right way) passed to you by the boot rom, it must be relocated.
> - if (current == bdflush_tsk)
> + if (bdflush_tsk == 0 || current == bdflush_tsk)
This is the real solution to the problem. Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-02 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 14:54 Motorola MPC8260-ADS Boot hassel Steve Tarr
2000-06-01 23:25 ` Dan Malek
2000-06-01 18:02 ` Steve Tarr
2000-06-02 0:49 ` Dan Malek
2000-06-02 4:29 ` Murray Jensen
2000-06-02 14:06 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-02 21:13 Steve Tarr
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=3937BF76.BB429A58@embeddededge.com \
--to=dan@netx4.com \
--cc=Murray.Jensen@cmst.csiro.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tarr@lucent.com \
/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).