linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: Aman <aman@mistralsoftware.com>
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Hangs after "Now Booting the kernel "
Date: Thu, 31 Oct 2002 07:44:15 -0700	[thread overview]
Message-ID: <20021031074415.A2977@home.com> (raw)
In-Reply-To: <000701c28053$dd0f6610$370da8c0@aman>; from aman@mistralsoftware.com on Thu, Oct 31, 2002 at 02:05:19AM +0530


On Thu, Oct 31, 2002 at 02:05:19AM +0530, Aman wrote:
>
> Hi All
>
> I have build a image using the command make zImage.initrd. This gives a
> linux image zImage.initrd.ebony[Ramdisk + Kernel Image]. This image run fine
> in the PPC440 evalkit. However the same image if I run in my custom board
> which has a 440GP processor, it hangs after saying "now booting the kernel".
> What might be the problem ?.

You might see linuxppc-commit archives or read changeset descriptions for
440 checkins in your BK repo.  Where the image is relocated and the
minimum memory assumption is extremely critical...if you changed any
of it for your custom port you can shoot yourself in the foot.

> I have one more question , is the TLB setting is reconfigured during linux
> image booting , if so is it possible to get the memory map of that.

Read head_440.S

--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

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

  reply	other threads:[~2002-10-31 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 20:35 Hangs after "Now Booting the kernel " Aman
2002-10-31 14:44 ` Matt Porter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31  4:50 Prabhu Kubendran

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=20021031074415.A2977@home.com \
    --to=porter@cox.net \
    --cc=aman@mistralsoftware.com \
    --cc=linuxppc-embedded@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).