From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: [RFC] Initial attempt to make ARM use LMB Date: Fri, 28 May 2010 15:32:07 +0100 Message-ID: <20100528143207.GB25568@n2100.arm.linux.org.uk> References: <20100325233248.GM24984@n2100.arm.linux.org.uk> <20100522215848.GB29889@n2100.arm.linux.org.uk> <20100526004418.GM9645@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from caramon.arm.linux.org.uk ([78.32.30.218]:41154 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750916Ab0E1OcW (ORCPT ); Fri, 28 May 2010 10:32:22 -0400 Content-Disposition: inline In-Reply-To: <20100526004418.GM9645@atomide.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Tony Lindgren Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, Tomi Valkeinen On Tue, May 25, 2010 at 05:44:18PM -0700, Tony Lindgren wrote: > Also, the last patch in lmb branch "ARM: use LMB to allocate system > memory MMIO resource structures" causes both osk5912 and n900 > to hang very early. Maybe I'm missing some patch again.. I'll drop this patch for the time being - we don't have stuff in the right order yet for lmb_alloc() to work immediately after arm_lmb_init() with highmem present - lmb_alloc tries to allocate from unmapped or high memory, which we then use __va() on and referencing the resulting pointer causes an abort. However, using lmb_alloc() for the OMAP framebuffers shouldn't be an issue because the problem only happens if you want to immediately dereference the memory.