Date: Fri, 12 Jan 2018 20:34:50 -0800 (PST) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Joel Dahl <joel@vnode.se> Cc: Maxim Sobolev <sobomax@freebsd.org>, Marcin Wojtas <mw@semihalf.com>, freebsd-virtualization@freebsd.org, mk@semihalf.com Subject: Re: ena(4) is not in GENERIC, now default for some/all instances on AWS EC2 Message-ID: <201801130434.w0D4YoQv043280@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <20180112190423.GC39759@ymer.vnode.se>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Thu, Jan 11, 2018 at 10:14:55AM -0800, Maxim Sobolev wrote: > > Well, that might work, but I am curious why do we have all other network 40 > > or so drivers in the GENERIC but not this one. Considering significant > > portion of FreeBSD systems deployed these days are going to be running on > > the cloud this makes no sense to me. Is there some policy out there which > > governs such decisions? > > Email current@ and ask if there are any objections before you add it to > GENERIC? There is work going on in -current by Warner (imp@) called devmatch that makes this issue go away and rips out all the other drivers from GENERIC that can be automatically loaded by devmatch in the future. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201801130434.w0D4YoQv043280>