Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755669Ab0GLUyo (ORCPT ); Mon, 12 Jul 2010 16:54:44 -0400 Received: from relais.videotron.ca ([24.201.245.36]:10672 "EHLO relais.videotron.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754818Ab0GLUux (ORCPT ); Mon, 12 Jul 2010 16:50:53 -0400 MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_GqcioTTQWFIwCVRgfELxZQ)" Date: Mon, 12 Jul 2010 16:50:51 -0400 (EDT) From: Nicolas Pitre X-X-Sender: nico@xanadu.home To: Arnd Bergmann Cc: =?ISO-8859-15?Q?Uwe_Kleine-K=F6nig?= , Linus Torvalds , Russell King - ARM Linux , Daniel Walker , Kevin Hilman , Linux Kernel Mailing List , linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Grant Likely , Eric Miao , linux-omap@vger.kernel.org Subject: Re: ARM defconfig files In-reply-to: <201007122231.16283.arnd@arndb.de> Message-id: References: <20100712185029.GB14425@pengutronix.de> <201007122231.16283.arnd@arndb.de> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2142 Lines: 47 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --Boundary_(ID_GqcioTTQWFIwCVRgfELxZQ) Content-type: TEXT/PLAIN; charset=iso-8859-1 Content-transfer-encoding: 8BIT On Mon, 12 Jul 2010, Arnd Bergmann wrote: > On Monday 12 July 2010 20:50:29 Uwe Kleine-K?nig wrote: > > > > [1] The following changes since commit 67a3e12b05e055c0415c556a315a3d3eb637e29e: > > > > Linux 2.6.35-rc1 (2010-05-30 13:21:02 -0700) > > > > are available in the git repository at: > > git://git.pengutronix.de/git/ukl/linux-2.6.git arm/defconfig/reduced-v2.6.35-rc1 > > BTW, looking at the most common entries in there, I think we might at some > point want to change some of the defaults in the respective Kconfig files. > Right now an empty defconfig would result in a configuration without > file system, networking or modules: We need to come up with a scheme that allows for expressing the most likely options you might want if you have machine x and/or machine y selected. Those likely options are for drivers corresponding to hardware soldered on the board or integrated into a SOC and therefore which is not "optional". Right now this information is carried in the defconfig files. Without that you need to lookup various datasheets and wade through thousands of Kconfig options. Compared to that, stuff like filesystems and networking protocols are optional items that currently are more arbitrarily included into or excluded from the defconfig files. I think that the first category of options should automatically be selected on a per machine basis depending on BASE_CONFIG or the like and expressed directly in the Kconfig files. Typically there are very few of those (like a dozen or so for some example target I looked at). Nicolas --Boundary_(ID_GqcioTTQWFIwCVRgfELxZQ)-- -- 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/