Embedded PowerPC with more than 2Go of RAM.

Embedded PowerPC with more than 2Go of RAM.

[Laurent Lagrange]

Hi all,

We want to design a PCI host embedded PowerPC board with a 3Go local RAM
memory.
This processor is a MPC74xx with an internal 32 bits and an external 36 bits
address bus.

Usually, the mapping is :
0x00000000-0x80000000 : physical RAM
0x80000000-0xc0000000 : PCI memory access
0xc0000000-0xf0000000 : kernel virtual memory
0xf0000000-0xffffffff : IO area access

1) On this board, the physical memory will be :
0x00000000-0xc0000000 : physical RAM
Where could we map PCI memory space ?

2) The kernel virtual memory usually has the same size as the physical RAM
(two memory footprint for the same physical space ! ).
The kernel virtual memory will be :
0xc0000000-0x180000000 : kernel virtual memory
Where could we map IO space ?

3) Usually, all the host memory is mapped on pci bus. For a 32bits pci bus,
we could not do this.
Is it possible to only map on pci, the DMA memory area which is managed with
the kmalloc(size, GFP_DMA)
and kfree functions ? How can we set the DMA memory parameters (base address
and size) ?

Thanks for any idea

Laurent

Re: Embedded PowerPC with more than 2Go of RAM.

[Roger Larsson]

On Monday 30 May 2005 11.55, Laurent Lagrange wrote:
> Hi all,
>
> We want to design a PCI host embedded PowerPC board with a 3Go local RAM
> memory.
> This processor is a MPC74xx with an internal 32 bits and an external 36
> bits address bus.

In that case it should have some a mechanism for mapping virtual address range
(32 bits) to physical (36 bits).

>
> Usually, the mapping is :
   physical, only using 32 bits
> 0x00000000-0x80000000 : physical RAM
> 0x80000000-0xc0000000 : PCI memory access
> 0xc0000000-0xf0000000 : kernel virtual memory
> 0xf0000000-0xffffffff : IO area access

First attempt: I would try to put the PCI memory range at
0x100000000-140000000 (above 32 bits addressable)

But this will require the drivers to doing things correctly...

Second attempt: Do you need all RAM to be directly usable by user application?
Or would it be enough to be able to use it as a RAM disk? (with that amount
of memory my guess is that this is what you really want!) Should it be nice to 
have it persistant over reboots?
In that case put the RAM disk part above 32 bits addressable, only that RAM
disk driver needs to handle the specific nature of this memory (DMA memory
to memory). And several years ago I saw some ramdisk driver that could were
persistent (BIOS and linux RAM memory init was set not to touch it).
Add some standby power to it and it will be persistent over power failures 
too..
Then ask yourself - does it need to be memory mapped? Or would a IDE like
interface be enough???

/RogerL

pci card memory card with SATA interface

[Roger Larsson]

Noticed this related announcement...

http://www.anandtech.com/tradeshows/showdoc.aspx?i=2431&p=5

/RogerL