Tony Lindgren <tony@xxxxxxxxxxx> writes: > * Tony Lindgren <tony@xxxxxxxxxxx> [080229 05:29]: >> * Adrian Bunk <bunk@xxxxxxxxxx> [080229 02:49]: >> > On Fri, Feb 29, 2008 at 12:07:52PM +0900, Kyungmin Park wrote: >> > > >> > > > > > That build blog is missing something critical: builds for >> > > > > > all OMAP platforms in ** MAINLINE ** kernels. Not just the >> > > > > > Linux-OMAP tree. >> > > > > > >> > > > > > ... >> > > > > >> > > > > It already exists for mainline, thanks to the people from Simtec: >> > > > > http://armlinux.simtec.co.uk/kautobuild/ >> > > > >> > > > Then maybe the OMAP build blog should link to that too, so >> > > > there's one-stop-shopping for OMAP related kernel build problems. >> > > > >> > > > >> > > > > As regards the H3 case, maybe I've look at it too quick but there's no >> > > > > defconfig in mainline and it's not the only one :( Having the missing >> > > > > defconfigs merged would help noticing build breakages. >> > > > >> > > > Good point. >> > > >> > > Yes, there are a lot of defconfigs are missing including apollon in mainline. >> > > >> > > How about to add missing defconfigs to mainline to work both mainline and omap tree? >> > >> > Sounds good - and I'd suggest aiming at getting them into 2.6.25 and >> > trying to get them into Linus' tree soon. >> >> We could have one generic config covering all 15xx and 16xx boards >> rather than add all them separately. This would provide the same build >> info as multiple board configs and save some Kautobuild cycles. > > Having one omap_1xxx_defconfig with all possible boards also helps with the > issue that some boards are missing drivers in mainline kernel to make > them usable. Why not. What matters is that there's a defconfig. Being able to boot a kernel made with this config would be nice but I don't know if this can be a show-stopper. What's the next step ? Are you sending a defconfig to RMK ? Arnaud -- 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
