linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Dell Query <dell.query@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Unable to Read PPC440EPx Board ID thru Board Control and Status Registers (BCSR)
Date: Tue, 4 Dec 2007 10:28:07 +0100	[thread overview]
Message-ID: <200712041028.07380.sr@denx.de> (raw)
In-Reply-To: <86675.82133.qm@web45613.mail.sp1.yahoo.com>

On Monday 03 December 2007, Dell Query wrote:
> I finally got the new pdf files from other Resource CDs and used 0xc000000
> address, without 0x2000 offset.

Good.

> It works! Thanks a lot for the help.
>
> But may I know why in Linux it is mapped to 0x1c000000, wherein the doc
> stated 0xc000000?

The doc most probably only refers to the virtual address mapped in U-Boot 
here.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office@denx.de
=====================================================================

      reply	other threads:[~2007-12-04  9:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 10:47 Unable to Read PPC440EPx Board ID thru Board Control and Status Registers (BCSR) Dell Query
2007-11-28  3:25 ` Josh Boyer
2007-11-28  6:38   ` Dell Query
2007-11-28 10:51     ` Stefan Roese
2007-11-29  3:16       ` Dell Query
2007-11-29  6:10         ` Stefan Roese
2007-11-29  6:41           ` Dell Query
2007-11-29  6:56             ` Stefan Roese
2007-11-29 10:01               ` Dell Query
2007-11-29 10:13                 ` Stefan Roese
2007-12-03  7:17                   ` Dell Query
2007-12-04  9:28                     ` Stefan Roese [this message]

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=200712041028.07380.sr@denx.de \
    --to=sr@denx.de \
    --cc=dell.query@yahoo.com \
    --cc=linuxppc-embedded@ozlabs.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).