Date: Sat, 23 Jun 2012 17:29:58 +0100 From: Kate F <kate@elide.org> To: Lukasz Wojcik <lukasz.wojcik@zoho.com>, freebsd-arm@freebsd.org Subject: Re: PHYSMEM_SIZE and a hang on boot for kirkwood Message-ID: <CAA36g0Wj%2BLiATBtcJejT20_otnkpeQ=N16X8ZtHDdjsC=LjGXg@mail.gmail.com> In-Reply-To: <4FE5D495.6020605@zoho.com> References: <CAA36g0U8VUCVMadEAD3rZnVwfnc5wpxpuTgxEADCfLwWGxcYrQ@mail.gmail.com> <4FE5D495.6020605@zoho.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23 June 2012 15:37, Lukasz Wojcik <lukasz.wojcik@zoho.com> wrote: > On 06/23/12 15:45, Kate F wrote: >> >> I believe this is the same problem. Is there a way I can hardcode the >> physical memory size which would be equivalent to 8.3's PHYSMEM_SIZE >> option? >> >> Is is there a better way to solve this, and have the memory size found >> automatically? > > I believe 9.0 is FDT-ized already. Take a look at: > sys/boot/fdt/dts/db88f6281.dts, especially '/memory' node. > > also: > > http://wiki.freebsd.org/FlattenedDeviceTree Whoops. I meant I'm using -CURRENT, of course - because I'm interested in the recent NAND work. The db88f6281.dts tree is exactly what I was looking for. The memory node was indeed set for 512M, as PHYSMEM_SIZE was before FDT. So I set that accordingly: memory { device_type = "memory"; reg = <0x0 0x10000000>; // 256M at 0x0 }; and now 10.0-CURRENT boots just fine, as did 8.3 with the equivalent change. Thank you! -- Kate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAA36g0Wj%2BLiATBtcJejT20_otnkpeQ=N16X8ZtHDdjsC=LjGXg>