From owner-svn-src-head@FreeBSD.ORG Sun Mar 23 11:52:06 2014 Return-Path: Delivered-To: svn-src-head@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA667503; Sun, 23 Mar 2014 11:52:06 +0000 (UTC) Received: from nibbler.fubar.geek.nz (nibbler.fubar.geek.nz [199.48.134.198]) by mx1.freebsd.org (Postfix) with ESMTP id C91F7F5C; Sun, 23 Mar 2014 11:52:06 +0000 (UTC) Received: from bender.Home (97e07ba1.skybroadband.com [151.224.123.161]) by nibbler.fubar.geek.nz (Postfix) with ESMTPSA id 117AE5DEB7; Sun, 23 Mar 2014 11:51:56 +0000 (UTC) Date: Sun, 23 Mar 2014 11:51:50 +0000 From: Andrew Turner To: Ian Lepore Subject: Re: svn commit: r263424 - head/sys/arm/conf Message-ID: <20140323115150.51e68e2a@bender.Home> In-Reply-To: <1395494755.81853.38.camel@revolution.hippie.lan> References: <201403201701.s2KH1L84024044@svn.freebsd.org> <20140321094316.76ccf459@bender.Home> <1395412070.81853.8.camel@revolution.hippie.lan> <20140321190402.GT32089@funkthat.com> <1395494755.81853.38.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: svn-src-head@FreeBSD.org, John-Mark Gurney , Ruslan Bukin , src-committers@FreeBSD.org, svn-src-all@FreeBSD.org X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Mar 2014 11:52:07 -0000 On Sat, 22 Mar 2014 07:25:55 -0600 Ian Lepore wrote: > Last time I tried to put something into arm/conf/DEFAULTS I got my > hand slapped, but... putting the diagnostic options in there on head > and not on stable branches would make the "touch 77 config files" > problem go away. This is another problem we have on ARM, we are abusing FDT_DTS_FILE. We should work to reduce the number of kernel configs we have where possible. My preference would be for no more than one config for each SoC/SoC family, however the granularity depends on the hardware and SoC specific code. Andrew