> -----Original Message----- > From: Grazvydas Ignotas [mailto:notasas@xxxxxxxxx] > Sent: Tuesday, October 05, 2010 5:14 AM > To: Shilimkar, Santosh > Cc: Tony Lindgren; linux-omap@xxxxxxxxxxxxxxx; linux-arm- > kernel@xxxxxxxxxxxxxxxxxxx; Russell King - ARM Linux > Subject: Re: [PATCH 02/14] omap: Map only available sram memory > > > 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. Indeed strange. At least good to know that omap2plus_defconfig on linux-next is booting fine. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
