linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Micha Nelissen <micha@neli.hopto.org>
To: Aggrwal Poonam-B10812 <B10812@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] e500v2 36 bit large physical HID0[EN_MAS7_UPDATE]
Date: Wed, 16 Jun 2010 13:34:05 +0200	[thread overview]
Message-ID: <4C18B6AD.3030200@neli.hopto.org> (raw)
In-Reply-To: <8660DA277DC57B4BAAC78225F03146B6AB1BB3@zin33exm24.fsl.freescale.net>

Aggrwal Poonam-B10812 wrote:
> Not sure of other platforms but on 85xx platforms on which I am
> currently working u-boot does LAW and eLBC programming for 36bit
> physical address. Hence 
> possibly u-boot has to made aware of large physical address space.
> Please correct me if I am wrong.

Yes, I can understand this for SDRAM and local flash interface. For 
RapidIO we have (local) patches to pass the law address range in the 
dtb. Perhaps also for PCI-express this might be done; U-boot has nothing 
to with these high speed interfaces (in our case at least).

Micha

  reply	other threads:[~2010-06-16 11:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16  6:58 [PATCH] e500v2 36 bit large physical HID0[EN_MAS7_UPDATE] Micha Nelissen
2010-06-16  7:29 ` Aggrwal Poonam-B10812
2010-06-16  9:24   ` Micha Nelissen
2010-06-16 10:49     ` Aggrwal Poonam-B10812
2010-06-16 11:34       ` Micha Nelissen [this message]
2010-06-16 11:38         ` Aggrwal Poonam-B10812
2010-06-16 14:23     ` Timur Tabi
2010-06-16 14:52       ` Micha Nelissen
2010-06-22 22:39       ` Scott Wood
2010-06-16 15:01 ` Kumar Gala
2010-06-16 15:12   ` Micha Nelissen
2010-06-16 15:18     ` Micha Nelissen

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=4C18B6AD.3030200@neli.hopto.org \
    --to=micha@neli.hopto.org \
    --cc=B10812@freescale.com \
    --cc=linuxppc-dev@lists.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).