Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759501Ab0GPXtb (ORCPT ); Fri, 16 Jul 2010 19:49:31 -0400 Received: from mail2.shareable.org ([80.68.89.115]:55585 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755004Ab0GPXta (ORCPT ); Fri, 16 Jul 2010 19:49:30 -0400 Date: Sat, 17 Jul 2010 00:49:18 +0100 From: Jamie Lokier To: Daniel Walker Cc: Nicolas Pitre , linux-kbuild@vger.kernel.org, Tony Lindgren , Benjamin Herrenschmidt , linux-kernel@vger.kernel.org, Grant Likely , Linus Torvalds , Russell King , Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= , linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC PATCH] Kconfig: Enable Kconfig fragments to be used for defconfig Message-ID: <20100716234918.GA31060@shareable.org> References: <20100713230352.6781.18644.stgit@angua> <1279062881.4609.34.camel@c-dwalke-linux.qualcomm.com> <1279064008.4609.48.camel@c-dwalke-linux.qualcomm.com> <1279124563.21162.14.camel@c-dwalke-linux.qualcomm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1279124563.21162.14.camel@c-dwalke-linux.qualcomm.com> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1457 Lines: 32 Daniel Walker wrote: > > But all the rest is arbitrary and could be part of common shared > > profiles or the like in defconfig format. > > I'm sure most people will want to have a config isolated to their > specific device. That to me seems reasonable because everyone wants the > smallest possible kernel they can get for their given device. Indeed, but people who want the smallest possible kernel for their specific device _in a particular use context_ tend to want: - To disable support for parts of the device they aren't using. For example, an SoC with integrated ethernet that isn't actually wired up on their board, or where they're using an external ethernet chip instead for some reason. - To choose what's modular and what isn't, even for integrated parts. For example to control the bootup sequence, they might want to delay integrated USB and IDE initialisation, which is done by making those modular and loading them after bringing up a splash screen earlier in the boot scripts. So there is still a need to be able to override the drivers and settings, but it's still incredibly useful to have defaults which describe the SoC or board accurately. -- Jamie -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/