On Wed, Sep 17, 2008 at 3:23 PM, twebb <[EMAIL PROTECTED]> wrote: > On Wed, Sep 17, 2008 at 2:59 PM, Koen Kooi <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html >
If you take a look at the http://git.omapzoom.org tree as opposed to the official Linux OMAP tree, that things will be more linear to your 2.6.22.18 tree. I'm currently moving our 2.6.22.18 codebase to 2.6.27-rc3 based on the OMAPZOOM tree and it's faring a lot better then when I tried the official tree. So use OMAPZOOM to quickly jump ahead and once up-to-date you can figure out what the next step is to get more towards the official L-O tree.. Regards ~ Ashwin -- 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
