From: Wolfgang Denk <wd@denx.de>
To: David Hawkins <dwh@ovro.caltech.edu>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux on PPC
Date: Sat, 04 Mar 2006 03:05:29 +0100 [thread overview]
Message-ID: <20060304020529.F1CDF352627@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 03 Mar 2006 08:53:07 PST." <44087473.6020905@ovro.caltech.edu>
In message <44087473.6020905@ovro.caltech.edu> you wrote:
>
> > Many memory maps (especially those provides with some eval boards for
> > demonstration purpose) will NOT work with Linux. Remember that the
> > memory map is usually not cast in silicon, but implemented in
> > software, so you can change it as needed.
>
> Right, thats I made sure to say; Physical Memory Map.
That's what I mean: the physical memory map is usually set up in
software, so it can be changed to your needs.
> For example, on the Artesyn manual on their PrPMC they give a
> physical memory map, and in the Yosemite board, there is a
> physical memory map. I know many of the memory areas can be
> redefined in hardware to have a different memory location, but
> its still a physical address.
...which usually can be reprogrammed in software.
> Now, when the bootloader loads, eg. U-Boot, it sets up the
> memory management. Now this is where my understanding gets
> shakey, since I haven't looked at much of the code, so perhaps
> you can clarify. The translation unit (TLB) maps virtual addresses
> (or should that be MMU output addresses) into physical addresses,
U-Boot usually does not use the MMU.
> What are the basic requirements for a Linux memory map then?
See the FAQ.
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
It is surely a great calamity for a human being to have no ob-
sessions. - Robert Bly
next prev parent reply other threads:[~2006-03-04 2:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 2:01 Linux on PPC rtos
2006-03-03 2:23 ` Frank
2006-03-03 5:09 ` nreddy
2006-03-03 16:00 ` Wolfgang Denk
2006-03-03 5:10 ` David Hawkins
2006-03-03 9:33 ` Adrian Cox
2006-03-03 16:04 ` Wolfgang Denk
2006-03-03 16:53 ` David Hawkins
2006-03-04 2:05 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-03 19:39 Rune Torgersen
2006-03-03 20:06 ` David Hawkins
2006-03-04 2:09 ` Wolfgang Denk
2006-03-04 2:51 ` David Hawkins
2006-03-03 20:28 Steve Strublic
2006-03-03 20:31 Rune Torgersen
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=20060304020529.F1CDF352627@atlas.denx.de \
--to=wd@denx.de \
--cc=dwh@ovro.caltech.edu \
--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).