Date: Tue, 24 Feb 2009 18:47:02 +0300 (MSK) From: Aleksey V Fedorov <alexf@vsi.ru> To: Rafal Jaworowski <raj@semihalf.com> Cc: freebsd-ppc@freebsd.org Subject: Re: boot process Message-ID: <Pine.GSO.4.62.0902241839390.12361@serv1> In-Reply-To: <49A2704F.4060703@semihalf.com> References: <Pine.GSO.4.62.0902212141241.25932@serv1> <49A2704F.4060703@semihalf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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? --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.62.0902241839390.12361>