Date: Sat, 13 Jan 2018 09:30:01 -0500 From: Thomas Laus <lausts@acm.org> To: freebsd-virtualization@freebsd.org Subject: Re: ena(4) is not in GENERIC, now default for some/all instances on AWS EC2 Message-ID: <a5d7358b-256f-6230-1d72-3b38bf170fd8@acm.org> In-Reply-To: <201801130434.w0D4YoQv043280@pdx.rh.CN85.dnsmgr.net> References: <201801130434.w0D4YoQv043280@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/12/18 23:34, Rodney W. Grimes wrote: > > 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. > That resolves the problem for Current, but maybe a better solution for RELENG_11 is to add the ena(4) driver to the GENERIC build script for future 'official' EC2 images that get uploaded to AWS. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a5d7358b-256f-6230-1d72-3b38bf170fd8>