* Premi, Sanjeev <[email protected]> [110627 06:24]: > > [sp] While I take my time understanding things on devel-timer; > I had a quick question - at risk of being flamed. > > Adding a new machine ID would trickle to u-boot and same > uImage (default) may not work across board revisions.
Yes that's a hassle :( Until we have device tree, maybe see if u-boot passes ATAG_REVISION that's available as system_rev in kernel? > How does this scheme look like: > - GPTIMER1 is used as default - as it works for most boards. > - GPTIMER12 is used based on a static config option OR a > board specific bootarg > > I know both these options aren't general practice. Still > wanted to know your views in the current context. Let's not do a Kconfig option, but a cmdline option should work if done in a generic way. If you decide to go that way, then please add that to timer.c against devel-timer branch. Regards, Tony -- 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
