>> Thanks Robert, >> >> The 3.4.4 kernel is plain vanilla plus: >> >> http://rcn-ee.net/deb/sid-armhf/v3.4.4-x1/patch-3.4.4-x1.diff.gz >> >> We're running archlinuxarm, and working with devs there to upgrade to 3.5.4, >> in hopes this will address most or all of the issues. That will include: >> >> http://rcn-ee.net/deb/sid-armhf/v3.5.4-x6/patch-3.5.4-x6.diff.gz >> >> We adopted archlinux because it's about as close to a git kernel as can be >> had in a disto packaged format. > > Ah, so my external patchset... Well, for the patch, nothing actually > changed between 3.4.3-x1 -> 3.4.4-x1... (besides the stable patchset) > > https://github.com/RobertCNelson/stable-kernel/commits/v3.4.x/ > > (the 3 commits are related to scripts in that git repo.) > > So, i would first look at the config (zcat /proc/config.gz) between > those two releases, and if the arch developers added any more patches > to it.. https://github.com/archlinuxarm/PKGBUILDs/commit/68a9e5a1609fde10a2f31dac8df211f0c3874eb7 It looks like they disabled CONFIG_OMAP_RESET_CLOCKS I'm pretty sure that would force you to be stuck with what ever u-boot sets up for those pins... Regards, -- Robert Nelson http://www.rcn-ee.com/ -- 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
