linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Walter L. Wimer III" <walt.wimer@timesys.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: IMAP_ADDR on PPC 8xx
Date: Tue, 09 May 2006 00:46:53 +0200	[thread overview]
Message-ID: <20060508224653.C4B48352B0C@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 08 May 2006 13:23:03 EDT." <1147108983.27101.63.camel@excalibur.timesys.com>

In message <1147108983.27101.63.camel@excalibur.timesys.com> you wrote:
> 
> In particular, I have an MPC885ADS board running "U-Boot 1.1.3 (Apr 19
> 2005 - 13:39:58)".  It will boot neither 2.6.15 nor 2.6.16.11.  After
> U-Boot decompresses the kernel, I get no kernel output at all; it just
> hangs.

Probably you forgot to specify a correct  console  device  with  your
boot arguments.

> After some debugging, I think things go awry when the code starts
> dereferencing IMAP_ADDR as a direct pointer.  IMAP_ADDR is defined to be
> 0xFF000000, but the MPC885ADS documentation says that the internal

Correct.

> memory map is supposed to at 0x22000000.  In addition, when I look at
> the bd_t pointer from U-Boot, it's saying that 0x22000000 is the correct
> address.

No. U-Boot uses 0xFF000000. At least the official U-Boot source  tree
does. I don't know where you got yours from, or who might have broken
it.

> Why is this a problem for us and apparently not for anyone else on this
> list?  Is no one else using U-Boot?  Or does everyone else's U-Boot use
> 0xFF000000 instead of 0x22000000?  Or do I have a different problem

Most probably everybody else who uses U-Boot uses a good version with
a high mapping.

> While reading through the archives, I see that using IMAP_ADDR the way
> it is currently used is somewhat frowned upon anyway.  Is this one of
> those things that we (the PPC Linux community) should fix the "right
> way" once and for all?  I'm happy to submit a patch once I understand
> what the "right way" is...  :-)

The memory map requirements of PowerPC systems  have  been  explained
many  times  before,  so a little search in the archives, HOWTOs etc.
should point you quickly for good description why a low mapping  like
0x22000000 cannot work.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Hokey religions and ancient weapons are  no  substitute  for  a  good
blaster at your side.                                      - Han Solo

  reply	other threads:[~2006-05-08 22:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08 17:23 IMAP_ADDR on PPC 8xx Walter L. Wimer III
2006-05-08 22:46 ` Wolfgang Denk [this message]
2006-05-09 17:14   ` Walter L. Wimer III
2006-05-09 20:22     ` Wolfgang Denk
2006-05-09 20:46       ` Walter L. Wimer III
  -- strict thread matches above, loose matches on Subject: below --
2006-05-09 18:38 Kenneth Poole
2006-05-09 19:52 ` Walter L. Wimer III
2006-05-09 21:51   ` Dan Malek
2006-05-10 15:23     ` Walter L. Wimer III
2006-05-10 16:49       ` Walter L. Wimer III
2006-05-10 17:45         ` Dan Malek
2006-05-10 19:58           ` John Rigby
2006-05-10 20:19           ` Walter L. Wimer III

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=20060508224653.C4B48352B0C@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=walt.wimer@timesys.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).