On Mon, 10 Mar 2008 23:04:07 -0300, "Luís Vitório Cargnini" <lvcargnini@xxxxxxxxx> wrote: > ebuilding the kernel, my intern will test it tomorrow morning, then > I'll send the results but as you all I do not understood why it > generate so many partitions nad not booted the filesystem, it was > everything ok until 2.6.24, since the last upgrade things stop > working. Might be a regression. If you know the exact point where it was working (2.6.23-omap1 was working ?) then you can git bisect to track down where it broke. Try this: $ git bisect start $ git bisect good v2.6.23-omap1 $ git bisect bad then it'll start a binary search between v2.6.23-omap1 and HEAD and choose one commit in the middle. After it chooses you, build the kernel and flash to see whether it works or not. If it works then you $ git bisect good otherwise you $ git bisect bad You keep doing that until you get the exact commit that broke omap_nor.c -- Best Regards, Felipe Balbi http://felipebalbi.com me@xxxxxxxxxxxxxxx -- 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
