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, 14 May 2010 11:16:16 +0100 Message-ID: <20100514101615.GF10339@n2100.arm.linux.org.uk> References: <20100325233248.GM24984@n2100.arm.linux.org.uk> <20100505150209.GC2606@n2100.arm.linux.org.uk> <20100513174023.GB13001@n2100.arm.linux.org.uk> <20100513211951.GH3428@atomide.com> <20100513215825.GC13001@n2100.arm.linux.org.uk> <20100513220139.GO3428@atomide.com> <20100513221229.GD13001@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from caramon.arm.linux.org.uk ([78.32.30.218]:35725 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758956Ab0ENKQg (ORCPT ); Fri, 14 May 2010 06:16:36 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Grazvydas Ignotas Cc: "Shilimkar, Santosh" , Tony Lindgren , "linux-arm-kernel@lists.infradead.org" , "linux-omap@vger.kernel.org" , Tomi Valkeinen On Fri, May 14, 2010 at 01:11:43PM +0300, Grazvydas Ignotas wrote: > It seems you are using DSS2/CONFIG_FB_OMAP2, looks like this patch is > for DSS1/CONFIG_FB_OMAP. > > DSS2 does have a problem on linux-next after 'ARM: Prohibit ioremap() > on kernel managed RAM' I'm going to drop that patch out - but that's not to say it won't return (it will.) > because it also uses reserve_bootmem() in > drivers/video/omap2/vram.c and later ioremap on RAM. Perhaps LMB can > be used to fix that too? WTF is reserve_bootmem doing in a driver?