> > > should do their builds with the multi-omap selected. > > > > > > Also the distros want multi-omap. Only the product > specific kernels > > > should be built with only one option selected to optimize for > > > speed and size. > > I think most of the things are in place for multi-omap for > OMAP4 as well if all the comments are taken care. > > Yeah cool. Looks like the gic interrupt code can also be initialized > from the init_common_hw or so. Of course the entry-macro.S still > needs a separate non-optimized handler for things to boot, I'll > update an earlier patch for that at some point. > Yes it is initialised from common hw init. Regards Santosh-- 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
