* Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> [101019 17:04]: > Tony Lindgren <tony@xxxxxxxxxxx> writes: > > > > This actually produces a booting omap2+ kernel with no .config > > at all. I've tested it with: > > > > $ echo CONFIG_ARCH_OMAP=y > .config > > $ yes "" | ARCH=arm make oldconfig > > > > So if you have something that's needed on almost every omap, > > you can select it there. > > One thing I don't like about this is that there is currently no way to > 'select' as a module. I think that would take two passes to do currently for the depenencies.. But we can certainly select all the omap drivers as modules in omap2plus_defconfig. > In order to get to a minimal kernel, in theory, we don't need regulator, > i2c, MFD, or twl4030* built in. They should all be built as modules. > Yes, there are some assumptions made today that some of these things are > built in, and then are used from init code, but that is broken. I think the only thing keeping us from doing that is that most of the boards don't use initramfs. Without initramfs these are needed to mount root on MMC. > If someone is looking for a good omap-kernel-janitors project, I would > suggest getting to a *really* minimal OMAP2+ kernel with everything > possible built as modules to be a very good project. Agreed. The way to do that is to set everything possible as modules in omap2plus_defconfig, and move to kernel + initramfs based booting like most distros do. Regards, Tony -- 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
