Govindraj wrote:
> On Tue, Feb 22, 2011 at 3:19 PM, Anand Gadiyar <[email protected]> wrote:
> > Looks like linux-next as of today is broken on at least OMAP4.
> >
> > Turning on earlyprintk, I get a crash in omap_init_mcspi. Disabling
> > CONFIG_SPI_OMAP24XX gets me as far as the following lines from my
> > bootup log, but I haven't attempted to debug further.
>
>
> SPI fix is available but yet be merged its discussed in this thread:
>
> http://dchs.spinics.net/lists/linux-omap/msg46446.html
And the other hack I needed to fix the failure when I disable SPI
is this one (thanks Tarun).
It's just a hack - I hope a better fix will be along shortly.
- Anand
Index: linux-omap-usb/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
===================================================================
--- linux-omap-usb.orig/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
+++ linux-omap-usb/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
@@ -5068,7 +5068,7 @@ static __initdata struct omap_hwmod *oma
&omap44xx_spinlock_hwmod,
/* timer class */
- &omap44xx_timer1_hwmod,
+ /* &omap44xx_timer1_hwmod, */
&omap44xx_timer2_hwmod,
&omap44xx_timer3_hwmod,
&omap44xx_timer4_hwmod,
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
