[Bug 207413] MFC of r295323 - intel e1000 update

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Feb 22 11:10:11 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207413

            Bug ID: 207413
           Summary: MFC of r295323 - intel e1000 update
           Product: Base System
           Version: 10.2-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Keywords: IntelNetworking
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: oliver.pinter at balabit.com
                CC: erj at freebsd.org, gnn at FreeBSD.org, marius at FreeBSD.org,
                    op at hardenedbsd.org, re at FreeBSD.org, sbruno at FreeBSD.org
             Flags: mfc-stable10?

Please MFC the e1000 update, which adds support for the newest Intel Network
cards.

The original commit marked this as MFC after 2 weeks, which expired and still
not MFCd:

Update em(4) to 7.6.1; update igb(4) to 2.5.3.

Major changes:

    Add i219/i219(2) hardware support. (Found on Skylake generation and newer
chipsets.)
        Further to the last Skylake support diff, this one also includes
support for the Lewisburg chipset (i219(3)).

    Add a workaround to an igb hardware errata. All 1G server products need to
have IPv6 extension header parsing turned off. This should be listed in the
specification updates for current 1G server products, e.g. for i350 it's errata
#37 in this document:
http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/ethernet-controller-i350-spec-update.pdf

    Avoton (i354) PHY errata workaround added

And a bunch of minor fixes, as well as #defines for things that the current
em(4)/igb(4) drivers don't implement.

Differential Revision: https://reviews.freebsd.org/D3162
Reviewed by: sbruno, marius, gnn
Approved by: gnn
MFC after: 2 weeks
Sponsored by: Intel Corporation

https://reviews.freebsd.org/rS295323

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list