From: Matt Porter <mporter@kernel.crashing.org>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Lots of memory on 826x
Date: Tue, 8 Mar 2005 13:32:49 -0700 [thread overview]
Message-ID: <20050308133249.C8434@cox.net> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B8592E9@ismail.innsys.innovsys.com>; from runet@innovsys.com on Tue, Mar 08, 2005 at 12:37:33PM -0600
On Tue, Mar 08, 2005 at 12:37:33PM -0600, Rune Torgersen wrote:
> Ok... Got a little closer....
>
> I have PCI (outbound) mapped in the area 0x80000000-0x8fffffff
> (prefetch/non-prefetch and IO)
> IMMR of cource is at 0xf0000000
>
> So I map the IO as following:
> /* Map IMMR region to a 256MB BAT */
> addr = (cpm2_immr != NULL) ? (uint)cpm2_immr : CPM_MAP_ADDR;
> io_block_mapping(addr, addr, 0x10000000, _PAGE_IO);
>
> io_block_mapping(0x80000000, 0x80000000, 0x10000000, _PAGE_IO);
>
> Now I can almost boot....:
> It craches when trying to read from harddisk
> (only happens with more than 512MB)
That's expected if you are going to 768MB. You have kernel lowmem
being mapped at 0xc0000000+<size_of_system_memory>. With 768MB that
takes you all the way to where you have the IMMR mapped 1:1 I
guess. This leaves no room for vmalloc space. With 768MB of ram
the kernel will calculate VMALLOC_START at 0xf1000000 which is a
problem.
A few options are:
* Move the IMMR much higher to allow vmalloc space
* Modify maximum low memory to limit to 512MB using the advanced
options menu
* Modify KERNELBASE to something like 0xa0000000 using the advanced
options menu
All of these methods will provide addition vmalloc space.
Don't forget to turn on HIGHMEM to use everything above MAX_LOW_MEM.
-Matt
next prev parent reply other threads:[~2005-03-08 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 18:37 Lots of memory on 826x Rune Torgersen
2005-03-08 18:54 ` Mark Chambers
2005-03-08 20:32 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 17:52 Rune Torgersen
2005-03-08 23:35 Rune Torgersen
2005-03-08 23:39 ` Matt Porter
2005-03-08 23:20 Rune Torgersen
2005-03-08 23:30 ` Matt Porter
2005-03-08 21:16 Rune Torgersen
2005-03-08 23:13 ` Kumar Gala
2005-03-08 17:33 Rune Torgersen
2005-03-08 18:06 ` Kumar Gala
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=20050308133249.C8434@cox.net \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=runet@innovsys.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).