Re: rm bge supported devices

[Alexander Salmin]

On 2015-12-02 14:12, Reyk Floeter wrote:

n Wed, Dec 02, 2015 at 06:37:19AM -0500, Ted Unangst wrote:

>There are many other product lists, but starting with the two big broadcom
>flavors here. I've had a dozen machines with bge, but none of them were listed
>in the man page. I don't think these product lists are helpful.
>
>1. If you have a device and want to know if it's supported, there's no reverse
>mapping from product to driver. How do I know what driver supports my NC320m
>nic? It's faster to plug it in and find out than to read every ethernet man
>page looking for it. (And then plugging it in anyway after I don't find it
>because these lists are perpetually out of date.)
>
>2. If you have picked a driver and are trying to find a device, these are very
>incomplete guides. Most of the devices aren't for sale anymore. Many of the
>rest are now revision B or revision C and may or may not work.
>
>I think we are better off not maintaining such lists. We document the chip
>(family) supported by the driver. Consult the spec sheet if you want to know
>which chip is on your network card.
>
>There may be exceptional circumstances for some drivers, so I'm not planning to
>delete all the lists all at once, but deal with one family at a time.
>

The last time I used it was when I looked up if the "Intel X540-T2" is
an ix(4) - before I ordered it online.  It is listed in the manpage,
so I didn't bother asking other people or looking up the chipset.  And
it worked, of course.  I think it is convenient for the most common
devices and doesn't have to be a comprehensive list.

Reyk

I don't mind if this information is removed from the manual of the 
device driver but I do mind if this information is lost without being 
implemented somewhere else. Maybe it can be a list on the web FAQ 
somewhere if you don't want it there. I'd also be happy to help maintain 
that list of "known working hardware for driver X".


Alexander

Re: rm bge supported devices

[Theo de Raadt]

> On 2015/12/02 12:09, jus...@postgresql.org wrote:
> > On 2015-12-02 11:37, Ted Unangst wrote:
> > >2. If you have picked a driver and are trying to find a device, these
> > >are very incomplete guides. Most of the devices aren't for sale anymore.
> > >Many of the rest are now revision B or revision C and may or may not work.
> 
> For those of us whose hardware procurement policy typically involves
> ebay, they can be quite useful, they are incomplete but there are loads
> of e.g. the HP nics available, and there are a lot fewer junk results if
> you can search for NC380T/NC382T than "dual port pci express gigabit"
> and have to sift through all the PCI-X ones that have been miscategorised.

I agree with Stuart.

When these lists include chip numbers, that is valuable.  Lists
containing names like Belkin RandomProduct may be less helpful, but
the case hasn't been proven the lists should be removed.

Re: rm bge supported devices

[justin]

On 2015-12-02 16:07, Alexander Salmin wrote:


I don't mind if this information is removed from the manual of the
device driver but I do mind if this information is lost without being
implemented somewhere else. Maybe it can be a list on the web FAQ
somewhere if you don't want it there. I'd also be happy to help
maintain that list of "known working hardware for driver X".


For this kind of thought, the hardware lists could be extracted from
each of the driver man pages, then turned into a "Hardware 
Compatibility

List".  eg:

  1GbE network cards
  **

  Model   Driver
  Intel I340-T2   em
  Intel I340-T4   em
  Intel I350-T2   em
  Intel I350-T4   em


  10GbE network cards
  ***

  Model   Driver
  Intel X350-T4   ix


  Wifi cards
  **

  Model   Driver
  A-Link WL54Hral
  AirLive WN-5000PCI  ral
  Amigo AWI-926W  ral
  AMIT WL531P ral
  AOpen AOI-831   ral
  ASUS WL-130Gral
  ASUS WL-130Nral
  ASUS WIFI-G-AAY ral


Having this info in one easy-to-search location sounds like it would
be even better for some use cases (eg people looking for hardware by
category, instead of by driver).

Thoughts? :)

Regards and best wishes,

Justin Clift

Re: rm bge supported devices

[Bryan Vyhmeister]

On Wed, Dec 02, 2015 at 09:30:30AM -0700, Theo de Raadt wrote:
> I agree with Stuart.
> 
> When these lists include chip numbers, that is valuable.  Lists
> containing names like Belkin RandomProduct may be less helpful, but
> the case hasn't been proven the lists should be removed.

I completely agree as well. I use the lists, particularly for wireless
adapters, to at least get an idea what type of parts to look for on
Amazon or eBay.  Last month I pickup up a urtwn(4) device that I would
never have found had it not been listed in the man page.

Although I haven't checked the bge(4) man page in a long time, I have
checked the em(4) and ix(4) man pages recently in search for hardware. I
would really like to see this information remain in the man pages. I
recognize it can't be totally complete but it at least gives a starting
point. Anyone who looks at the manpage and sees a list of chipsets
followed by "including the following:" should realize that it is not an
exhaustive list.

If this information is removed, it will also lead to many more "Does
this work?" posts on misc@ since many people can't buy hardware for trial
and error.

Bryan

Re: rm bge supported devices

[Stuart Henderson]

On 2015/12/02 16:40, jus...@postgresql.org wrote:
> On 2015-12-02 16:07, Alexander Salmin wrote:
> 
> >I don't mind if this information is removed from the manual of the
> >device driver but I do mind if this information is lost without being
> >implemented somewhere else. Maybe it can be a list on the web FAQ
> >somewhere if you don't want it there. I'd also be happy to help
> >maintain that list of "known working hardware for driver X".
> 
> For this kind of thought, the hardware lists could be extracted from
> each of the driver man pages, then turned into a "Hardware Compatibility
> List".  eg:

We previously had lists by category in the "arch" pages on the website
but they got out of sync, we removed them in favour of having the
information in one place (in the driver manual).

Re: rm bge supported devices

[justin]

On 2015-12-02 17:39, Theo de Raadt wrote:


Sorry to have to tell you - what you propose is competely impossible.
At the low-end, we have experienced numerous cases where model 
numbers

don't change, but chipsets do.  What you propose is not time well
spent.


Oh well.  Another case of theory != reality. :)

+ Justin

Re: rm bge supported devices

[Theo de Raadt]

> > 
> >> I don't mind if this information is removed from the manual of the
> >> device driver but I do mind if this information is lost without 
> >> being
> >> implemented somewhere else. Maybe it can be a list on the web FAQ
> >> somewhere if you don't want it there. I'd also be happy to help
> >> maintain that list of "known working hardware for driver X".
> >
> > For this kind of thought, the hardware lists could be extracted from
> > each of the driver man pages, then turned into a "Hardware 
> > Compatibility
> > List".  eg:
> >
> >   1GbE network cards
> >   **
> >
> >   Model   Driver
> >   Intel I340-T2   em
> >   Intel I340-T4   em
> >   Intel I350-T2   em
> >   Intel I350-T4   em
> >
> >
> >   10GbE network cards
> >   ***
> >
> >   Model   Driver
> >   Intel X350-T4   ix
> >
> >
> >   Wifi cards
> >   **
> >
> >   Model   Driver
> >   A-Link WL54Hral
> >   AirLive WN-5000PCI  ral
> >   Amigo AWI-926W  ral
> >   AMIT WL531P ral
> >   AOpen AOI-831   ral
> >   ASUS WL-130Gral
> >   ASUS WL-130Nral
> >   ASUS WIFI-G-AAY ral
> >
> >
> > Having this info in one easy-to-search location sounds like it would
> > be even better for some use cases (eg people looking for hardware by
> > category, instead of by driver).
> 
> This kind of list could probably benefit from a field like "Supported
> from", indicating which release of OpenBSD added the support.
> 
>eg 5.8, 5.9, etc.

Sorry to have to tell you - what you propose is competely impossible.
At the low-end, we have experienced numerous cases where model numbers
don't change, but chipsets do.  What you propose is not time well
spent.

Re: rm bge supported devices

[justin]

On 2015-12-02 17:24, Stuart Henderson wrote:

On 2015/12/02 16:40, jus...@postgresql.org wrote:

On 2015-12-02 16:07, Alexander Salmin wrote:

>I don't mind if this information is removed from the manual of the
>device driver but I do mind if this information is lost without 
being

>implemented somewhere else. Maybe it can be a list on the web FAQ
>somewhere if you don't want it there. I'd also be happy to help
>maintain that list of "known working hardware for driver X".

For this kind of thought, the hardware lists could be extracted from
each of the driver man pages, then turned into a "Hardware 
Compatibility

List".  eg:


We previously had lists by category in the "arch" pages on the 
website

but they got out of sync, we removed them in favour of having the
information in one place (in the driver manual).


Sorry then.  Newbie-ness showing. ;)

Though since both approaches have been tried now, using hindsight has 
one
of the approaches been markedly better than the others for some use 
cases?


Personally, finding equipment was difficult for me as there's no "whole
category" list at the moment.  But, it's possible I'm an idiot. :D

+ Justin

Re: rm bge supported devices

[Jason McIntyre]

On Wed, Dec 02, 2015 at 06:37:19AM -0500, Ted Unangst wrote:
> There are many other product lists, but starting with the two big broadcom
> flavors here. I've had a dozen machines with bge, but none of them were listed
> in the man page. I don't think these product lists are helpful.
> 
> 1. If you have a device and want to know if it's supported, there's no reverse
> mapping from product to driver. How do I know what driver supports my NC320m
> nic? It's faster to plug it in and find out than to read every ethernet man
> page looking for it. (And then plugging it in anyway after I don't find it
> because these lists are perpetually out of date.)
> 
> 2. If you have picked a driver and are trying to find a device, these are very
> incomplete guides. Most of the devices aren't for sale anymore. Many of the
> rest are now revision B or revision C and may or may not work.
> 
> I think we are better off not maintaining such lists. We document the chip
> (family) supported by the driver. Consult the spec sheet if you want to know
> which chip is on your network card.
> 
> There may be exceptional circumstances for some drivers, so I'm not planning 
> to
> delete all the lists all at once, but deal with one family at a time.
> 

i disagree. it takes .2 of a second to grep the man pages. if nothing
shows up, so what. you're no worse off. but if you get a match, great.

why undo what's already there? we all know it's impossible to list
everything. it doesn;t mean we can;t list whatever it is we know works.

this diff will just make things more inconsistent, without any benefit
that i can see.

jmc

> Index: bge.4
> ===
> RCS file: /cvs/src/share/man/man4/bge.4,v
> retrieving revision 1.65
> diff -u -p -r1.65 bge.4
> --- bge.4 27 Jan 2015 01:38:53 -  1.65
> +++ bge.4 2 Dec 2015 11:25:17 -
> @@ -45,59 +45,7 @@ The
>  .Nm
>  driver provides support for various NICs based on the Broadcom BCM570x,
>  571x, 572x, 575x, 576x, 578x, 5776x and 5778x Gigabit Ethernet controller
> -chips and the 590x and 5779x Fast Ethernet controller chips,
> -including the following:
> -.Pp
> -.Bl -bullet -compact
> -.It
> -3Com 3c996-T (10/100/1000baseT)
> -.It
> -3Com 3c996-SX (1000baseSX)
> -.It
> -3Com 3c996B-T (10/100/1000baseT)
> -.It
> -Allied-Telesis AT-2972LX10/LC
> -.It
> -Fujitsu PW0G8GE1U (1000baseSX)
> -.It
> -Fujitsu PW0G8GE2U (10/100/1000baseT)
> -.It
> -Fujitsu PW008GE4 (1000baseSX)
> -.It
> -Fujitsu PW008GE5 (10/100/1000baseT)
> -.It
> -Fujitsu PW008QG1U (10/100/1000baseT)
> -.It
> -HP ProLiant NC320T PCI-E Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC320m PCI-E Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC370F PCI-X Gigabit NIC (1000baseSX)
> -.It
> -HP ProLiant NC370T PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC1020 PCI Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC6770 PCI-X Gigabit NIC (1000baseSX)
> -.It
> -HP ProLiant NC7760 embedded PCI Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC7771 PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC7780 embedded PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC7782 embedded PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -Netgear GA302T (10/100/1000baseT)
> -.It
> -SysKonnect SK-9D21 (10/100/1000baseT)
> -.It
> -SysKonnect SK-9D41 (1000baseSX)
> -.El
> +chips and the 590x and 5779x Fast Ethernet controller chips.
>  .Pp
>  The
>  .Nm
> Index: bnx.4
> ===
> RCS file: /cvs/src/share/man/man4/bnx.4,v
> retrieving revision 1.30
> diff -u -p -r1.30 bnx.4
> --- bnx.4 14 Sep 2014 00:17:09 -  1.30
> +++ bnx.4 2 Dec 2015 11:25:30 -
> @@ -44,28 +44,6 @@ The
>  .Nm
>  driver supports Broadcom's NetXtreme II product family which is made up of
>  the BCM5706, BCM5708, BCM5709, and BCM5716 Ethernet controller chips.
> -Products using these controller chips include:
> -.Pp
> -.Bl -bullet -compact
> -.It
> -HP NC370F PCI-X Multifunction Gigabit server adapter (1000baseSX)
> -.It
> -HP NC370T PCI-X Multifunction Gigabit server adapter (10/100/1000baseT)
> -.It
> -HP Dual NC370i Multifunction Gigabit embedded server adapter 
> (10/100/1000baseT)
> -.It
> -HP NC373F PCI Express Multifunction Gigabit server adapter (1000baseSX)
> -.It
> -HP NC373i PCI Express Multifunction Gigabit embedded server adapter 
> (10/100/1000baseT)
> -.It
> -HP NC374m PCI Express Multifunction Gigabit embedded server adapter 
> (10/100/1000baseT)
> -.It
> -HP NC373T PCI Express Multifunction Gigabit server adapter (10/100/1000baseT)
> -.It
> -HP NC380T PCI Express Dual Port Multifunction Gigabit server adapter 
> (10/100/1000baseT)
> -.It
> -HP NC382T PCI Express Dual Port server adapter (10/100/1000baseT)
> -.El
>  .Pp
>  The NetXtreme II 

rm bge supported devices

[Ted Unangst]

There are many other product lists, but starting with the two big broadcom
flavors here. I've had a dozen machines with bge, but none of them were listed
in the man page. I don't think these product lists are helpful.

1. If you have a device and want to know if it's supported, there's no reverse
mapping from product to driver. How do I know what driver supports my NC320m
nic? It's faster to plug it in and find out than to read every ethernet man
page looking for it. (And then plugging it in anyway after I don't find it
because these lists are perpetually out of date.)

2. If you have picked a driver and are trying to find a device, these are very
incomplete guides. Most of the devices aren't for sale anymore. Many of the
rest are now revision B or revision C and may or may not work.

I think we are better off not maintaining such lists. We document the chip
(family) supported by the driver. Consult the spec sheet if you want to know
which chip is on your network card.

There may be exceptional circumstances for some drivers, so I'm not planning to
delete all the lists all at once, but deal with one family at a time.

Index: bge.4
===
RCS file: /cvs/src/share/man/man4/bge.4,v
retrieving revision 1.65
diff -u -p -r1.65 bge.4
--- bge.4   27 Jan 2015 01:38:53 -  1.65
+++ bge.4   2 Dec 2015 11:25:17 -
@@ -45,59 +45,7 @@ The
 .Nm
 driver provides support for various NICs based on the Broadcom BCM570x,
 571x, 572x, 575x, 576x, 578x, 5776x and 5778x Gigabit Ethernet controller
-chips and the 590x and 5779x Fast Ethernet controller chips,
-including the following:
-.Pp
-.Bl -bullet -compact
-.It
-3Com 3c996-T (10/100/1000baseT)
-.It
-3Com 3c996-SX (1000baseSX)
-.It
-3Com 3c996B-T (10/100/1000baseT)
-.It
-Allied-Telesis AT-2972LX10/LC
-.It
-Fujitsu PW0G8GE1U (1000baseSX)
-.It
-Fujitsu PW0G8GE2U (10/100/1000baseT)
-.It
-Fujitsu PW008GE4 (1000baseSX)
-.It
-Fujitsu PW008GE5 (10/100/1000baseT)
-.It
-Fujitsu PW008QG1U (10/100/1000baseT)
-.It
-HP ProLiant NC320T PCI-E Gigabit NIC (10/100/1000baseT)
-.It
-HP ProLiant NC320m PCI-E Gigabit NIC (10/100/1000baseT)
-.It
-HP ProLiant NC370F PCI-X Gigabit NIC (1000baseSX)
-.It
-HP ProLiant NC370T PCI-X Gigabit NIC (10/100/1000baseT)
-.It
-HP ProLiant NC1020 PCI Gigabit NIC (10/100/1000baseT)
-.It
-HP ProLiant NC6770 PCI-X Gigabit NIC (1000baseSX)
-.It
-HP ProLiant NC7760 embedded PCI Gigabit NIC (10/100/1000baseT)
-.It
-HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseT)
-.It
-HP ProLiant NC7771 PCI-X Gigabit NIC (10/100/1000baseT)
-.It
-HP ProLiant NC7780 embedded PCI-X Gigabit NIC (10/100/1000baseT)
-.It
-HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseT)
-.It
-HP ProLiant NC7782 embedded PCI-X Gigabit NIC (10/100/1000baseT)
-.It
-Netgear GA302T (10/100/1000baseT)
-.It
-SysKonnect SK-9D21 (10/100/1000baseT)
-.It
-SysKonnect SK-9D41 (1000baseSX)
-.El
+chips and the 590x and 5779x Fast Ethernet controller chips.
 .Pp
 The
 .Nm
Index: bnx.4
===
RCS file: /cvs/src/share/man/man4/bnx.4,v
retrieving revision 1.30
diff -u -p -r1.30 bnx.4
--- bnx.4   14 Sep 2014 00:17:09 -  1.30
+++ bnx.4   2 Dec 2015 11:25:30 -
@@ -44,28 +44,6 @@ The
 .Nm
 driver supports Broadcom's NetXtreme II product family which is made up of
 the BCM5706, BCM5708, BCM5709, and BCM5716 Ethernet controller chips.
-Products using these controller chips include:
-.Pp
-.Bl -bullet -compact
-.It
-HP NC370F PCI-X Multifunction Gigabit server adapter (1000baseSX)
-.It
-HP NC370T PCI-X Multifunction Gigabit server adapter (10/100/1000baseT)
-.It
-HP Dual NC370i Multifunction Gigabit embedded server adapter (10/100/1000baseT)
-.It
-HP NC373F PCI Express Multifunction Gigabit server adapter (1000baseSX)
-.It
-HP NC373i PCI Express Multifunction Gigabit embedded server adapter 
(10/100/1000baseT)
-.It
-HP NC374m PCI Express Multifunction Gigabit embedded server adapter 
(10/100/1000baseT)
-.It
-HP NC373T PCI Express Multifunction Gigabit server adapter (10/100/1000baseT)
-.It
-HP NC380T PCI Express Dual Port Multifunction Gigabit server adapter 
(10/100/1000baseT)
-.It
-HP NC382T PCI Express Dual Port server adapter (10/100/1000baseT)
-.El
 .Pp
 The NetXtreme II product family is composed of various Converged NIC (or CNIC)
 Ethernet controllers which support a TCP Offload Engine (TOE),

Re: rm bge supported devices

[Mark Kettenis]

> Date: Wed, 2 Dec 2015 12:32:52 +
> From: Stuart Henderson 
> 
> On 2015/12/02 12:09, jus...@postgresql.org wrote:
> > On 2015-12-02 11:37, Ted Unangst wrote:
> > >2. If you have picked a driver and are trying to find a device, these
> > >are very incomplete guides. Most of the devices aren't for sale anymore.
> > >Many of the rest are now revision B or revision C and may or may not work.
> 
> For those of us whose hardware procurement policy typically involves
> ebay, they can be quite useful, they are incomplete but there are loads
> of e.g. the HP nics available, and there are a lot fewer junk results if
> you can search for NC380T/NC382T than "dual port pci express gigabit"
> and have to sift through all the PCI-X ones that have been miscategorised.

Given what sthen@ says here, I'm on the fence.  While the list isn't
complete, I do think it is listing a significant fraction of the
available hardware.  Yes there is a lot of bge(4) hardware out there
that isn't listed, but most of that is unlisted because it is onboard.

Re: rm bge supported devices

[Reyk Floeter]

On Wed, Dec 02, 2015 at 06:37:19AM -0500, Ted Unangst wrote:
> There are many other product lists, but starting with the two big broadcom
> flavors here. I've had a dozen machines with bge, but none of them were listed
> in the man page. I don't think these product lists are helpful.
> 
> 1. If you have a device and want to know if it's supported, there's no reverse
> mapping from product to driver. How do I know what driver supports my NC320m
> nic? It's faster to plug it in and find out than to read every ethernet man
> page looking for it. (And then plugging it in anyway after I don't find it
> because these lists are perpetually out of date.)
> 
> 2. If you have picked a driver and are trying to find a device, these are very
> incomplete guides. Most of the devices aren't for sale anymore. Many of the
> rest are now revision B or revision C and may or may not work.
> 
> I think we are better off not maintaining such lists. We document the chip
> (family) supported by the driver. Consult the spec sheet if you want to know
> which chip is on your network card.
> 
> There may be exceptional circumstances for some drivers, so I'm not planning 
> to
> delete all the lists all at once, but deal with one family at a time.
> 

The last time I used it was when I looked up if the "Intel X540-T2" is
an ix(4) - before I ordered it online.  It is listed in the manpage,
so I didn't bother asking other people or looking up the chipset.  And
it worked, of course.  I think it is convenient for the most common
devices and doesn't have to be a comprehensive list.

Reyk

> Index: bge.4
> ===
> RCS file: /cvs/src/share/man/man4/bge.4,v
> retrieving revision 1.65
> diff -u -p -r1.65 bge.4
> --- bge.4 27 Jan 2015 01:38:53 -  1.65
> +++ bge.4 2 Dec 2015 11:25:17 -
> @@ -45,59 +45,7 @@ The
>  .Nm
>  driver provides support for various NICs based on the Broadcom BCM570x,
>  571x, 572x, 575x, 576x, 578x, 5776x and 5778x Gigabit Ethernet controller
> -chips and the 590x and 5779x Fast Ethernet controller chips,
> -including the following:
> -.Pp
> -.Bl -bullet -compact
> -.It
> -3Com 3c996-T (10/100/1000baseT)
> -.It
> -3Com 3c996-SX (1000baseSX)
> -.It
> -3Com 3c996B-T (10/100/1000baseT)
> -.It
> -Allied-Telesis AT-2972LX10/LC
> -.It
> -Fujitsu PW0G8GE1U (1000baseSX)
> -.It
> -Fujitsu PW0G8GE2U (10/100/1000baseT)
> -.It
> -Fujitsu PW008GE4 (1000baseSX)
> -.It
> -Fujitsu PW008GE5 (10/100/1000baseT)
> -.It
> -Fujitsu PW008QG1U (10/100/1000baseT)
> -.It
> -HP ProLiant NC320T PCI-E Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC320m PCI-E Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC370F PCI-X Gigabit NIC (1000baseSX)
> -.It
> -HP ProLiant NC370T PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC1020 PCI Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC6770 PCI-X Gigabit NIC (1000baseSX)
> -.It
> -HP ProLiant NC7760 embedded PCI Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC7770 PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC7771 PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC7780 embedded PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC7781 embedded PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -HP ProLiant NC7782 embedded PCI-X Gigabit NIC (10/100/1000baseT)
> -.It
> -Netgear GA302T (10/100/1000baseT)
> -.It
> -SysKonnect SK-9D21 (10/100/1000baseT)
> -.It
> -SysKonnect SK-9D41 (1000baseSX)
> -.El
> +chips and the 590x and 5779x Fast Ethernet controller chips.
>  .Pp
>  The
>  .Nm
> Index: bnx.4
> ===
> RCS file: /cvs/src/share/man/man4/bnx.4,v
> retrieving revision 1.30
> diff -u -p -r1.30 bnx.4
> --- bnx.4 14 Sep 2014 00:17:09 -  1.30
> +++ bnx.4 2 Dec 2015 11:25:30 -
> @@ -44,28 +44,6 @@ The
>  .Nm
>  driver supports Broadcom's NetXtreme II product family which is made up of
>  the BCM5706, BCM5708, BCM5709, and BCM5716 Ethernet controller chips.
> -Products using these controller chips include:
> -.Pp
> -.Bl -bullet -compact
> -.It
> -HP NC370F PCI-X Multifunction Gigabit server adapter (1000baseSX)
> -.It
> -HP NC370T PCI-X Multifunction Gigabit server adapter (10/100/1000baseT)
> -.It
> -HP Dual NC370i Multifunction Gigabit embedded server adapter 
> (10/100/1000baseT)
> -.It
> -HP NC373F PCI Express Multifunction Gigabit server adapter (1000baseSX)
> -.It
> -HP NC373i PCI Express Multifunction Gigabit embedded server adapter 
> (10/100/1000baseT)
> -.It
> -HP NC374m PCI Express Multifunction Gigabit embedded server adapter 
> (10/100/1000baseT)
> -.It
> -HP NC373T PCI Express Multifunction Gigabit server adapter (10/100/1000baseT)
> -.It
> -HP NC380T PCI Express Dual Port Multifunction Gigabit server adapter 
> (10/100/1000baseT)
> -.It
> -HP NC382T PCI Express Dual Port server adapter (10/100/1000baseT)
> -.El
>  .Pp
>  The NetXtreme II product family is composed of various