Bug 192301 - igb(4) support for Intel i350 not mentioned in HCL
Summary: igb(4) support for Intel i350 not mentioned in HCL
Status: Closed FIXED
Alias: None
Product: Documentation
Classification: Unclassified
Component: Website (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Gavin Atkinson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-01 08:58 UTC by Marie Helene Kvello-Aune
Modified: 2015-01-16 01:39 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marie Helene Kvello-Aune 2014-08-01 08:58:32 UTC 
The hardware compatibility list for FreeBSD 8.3, 8.4, 9.0 and 10.0 (and possibly others) does not state that FreeBSD supports the Intel i350 series cards, while the release notes for 8.3 and 9.0 state support was added in r230848 and r218530 respectively.

HCL 8.3: http://www.freebsd.org/releases/8.3R/hardware.html
HCL 8.4: http://www.freebsd.org/releases/8.4R/hardware.html
HCL 9.0: http://www.freebsd.org/releases/9.0R/hardware.html
HCL 10.0: http://www.freebsd.org/releases/10.0R/hardware.html

RelNotes 8.3: http://www.freebsd.org/releases/8.3R/relnotes-detailed.html
RelNotes 9.0: http://www.freebsd.org/releases/9.0R/relnotes-detailed.html
Comment 1 Glen Barber freebsd_committer freebsd_triage 2014-08-01 15:49:06 UTC 
This is not fixable for prior releases, but is fixable for the upcoming 10.1-R and future releases.
Comment 2 commit-hook freebsd_committer freebsd_triage 2014-10-16 23:07:38 UTC 
A commit references this bug:

Author: gavin
Date: Thu Oct 16 23:07:09 UTC 2014
New revision: 273197
URL: https://svnweb.freebsd.org/changeset/base/273197

Log:
  The igb(4) driver supports 82580, i350, i354, i210 and i211 chipsets too,
  document them.

  PR:		192301
  MFC after:	1 week

Changes:
  head/share/man/man4/igb.4
Comment 3 Gavin Atkinson freebsd_committer freebsd_triage 2014-10-16 23:08:49 UTC 
Thanks for your contribution, I've fixed this in head and will merge in the coming week.  I may have been too late to get this in in time for 10.1, unfortunately.