Re: linuxppc_2_4_devel Memory map on PPC / MPC5200

2 messages, 2 authors, 2004-03-08 · open the first message on its own page

Re: linuxppc_2_4_devel Memory map on PPC / MPC5200

From: Wolfgang Denk <hidden>
Date: 2004-03-08 14:11:24

In message [off-list ref] you wrote:
But talking about this, I see in mpc5xxx_common
...
        io_block_mapping(0x40000000, 0x40000000, 0x10000000, _PAGE_IO);
        io_block_mapping(0x50000000, 0x50000000, 0x01000000, _PAGE_IO);
        io_block_mapping(0x80000000, 0x80000000, 0x10000000, _PAGE_IO);
        io_block_mapping(0xf0000000, 0xf0000000, 0x10000000, _PAGE_IO);
}
...
But then, what are the 3 other mappings ?
See the U-Boot sources ("include/configs/IceCube.h").

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
How long does it take a  DEC  field  service  engineer  to  change  a
lightbulb?       It depends on how many bad ones he brought with him.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: linuxppc_2_4_devel Memory map on PPC / MPC5200

From: Sylvain Munaut <hidden>
Date: 2004-03-08 16:28:59

Hi

Wolfgang Denk wrote:
In message [off-list ref] you wrote:

quoted
But talking about this, I see in mpc5xxx_common
...

quoted
       io_block_mapping(0x40000000, 0x40000000, 0x10000000, _PAGE_IO);
       io_block_mapping(0x50000000, 0x50000000, 0x01000000, _PAGE_IO);
       io_block_mapping(0x80000000, 0x80000000, 0x10000000, _PAGE_IO);
       io_block_mapping(0xf0000000, 0xf0000000, 0x10000000, _PAGE_IO);
}
...

quoted
But then, what are the 3 other mappings ?
See the U-Boot sources ("include/configs/IceCube.h").
I've just read the IceCube.h file as well as the mpc5xxx init code ( in
the cpu/mpc5xxx, board/icecube and some in lib_ppc ).

So yes, indeed U-Boot, does change the MBAR from it's boot default to
0xf000000 and setup the PCI Mem & IO space to 0x40000000 & 0x50000000.
Sorry I should have searched more in details what uboot does before asking.

What still surprises me is that it's mapped before the 0x80000000, so
isn't that inside the zone of per-process mapping ? ( < TASK_SIZE ).

As far as I understand it, Uboot does not use the mmu, it just ensure
that it's all clear ( tlb, bat, ... ). And I don't see anywhere what
could 0x8000000 be ? It's not the MBAR anymore. And I don't see anything
there anymore but still it can't be a map to nowhere ?


Thanks a lot.

    Sylvain Munaut

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help