* G, Manjunath Kondaiah <manjugk@xxxxxx> [110311 04:45]: > On Fri, Mar 11, 2011 at 11:05:25AM +0530, DebBarma, Tarun Kanti wrote: > > [...] > > > > > > > > > > * Tarun Kanti DebBarma <tarun.kanti@xxxxxx> [110308 15:41]: > > > > > > switch-over to platform device driver through following changes: > > > > > > (a) initiate dmtimer early initialization from omap2_gp_timer_init() > > > > > > in timer-gp.c. This is equivalent of timer_init()->timer->init(). > > > > > > (b) modify plat-omap/dmtimer routines to use new register map and > > > > > > platform data. > > > > > > > > > > This patch breaks booting for 2420 and makes boot hang early > > > > > on 2430. Note that to test with omap-for-linus branch you need > > > > > to disable the following in omap2plus_defconfig: > > > > > > > > > > CONFIG_ARCH_OMAP3 > > > > > CONFIG_ARCH_OMAP4 > > > > > CONFIG_CPU_32v6K > > > > I disabled above options on omap-for-linus *WITHOUT* my patch series. > > > > I am still seeing crash. Here is the log. > > > > I tried on two different setups. Not sure if I am missing something. > > > > > > Hmm sounds like H4 needs some attention. Can you try the following > > > completely untested patch? > > > > This works fine! > > I tried to use below patch for booting OMAP2420 H4 on top of: > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git > Branch: omap-for-linus > commit 94a06b74e724caabcf0464c81527cfbcae0c8aff > Merge: 0dde52a 9062511 > Author: Tony Lindgren <tony@xxxxxxxxxxx> > Merge branch 'for_2.6.39/pm-misc' of > ssh://master.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm > into omap-for-linus > > Looks like it stops after uncompressing kernel. Same setup works fine > with tag v2.6.37. See the mails earlier in this thread on what you currently need to disable in .config in omap-for-linus branch to boot omap2 machines. This will get sorted out in mainline when Russell's ARMv6K related patches get merged during the merge window. Tony -- 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
