[PATCH] omap2-beagle: Depend upon CONFIG_GPIO_TWL4030

Tony Lindgren tony at atomide.com
Thu Jan 20 12:27:41 EST 2011

* Felipe Balbi <balbi at ti.com> [110119 20:07]:
> On Wed, Jan 19, 2011 at 03:04:13PM -0500, Ben Gamari wrote:
> > On Wed, 19 Jan 2011 05:45:28 +0200, Felipe Balbi <balbi at ti.com> wrote:
> > > The point is, being able to disable features I don't want on my kernel
> > > image, is completely valid, if there's a compile breakage, then fix the
> > > breakage but don't prevent the board from compiling.
> > > 
> > I understand. That being said, Linus has made it well known that
> > defconfigs will not be an option going forward. Have we found another
> I never mentioned defconfigs here.
> > means of selecting the basic drivers necessary to get a fully functional
> > board? Perhaps a CONFIG_MACH_OMAP3_BEAGLE_CORE option selecting the
> > necessary driver for a fully functional board would be a solution. I
> I'll leave this for Tony to decide, but I don't like your proposal.
> > remember this being discussed several months ago (when Linus started
> > pulling defconfigs out of the tree), but I don't recall there being any
> > replacement proposals. It should be possible to build a functional
> > kernel from the mainline without iterating over all available
> > configuration options.
> So you're saying that when you're building a kernel for you
> laptop/desktop you don't have to get a menuconfig and choose the drivers
> you want to compile ? I dare to doubt that.

What we want to do in the long run is build a minimal kernel and make
everything else loaded as modules from initramfs. In order to do that
we need to cut down all the dependencies between core omap code and
the drivers. So I'd stay away from selecting things for boards where


More information about the linux-arm-kernel mailing list