From: Ben Gamari <bgamari.foss@gmail.com>
Cc: Felipe Balbi <balbi@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] omap2-beagle: Depend upon CONFIG_GPIO_TWL4030
Date: Thu, 20 Jan 2011 16:44:42 -0500 [thread overview]
Message-ID: <8739ondzcl.fsf@gmail.com> (raw)
In-Reply-To: <20110120040825.GB2389@legolas.emea.dhcp.ti.com>
--text follows this line--
On Thu, 20 Jan 2011 06:08:25 +0200, Felipe Balbi <balbi@ti.com> wrote:
> On Wed, Jan 19, 2011 at 03:04:13PM -0500, Ben Gamari wrote:
> > 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.
>
Certainly, I was trying to point out that there is no good way to
package a configuration for a given board, which definitely increases
the learning curve for a board integrator.
> > 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.
>
Fair enough.
> 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.
>
On the whole x86 hardware is far more uniform than ARM hardware. There
is a good reason why there used to be so many defconfigs for ARM in the tree.
Cheers,
- Ben
WARNING: multiple messages have this Message-ID (diff)
From: bgamari.foss@gmail.com (Ben Gamari)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap2-beagle: Depend upon CONFIG_GPIO_TWL4030
Date: Thu, 20 Jan 2011 16:44:42 -0500 [thread overview]
Message-ID: <8739ondzcl.fsf@gmail.com> (raw)
In-Reply-To: <20110120040825.GB2389@legolas.emea.dhcp.ti.com>
--text follows this line--
On Thu, 20 Jan 2011 06:08:25 +0200, Felipe Balbi <balbi@ti.com> wrote:
> On Wed, Jan 19, 2011 at 03:04:13PM -0500, Ben Gamari wrote:
> > 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.
>
Certainly, I was trying to point out that there is no good way to
package a configuration for a given board, which definitely increases
the learning curve for a board integrator.
> > 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.
>
Fair enough.
> 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.
>
On the whole x86 hardware is far more uniform than ARM hardware. There
is a good reason why there used to be so many defconfigs for ARM in the tree.
Cheers,
- Ben
next prev parent reply other threads:[~2011-01-20 21:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 21:25 [PATCH] omap2-beagle: Depend upon CONFIG_GPIO_TWL4030 Ben Gamari
2011-01-17 21:25 ` Ben Gamari
2011-01-18 3:10 ` Felipe Balbi
2011-01-18 3:10 ` Felipe Balbi
2011-01-18 13:51 ` Ben Gamari
2011-01-18 13:51 ` Ben Gamari
2011-01-19 3:45 ` Felipe Balbi
2011-01-19 3:45 ` Felipe Balbi
2011-01-19 20:04 ` Ben Gamari
2011-01-19 20:04 ` Ben Gamari
2011-01-20 4:08 ` Felipe Balbi
2011-01-20 4:08 ` Felipe Balbi
2011-01-20 17:27 ` Tony Lindgren
2011-01-20 17:27 ` Tony Lindgren
2011-01-20 21:44 ` Ben Gamari [this message]
2011-01-20 21:44 ` Ben Gamari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8739ondzcl.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.