From: p2@mind.be (Peter 'p2' De Schrijver)
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 19:52:14 +0100 [thread overview]
Message-ID: <20030209185214.GA841@mind.be> (raw)
In-Reply-To: <C08678384BE7D311B4D70004ACA37105111946A2@amer22.avnet.com>
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.
>
> 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.
>
The 405 has an exception vector pointer register, which is initialized
by linux (linuxppc_2_4_devel cvs tree) with the kernel base. So in
principle it should be possible to have linux run on a system without
memory at address 0. I have never tried this however.
Cheers,
Peter.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-09 18:52 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 [this message]
2003-02-09 20:13 ` Peter Vandenabeele
-- 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=20030209185214.GA841@mind.be \
--to=p2@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).