linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Ricardo Severo" <severo.ricardo@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux boot on a ppc 405
Date: Sun, 27 Jan 2008 14:15:56 -0700	[thread overview]
Message-ID: <fa686aa40801271315m5ba4ea08p913fd6235eb1d240@mail.gmail.com> (raw)
In-Reply-To: <479CAF56.30306@gmail.com>

On 1/27/08, Ricardo Severo <severo.ricardo@gmail.com> wrote:
> Hi all,
>
> I am working with a Xilinx Virtex II Pro  evaluation board, wich has two
> PowerPC 405 and I'm trying to boot a vanilla linux kernel 2.6.23.14.
> Until now I've manged to make it uncompress the kernel, but it doesn't boot.
> My question is how the initial execution (the one who uncompresses the
> kernel image) transfers the processor to the kernel itself. I've looked
> in the arch/ppc/boot/simple/relocate.S code and it jumps to the position
> 0x0 after uncompressing, is it right? The kernel is uncompressed at that
> position?

Post your output log please.

If your getting a message that the kernel is uncompressing, but you
don't have any output beyond that then most likely your console is not
setup correctly.  If you've got a debugger, look at memory at the
__log_buf location to see if there are any boot logs there.

Cheers,
g.


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  parent reply	other threads:[~2008-01-27 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27 16:20 Linux boot on a ppc 405 Ricardo Severo
2008-01-27 18:29 ` David Baird
2008-01-27 21:15 ` Grant Likely [this message]
2008-01-28 22:53   ` Ricardo Ayres Severo
2008-01-28 22:55     ` Stephen Neuendorffer
2008-01-28 23:00       ` Ricardo Ayres Severo
2008-01-28 23:02         ` Stephen Neuendorffer
2008-01-28 23:04         ` Grant Likely

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=fa686aa40801271315m5ba4ea08p913fd6235eb1d240@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=severo.ricardo@gmail.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).