Date: Wed, 21 Feb 2018 15:03:27 -0700 From: Warner Losh <imp@bsdimp.com> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.cn85.dnsmgr.net> Cc: Ian Lepore <ian@freebsd.org>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: Custom kernel for RPi2 and 3 Message-ID: <CANCZdfpKNePC8wR-nHvmBN_AV=beSStKngprdeAWcHUC=Zi=kA@mail.gmail.com> In-Reply-To: <201802211958.w1LJwnhu087548@pdx.rh.CN85.dnsmgr.net> References: <1519242042.91697.116.camel@freebsd.org> <201802211958.w1LJwnhu087548@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 21, 2018 at 12:58 PM, Rodney W. Grimes < freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > Last time I tried to support the issue of people should really be > building a custom kernel and not running GENERIC I pretty much > got shot down as "this is 2018 no one should have to build a > kernel". > The current plan for 12 is that we'll gut GENERIC like a fish, at least on x86, and ship with a more minimal kernel. Everything that can be loaded as a module automatically will be loaded (there's some things that can't or could be but with a crazy amount of work, those wills till be static). The devmatch work I've done is driving it, but it isn't fully realized in -current yet since there's lots of PCI drivers that need love. For ARM specifically, we need a lot of work on the FDT side of the house to get there, and there's some issues about the best place to do the loading that might not be worked out by the branch for 12. Having a better story for embedded is needed regardless of the progress towards automatic loading. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpKNePC8wR-nHvmBN_AV=beSStKngprdeAWcHUC=Zi=kA>