On Wed, Sep 17, 2008 at 4:11 PM, twebb <[EMAIL PROTECTED]> wrote: > On Wed, Sep 17, 2008 at 3:36 PM, Ashwin Bihari <[EMAIL PROTECTED]> wrote: >>> >>> 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)? >>> >> >> 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 >> > > Great, that's helpful. Do you know omapzoom linux-2.6.25 to be > somewhat functional with OMAP 35x EVM, or would you suggest going with > something newer like v2.6.26-ti-07252008? Or must I go to 2.6.27-rc3? > I assume newer (to a point) would result in better stability on the > 35x EVM? > > Thanks, > twebb >
The EVM is a board option in this tree, so you're going to have the best possible luck with the latest and greatest code base. I have a custom board based on the OMAP3530. So I'm actually adding a new board-type and the necessary pieces appropriate for my platform. 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
