From: Felix Radensky <felix@allot.com>
To: linuxppc-embedded@ozlabs.org
Subject: 405GPr ioremap problem
Date: Tue, 09 Nov 2004 19:27:09 +0200 [thread overview]
Message-ID: <4190FDED.3080605@allot.com> (raw)
Hi, folks
I have a 405GPr based board with 512M of RAM.
My kernel is 2.4.17 from Monta Vista Linux 2.1.
I'm trying to reserve 64M on boot using mem=448M
and map it later by
ioremap(__pa(high_memory), 64*(1<<20));
This worked fine when system had 256M of RAM,
but now ioremap fails. If I understand the kernel
code correctly, by adding more RAM I've reduced
the vmalloc/ioremap space. I can also see that this
space is reduced dramatically on boot by mappings
done in arch/ppc/kernel/ppc4xx_setup.c:m4xx_map_io()
Is there any way to fix problem ? Is it necessary to have
a 1:1 virtual to physical mappings as its done in m4xx_map_io()
or maybe higher virtual addresses can be used, thus
allowing to save some precious ioremap space.
Thanks a lot in advance.
Please CC me, as I'm not on the list.
Felix.
next reply other threads:[~2004-11-09 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 17:27 Felix Radensky [this message]
2004-11-09 18:17 ` 405GPr ioremap problem Matt Porter
2004-11-10 18:37 ` Felix Radensky
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=4190FDED.3080605@allot.com \
--to=felix@allot.com \
--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).