Please note the commit below, in particular the UPDATING entry.
In short, if you use 
  em ix ixv ixl iavf vmx
drivers and compile them into kernel statically, you need to add
device iflib to your configs.

Standard in-tree configs were updated, so if you do e.g. 'include GENERIC'
you do not need to do anything.

----- Forwarded message from Konstantin Belousov <k...@freebsd.org> -----

Date: Fri, 15 Feb 2019 09:49:09 +0000 (UTC)
From: Konstantin Belousov <k...@freebsd.org>
To: src-committ...@freebsd.org, svn-src-...@freebsd.org,
        svn-src-sta...@freebsd.org, svn-src-stable...@freebsd.org
Subject: svn commit: r344149 - in stable/12: . share/man/man4 sys/amd64/conf
        sys/arm64/conf sys/conf sys/dev/ixgbe sys/i386/conf sys/mips/conf
        sys/modules sys/modules/iflib sys/powerpc/conf sys/powerpc/conf...

Author: kib
Date: Fri Feb 15 09:49:09 2019
New Revision: 344149
URL: https://svnweb.freebsd.org/changeset/base/344149

Log:
  MFC r343617, r343618:
  Make iflib a loadable module.

Modified: stable/12/UPDATING
==============================================================================
--- stable/12/UPDATING  Fri Feb 15 09:45:17 2019        (r344148)
+++ stable/12/UPDATING  Fri Feb 15 09:49:09 2019        (r344149)
@@ -16,6 +16,13 @@ from older versions of FreeBSD, try WITHOUT_CLANG and 
 the tip of head, and then rebuild without this option. The bootstrap process
 from older version of current across the gcc/clang cutover is a bit fragile.
 
+20190214:
+       Iflib is no longer unconditionally compiled into the kernel.  Drivers
+       using iflib and statically compiled into the kernel, now require
+       the 'device iflib' config option.  For the same drivers loaded as
+       modules on kernels not having 'device iflib', the iflib.ko module
+       is loaded automatically.
+
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Reply via email to