linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Peter Vandenabeele <peter.vandenabeele@mind.be>
To: "Kerl, John" <John.Kerl@Avnet.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Low memory on Virtex-II Pro
Date: Sun, 9 Feb 2003 21:13:39 +0100	[thread overview]
Message-ID: <20030209211339.F25620@mind.be> (raw)
In-Reply-To: <C08678384BE7D311B4D70004ACA37105111946A2@amer22.avnet.com>; from John.Kerl@Avnet.com on Fri, Feb 07, 2003 at 02:56:30PM -0700


On Fri, Feb 07, 2003 at 02:56:30PM -0700, Kerl, John wrote:
>
> Hello all,
>
> There have been some recent posts about Linux & Virtex-II Pro
> (FPGA with PPC405 hard core). & apparently people have it working

Yes.

> One question before I start, though:
>
> Of course the kernel starts at *virtual* address 0xc0000000, regardless
> of the processor.  But my understanding is that certain processors have
> zero-based *physical* addresses for RAM, and some don't -- x86 of course
> being an example of the former, and ARM being an example of the latter.
> I believe that PPC is an example of the former.  Certainly our MPC857T
> board, and all the other boards of which I'm aware, have RAM starting at
> physical address 0x00000000.
>
> Now, on our custom Virtex-II Pro board, with Xilinx EDK setup, there's a
> bit (the MSB) in the physical address that specifies whether a memory
> region is on the LMB bus or OPB bus.  We get to pick *which* bit, but
> there must be *a* bit set for the SDRAM.  The upshot is that our SDRAM
> starts at physical address 0xb0000000.  It can't be placed at address 0.
> And block RAM could be made low, but I can't see having megabytes of
> block RAM.
>
> So, I think I have to have the kernel at non-zero physical address
> with PPC405.
>
> Can anyone advise on success or failure of doing so?

What is your SDRAM controller ?

When we used the Xilinx SDRAM controller IP (softcore), it was easy
to remap the SDRAM physical base address to 0x00000000 in the .mhs
file (in the Xilinx EDK). We found this to be much less work than trying
to force the Linux kernel to boot from another address than 0x00000000.

Coreconnect PLB bus is what you want to use for off-chip memory
(OPB is low-speed peripherals).

Peter

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

  parent reply	other threads:[~2003-02-09 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07 21:56 Low memory on Virtex-II Pro Kerl, John
2003-02-09  4:38 ` Peter Ryser
2003-02-09 18:52 ` Peter 'p2' De Schrijver
2003-02-09 20:13 ` Peter Vandenabeele [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-12 19:33 Kerl, John

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=20030209211339.F25620@mind.be \
    --to=peter.vandenabeele@mind.be \
    --cc=John.Kerl@Avnet.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).