From: Wolfgang Denk <wd@denx.de>
To: scarayol@assystembrime.com
Cc: ctrichet@assystembrime.com, linuxppc-embedded@ozlabs.org
Subject: Re: Réf. : Re: starting RAM adress for linux kernel
Date: Fri, 03 Jun 2005 17:58:49 +0200 [thread overview]
Message-ID: <20050603155854.7403CC1512@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 03 Jun 2005 16:55:19 +0200." <OFF1C6B550.9120AF42-ONC1257015.004EFCD3@brime.fr>
Dear Sphie,
in message <OFF1C6B550.9120AF42-ONC1257015.004EFCD3@brime.fr> you wrote:
>
> we need to have the start of Ram at 0x0300 0000 because we use the command
> mem=40M (for uboot) to force Linux
> in the low part of memory and to reserve the high part of memory (218M
> exactly ) for ioremap (for our application) but we keep
I don't see any reason why this would prevent you from mapping the
RAM at physical address 0.
> the same flash mapping (to avoid more problems).
I don't know which problems you want to avoid by your chosen memory
map, but I guess that the problems you *cause* by this choice are
more, and more severe.
> Is the only solution is to inverse the mapping with Ram from 0 to 258M and
> the flash above ?
Yes.
> Finally, will Busybox work with Ram starting at 0x03000000 ?
No, it will not, as BB is application code which requires a running
kernel, and your kernel will not run with such a mapping.
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 may be that our role on this planet is not to worship God but to
create him." - Arthur C. Clarke
next prev parent reply other threads:[~2005-06-03 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 14:55 Réf. : Re: starting RAM adress for linux kernel scarayol
2005-06-03 15:58 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-03 15:06 Steven Blakeslee
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=20050603155854.7403CC1512@atlas.denx.de \
--to=wd@denx.de \
--cc=ctrichet@assystembrime.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=scarayol@assystembrime.com \
/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).