On Wed, Sep 17, 2008 at 2:59 PM, Koen Kooi <k.kooi@xxxxxxxxxxxxxxxxxx> wrote: > > Why 2.6.25? Git has 2.6.26 already and currenly is at 2.6.27rc6, so why go > from one obsolete version to another obsolete one? .27rc is pretty broken on > the EVM atm, ut .26 should work fine. > Was going with 2.6.25 because once I get basic functionality on the EVM with linux-omap-2.6.25, next step is applying a separate 2.6.25-based patch. So 2.6.26 should work OK on 35xEVM? If so, I'll see if patch applies without problems and give it a try. Does anyone (TI?) know how far apart their linux-2.6.22.18 (SDK 1.0.0) is from the linux-omap-2.6.git and when they might converge? Along these lines, which defconfig to use for OMAP35x EVM: SDK = omap3evm_defconfig or linux-omap-2.6.25 = omap3_evm_defconfig (different names and different contents)? Thanks. twebb -- 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
