OpenCores
URL https://opencores.org/ocsvn/or1k_old/or1k_old/trunk

Subversion Repositories or1k_old

[/] [or1k_old/] [trunk/] [rc203soc/] [sw/] [uClinux/] [Documentation/] [more-than-900MB-RAM.txt] - Diff between revs 1765 and 1782

Only display areas with differences | Details | Blame | View Log

Rev 1765 Rev 1782
This document describes how to configure the Linux kernel to
This document describes how to configure the Linux kernel to
support more than 950MB physical RAM on x86 systems:
support more than 950MB physical RAM on x86 systems:
you only have to change the 'Max physical memory in MB' kernel
you only have to change the 'Max physical memory in MB' kernel
config option to get everything working. If you have less than
config option to get everything working. If you have less than
900M RAM, dont touch the default setting, this option buys you
900M RAM, dont touch the default setting, this option buys you
nothing at all! The option is in 'General setup':
nothing at all! The option is in 'General setup':
          [ ] Kernel math emulation
          [ ] Kernel math emulation
          (1800)  Max physical memory in MB
          (1800)  Max physical memory in MB
          [*] Networking support
          [*] Networking support
          [ ] Limit memory to low 16MB
          [ ] Limit memory to low 16MB
the unit of CONFIG_MAX_MEMSIZE is 'megabytes', ie. a value of
the unit of CONFIG_MAX_MEMSIZE is 'megabytes', ie. a value of
'1024' means '1024 MBytes'. Unless in 2.1 there is no restriction
'1024' means '1024 MBytes'. Unless in 2.1 there is no restriction
on the value of CONFIG_MAX_MEMSIZE!
on the value of CONFIG_MAX_MEMSIZE!
IMPORTANT: the value of CONFIG_MAX_MEMSIZE should be about 128M
IMPORTANT: the value of CONFIG_MAX_MEMSIZE should be about 128M
more than the amount of physical RAM (or 1024 if RAM is less than
more than the amount of physical RAM (or 1024 if RAM is less than
900M), because the kernel needs some space for it's own memory
900M), because the kernel needs some space for it's own memory
mappings. The kernel enforces this 128M window by clipping away
mappings. The kernel enforces this 128M window by clipping away
from the end of phsyical memory if necessary. (in this case that
from the end of phsyical memory if necessary. (in this case that
chunk of physical memory is not used by Linux!) So configure this
chunk of physical memory is not used by Linux!) So configure this
option carefully, and look at 'free' output and boot messages
option carefully, and look at 'free' output and boot messages
wether all RAM is correctly detected and configured.
wether all RAM is correctly detected and configured.
A system with 2G physical memory should use a value of ~2400, a
A system with 2G physical memory should use a value of ~2400, a
system with 3.8G memory should use something like 3900. A bit of
system with 3.8G memory should use something like 3900. A bit of
experimentation with the limit wont hurt, the kernel needs a ~128M
experimentation with the limit wont hurt, the kernel needs a ~128M
window for vmalloc() plus PCI space uses up some memory too, thus
window for vmalloc() plus PCI space uses up some memory too, thus
physical addresses above FD000000 should rather be kept free.
physical addresses above FD000000 should rather be kept free.
if the BIOS does not report correct memory size, use the mem= boot
if the BIOS does not report correct memory size, use the mem= boot
commandline option to override it.
commandline option to override it.
feel free to report any problems/suggestions to:
feel free to report any problems/suggestions to:
         Ingo Molnar 
         Ingo Molnar 
 
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.