On Mon, Sep 28, 2009 at 10:04 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > Hi all, > > I've updated our linux-omap tree to v2.6.32-rc1. I've also > added a branch omap-2.6.31 for the old code. > > This time I also nuked the remaining omap legacy code we > still had lurking around :) The commits at the end of this > mail describe what I did first as commits, then I merged > everything to be the same as the mainline v2.6.32-rc1. > > So currently the linux-omap master branch is: > > v2.6.32-rc1 + omap-fixes + ehci + cbus > > The new model is that I'll be resetting the linux-omap master > branch to mainline at each -rc, then merge in our various > upstream queues back in again. Excellent! I was wondering why this wasn't being done. I certainly hope linus' 2.6.32 will work on omap right away. Anyway, I haven't been able to make 2.6.31 boot on beagleboard, and other people report similar issues: http://www.spinics.net/lists/linux-omap/msg17968.html Have you got 2.6.32-rc1 (+fixes) to boot? Cheers. -- Felipe Contreras -- 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
