Arnd Bergmann <arnd@xxxxxxxx> writes: > I would like those drivers to be enabled in some defconfig, so we get > compile-time coverage, but we generally stopped having one-config-per-board > files. > > Maybe we can have a pxa_defconfig file that enables lots of boards > and then we remove the individual configs? We don't have to remove > them all at once, but it would make me very happy if we could at > least kill off some of the ones that are not used regularly. I'll take that part, the pxa_defconfig which covers all pxa boards in arch/arm/mach-pxa. I have a prototype, which of course doesn't boot on any of my pxa platforms (breaks in the very early bootstrap code I think, DEBUG_LL is the next stage). Actually I've not even looked if a single kernel covering pxa2xx and pxa3xx is possible (since recently clock handling was a blocker). Once I have something that at least shows me a sign of life, I'll submit an RFC patch. This work will be orthogonal to Sergei's one, as it is aimed at having one defconfig compiling all mach-pxa/*.c files and the drivers referenced by them. This won't allow removing defconfig files until I have a good idea why my boards are not booting (lubbock, mainstone, mioa701, zylonite, cm-x300). Cheers. -- Robert -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
