Date: Wed, 21 Feb 2018 19:14:00 +0000 From: George Rosamond <george@ceetonetechnology.com> To: bob prohaska <fbsd@www.zefox.net>, Ian Lepore <ian@freebsd.org> Cc: freebsd-arm@freebsd.org Subject: Re: Custom kernel for RPi2 and 3 Message-ID: <703567cd-0d3e-7f0d-f2e7-48ef68911ff2@ceetonetechnology.com> In-Reply-To: <20180221181518.GA696@www.zefox.net> References: <20180220161900.GA2345@www.zefox.net> <c1a82728-a6cd-c972-9b54-73baca644528@zyxst.net> <20180221051801.GA73510@www.zefox.net> <d1e2036f-fb9e-71fa-0918-8b904f16a807@ceetonetechnology.com> <1519229812.91697.61.camel@freebsd.org> <20180221181518.GA696@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
bob prohaska: > 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. AFAIK, there's never been a simple way to compare GENERIC to the hardware in any easy way. In years past, I spent the time going line-by-line and trying to tinker with it. And the expansion of FreeBSD's abilities have added a lot of weight to the kernel. But I can imagine a script that takes GENERIC, filters what is in dmesg and what is vital to boot, then gives dumps out a working, smaller custom GENERIC. Maybe Ian sees something in /usr/src/Makefile that I missed again :) g
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?703567cd-0d3e-7f0d-f2e7-48ef68911ff2>