>-----Original Message----- >From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Kevin >Hilman >> > > >>> > Anand, >>> > >>> > It looks like the timers are not configured properly or the timer selection has gone wrong. Can >you just compare your previous working defconfig with this and correct the GPTIMER selection? >>> >>> As an aside, I'm seeing the same thing with mainline and Beagle. It does >>> not seem to matter whether the 32k timer or sys_clk is used as the GPTIMER >>> source. Also it does not seem to matter whether GPTIMER1 or GPTIMER12 is >>> configured. Looks like some kind of GPTIMER or GPTIMER-related interrupt >>> problem. Have not had the chance to isolate the exact problem yet, so, >>> other comments welcome. >> >> Not seeing this on overo at least. >> > >And my Beagle is booting fine with mainline and attached .config. Got many choices to choose for .config if I use SDP or LDP defconfigs - omap_3430sdp_defconfig omap_ldp_defconfig Looks like these have not been up-to-date. Not sure which options to choose for these boards. Eg: System V IPC (SYSVIPC) [Y/n/?] y POSIX Message Queues (POSIX_MQUEUE) [N/y/?] (NEW) ??? OMAP PM layer selection 1. No PM layer (OMAP_PM_NONE) (NEW) > 2. No-op/debug PM layer (OMAP_PM_NOOP) (NEW) 3. PM layer implemented using SRF (OMAP_PM_SRF) (NEW) choice[1-3]: > >Kevin -- 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
