Date: Thu, 1 Nov 2012 01:20:07 +0400 From: Ruslan Bukin <br@bsdpad.com> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-arm@freebsd.org Subject: Re: exynos4412 hangs on enabling MMU Message-ID: <20121031212007.GA48430@jail.io> In-Reply-To: <7FA4A9AA-F217-4425-9A21-E0967237540C@bsdimp.com> References: <20121030123231.GA91006@jail.io> <1351607803.1120.27.camel@revolution.hippie.lan> <7FA4A9AA-F217-4425-9A21-E0967237540C@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 30, 2012 at 10:08:21AM -0600, Warner Losh wrote: > > > On Tue, 2012-10-30 at 16:32 +0400, Ruslan Bukin wrote: > >> hello! > >> > >> exynos hangs on mcr cmd in this context: > >> > >> /* Enable MMU */ > >> [..] > >> orr r0, r0, #(CPU_CONTROL_MMU_ENABLE | CPU_CONTROL_DC_ENABLE) > >> mcr p15, 0, r0, c1, c0, 0 > >> [..] > >> > >> without CPU_CONTROL_MMU_ENABLE flag, mcr command works, > >> but board hangs again on line: > >> str r3, [r1], #0x0004 /* get zero init data */ > >> > >> any suggestions? > >> > >> -Ruslan > > > > I'd be interested in tracking that down... I've been booting lots of armv5 boards lately and haven't seen this hang with current. just read CPU_CONTROL_MMU_ENABLE bit from arm using mrc command, and it shows that MMU is enabled after mcr cmd (without using CPU_CONTROL_MMU_ENABLE bit), and disabled before. So MMU switch seems works. but board still hangs on line: str r3, [r1], #0x0004 /* get zero init data */ -Ruslan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121031212007.GA48430>