diff options
| author | Benjamin Herrenschmidt <benh@kernel.crashing.org> | 2006-03-03 10:35:40 +1100 |
|---|---|---|
| committer | Paul Mackerras <paulus@samba.org> | 2006-03-03 22:01:05 +1100 |
| commit | ab1b55e21f6977e420341727e9f4a50691057b5e (patch) | |
| tree | f2b6c25bc8bd40db6b5dda217dc3c29a4ce06127 /include | |
| parent | 141aa59b5347a4a021e37cfbc2258df9af9392f8 (diff) | |
| download | linux-ab1b55e21f6977e420341727e9f4a50691057b5e.tar.gz | |
[PATCH] powerpc: incorrect rmo_top handling in prom_init
On Thu, 2006-03-02 at 19:55 +0100, Olaf Hering wrote:
> My iBook1 has 2 memory regions in reg. Depending on how I boot it
> (vmlinux+initrd) or zImage.initrd, it will not boot with current Linus
> tree.
> rmo_top should be 160MB instead of 32MB.
On logically-partitioned machines the first element of the reg
property in the memory node is defined to be the "RMO" region,
i.e. the memory that the processor can access in real mode. On other
machines the first element has no special meaning, so only take it to
be the RMO region on LPAR machines.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions