boot process

[Aleksey V Fedorov]

Hi!

On Mon, 23 Feb 2009, Rafal Jaworowski wrote:

> 2. Hack e500_init() routine in the kernel to hard code some config data it
> normally gets from loader, like physical RAM size, memory regions number etc.,
> CCSR base address, CCB clock frequency, maybe something more, see e500_init()
> for details.

What is regular method to allocate some piece of memory in e500_init() for 
unflatten device tree structures? Board loader provide pointer to to the 
device-tree block in r3(i.e. void *mdp argument of e500_init()).
I can parse them, but where to store tree at this point?


--