From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Atm account <linux2@cdotd.ernet.in>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Problem in booting PPC with kernel 2.5.44
Date: 14 Nov 2002 14:36:21 +0100 [thread overview]
Message-ID: <1037280982.877.14.camel@zion> (raw)
In-Reply-To: <Pine.OSF.4.10.10211131428120.9066-100000@moon.cdotd.ernet.in>
On Wed, 2002-11-13 at 10:52, Atm account wrote:
>
> Hello All,
> We are porting Linux 2.5.44 for our custom board which has
> 603e processor..
> We are using the arch/ppc/boot/simple bootloader with minor
> modifications. At the end of boot-code relocation to 8 Mb, the code jumps
> to the relocated code and thereafter
> does the decompression (decompress_kernel)of the vmlinux image to physical
> address 0 and jumps to the 0th location (3 nops followed by code). It is
> from here that early_init is called.
> Now the problem is ... the kernel has been linked at 3GB and a call in
> kernel/head.S which says ---
> bl early_init
> translates to sth like => bl 0Xc000xxxx
> I dont have the MMU on at this point nor any dual mapping being done
> thru the BATs. So how is the above code supposed to execute ?????
> Our board precisely hangs after this jump.
Those are relative branches, not absolute.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-11-14 13:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-14 7:34 help needed for porting linux-2.5 to a ppc custom board Atm account
2002-09-16 18:16 ` Ricardo Scop
2002-09-16 18:21 ` Ricardo Scop
2002-11-13 9:52 ` Problem in booting PPC with kernel 2.5.44 Atm account
2002-11-14 13:36 ` Benjamin Herrenschmidt [this message]
2002-11-14 15:11 ` Tom Rini
2002-11-15 11:24 ` Atm account
2002-11-15 16:17 ` Tom Rini
2002-11-15 16:26 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2002-11-14 6:06 Atm account
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=1037280982.877.14.camel@zion \
--to=benh@kernel.crashing.org \
--cc=linux2@cdotd.ernet.in \
--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).