misc/44811: NetBSD WWW hardware support list should split out NICs by network type

[fair%netbsd.org@localhost]

>Number:         44811
>Category:       misc
>Synopsis:       NetBSD WWW hardware support list should split out NICs by 
>network type
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    misc-bug-people
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 02 01:25:00 +0000 2011
>Originator:     Erik E. Fair
>Release:        n/a
>Organization:
        The NetBSD Project
>Environment:
        NetBSD's web site at http://www.netbsd.org/support/hardware/pci.html
>Description:
        NetBSD now supports a very wide range of network interfaces
        for a wide range of networks. listing them all under "network
        interfaces" is ... unhelpful. Insufficient.

        They should be instead listed in subcategories by network type, i.e.
                Ethernet (meaning 10Mb/s)
                Fast Ethernet
                Gigabit Ethernet
                10 Gigabit Ethernet
                802.11a
                802.11b
                802.11g
                802.11n
                FDDI
                Token-Ring?
                Fiber Channel
                Infiniband
                Myrinet

        Particularly for the Ethernet family, it's reasonable to
        presume that a card in a given category supports the previous
        categories. Further, it's important that we use consistent
        terms for each of these, so that what the users are looking
        for is easily found.

        It would also be good to have a similar list broken out by
        bus interface (e.g. Sbus, ISA, PCI, PCI-X, PCIe).

        If we're careful & consistent enough, we might even be able
        to generate these lists automatically from the manual pages.

>How-To-Repeat:
        Try to find 802.11 cards in
        http://www.netbsd.org/support/hardware/pci.html
        which is a pretty messy list. Wish for precisely what I am
        requesting in this problem report.

>Fix:
        

>Unformatted: