From owner-freebsd-arm@freebsd.org Wed Feb 21 18:15:26 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF63EF1B679 for ; Wed, 21 Feb 2018 18:15:25 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F36A69D16; Wed, 21 Feb 2018 18:15:25 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w1LIFIYq000756 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 21 Feb 2018 10:15:19 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w1LIFIMj000755; Wed, 21 Feb 2018 10:15:18 -0800 (PST) (envelope-from fbsd) Date: Wed, 21 Feb 2018 10:15:18 -0800 From: bob prohaska To: Ian Lepore Cc: George Rosamond , freebsd-arm@freebsd.org, bob prohaska Subject: Re: Custom kernel for RPi2 and 3 Message-ID: <20180221181518.GA696@www.zefox.net> References: <20180220161900.GA2345@www.zefox.net> <20180221051801.GA73510@www.zefox.net> <1519229812.91697.61.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1519229812.91697.61.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Feb 2018 18:15:26 -0000 On Wed, Feb 21, 2018 at 09:16:52AM -0700, Ian Lepore wrote: > On Wed, 2018-02-21 at 05:44 +0000, George Rosamond wrote: > > bob prohaska: > > > > > > [...] > > Bob: > > > > This script can generate an /etc/src.conf based on the running system, > > extracted from /etc/src.conf(5). Since there's no standard /etc/src.conf > > through FreeBSD versions, it's a hassle to maintain without it. > > > > http://wiki.torbsd.org/doku.php?id=en:a_shell_script_to_convert_src.conf_5_contents_to_an_example_etc_src.conf_file > > > > HTH > > That script looks like a really complicated way to do: > > ? make showconfig __MAKE_CONF=/dev/null SRCCONF=/dev/null > > -- Ian Is there a straightforward way to sort what's being used from what can't (or isn't) being used? For example, on a Pi2 the command emits MK_WIRELESS = yes MK_WIRELESS_SUPPORT = yes Given that there's no onboard wireless and no USB WiFi adapter, it's fairly obvious those two can be set to "no". It's less clear what MK_TEXTPROC = yes portends, and whether it's essential. Perhaps I mis-posed the original question. What I'm looking for might better be called a minimal kernel configuration supporting only the hardware native to a particular board. The old RPI2 kernel config file seemed to do that, but I gather it's deprecated. Thanks for reading! bob prohaska