From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH 02/14] omap: Map only available sram memory Date: Mon, 4 Oct 2010 17:34:38 -0700 Message-ID: <20101005003438.GC3117@atomide.com> References: <1284716878-27667-1-git-send-email-santosh.shilimkar@ti.com> <1284716878-27667-2-git-send-email-santosh.shilimkar@ti.com> <1284716878-27667-3-git-send-email-santosh.shilimkar@ti.com> <20101001225303.GF3117@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:65391 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751129Ab0JEAeu (ORCPT ); Mon, 4 Oct 2010 20:34:50 -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" , "linux-omap@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Russell King - ARM Linux * Grazvydas Ignotas [101004 16:35]: > > Looks like for you " is_sram_locked" function is failing. There was a patch > > in my series from Vikram which was fixing this API. > > > > Do you have this patch applied when you are trying this out ? > > http://www.spinics.net/linux/lists/arm-kernel/msg98697.html > > Well it looks like this only happens on linux-next (was using > next-20101001 version) with this defconfig: > http://notaz.gp2x.de/misc/pnd/config_next_101001_2 > > this has yours and Vikram's patch you mentioned in. Using > omap2plus_defconfig on linux-next or this "bad" defconfig on > linux-omap boots fine, strange. Maybe you need to disable CONFIG_SMP still in for-next? At least one patch is still missing there, that's the TLB broadcast patch we have in omap-testing and sitting in Russell's patch system. Regards, Tony From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Mon, 4 Oct 2010 17:34:38 -0700 Subject: [PATCH 02/14] omap: Map only available sram memory In-Reply-To: References: <1284716878-27667-1-git-send-email-santosh.shilimkar@ti.com> <1284716878-27667-2-git-send-email-santosh.shilimkar@ti.com> <1284716878-27667-3-git-send-email-santosh.shilimkar@ti.com> <20101001225303.GF3117@atomide.com> Message-ID: <20101005003438.GC3117@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Grazvydas Ignotas [101004 16:35]: > > Looks like for you " is_sram_locked" function is failing. There was a patch > > in my series from Vikram which was fixing this API. > > > > Do you have this patch applied when you are trying this out ? > > http://www.spinics.net/linux/lists/arm-kernel/msg98697.html > > Well it looks like this only happens on linux-next (was using > next-20101001 version) with this defconfig: > http://notaz.gp2x.de/misc/pnd/config_next_101001_2 > > this has yours and Vikram's patch you mentioned in. Using > omap2plus_defconfig on linux-next or this "bad" defconfig on > linux-omap boots fine, strange. Maybe you need to disable CONFIG_SMP still in for-next? At least one patch is still missing there, that's the TLB broadcast patch we have in omap-testing and sitting in Russell's patch system. Regards, Tony