mirror of
https://git.FreeBSD.org/src.git
synced 2024-12-23 11:18:54 +00:00
d00275330d
MII-compliant PHY drivers. Many 10/100 ethernet NICs available today either use an MII transceiver or have built-in transceivers that can be programmed using an MII interface. It makes sense then to separate this support out into common code instead of duplicating it in all of the NIC drivers. The mii code also handles all of the media detection, selection and reporting via the ifmedia interface. This is basically the same code from NetBSD's /sys/dev/mii, except it's been adapted to FreeBSD's bus architecture. The advantage to this is that it automatically allows everything to be turned into a loadable module. There are some common functions for use in drivers once an miibus has been attached (mii_mediachg(), mii_pollstat(), mii_tick()) as well as individual PHY drivers. There is also a generic driver for all PHYs that aren't handled by a specific driver. It's possible to do this because all 10/100 PHYs implement the same general register set in addition to their vendor-specific register sets, so for the most part you can use one driver for pretty much any PHY. There are a couple of oddball exceptions though, hence the need to have specific drivers. There are two layers: the generic "miibus" layer and the PHY driver layer. The drivers are child devices of "miibus" and the "miibus" is a child of a given NIC driver. The "miibus" code and the PHY drivers can actually be compiled and kldoaded as completely separate modules or compiled together into one module. For the moment I'm using the latter approach since the code is relatively small. Currently there are only three PHY drivers here: the generic driver, the built-in 3Com XL driver and the NS DP83840 driver. I'll be adding others later as I convert various NIC drivers to use this code. I realize that I'm cvs adding this stuff instead of importing it onto a separate vendor branch, but in my opinion the import approach doesn't really offer any significant advantage: I'm going to be maintaining this stuff and writing my own PHY drivers one way or the other.
119 lines
4.5 KiB
Plaintext
119 lines
4.5 KiB
Plaintext
$Id$
|
|
/*$NetBSD: miidevs,v 1.6 1999/05/14 11:37:30 drochner Exp $*/
|
|
|
|
/*-
|
|
* Copyright (c) 1998, 1999 The NetBSD Foundation, Inc.
|
|
* All rights reserved.
|
|
*
|
|
* This code is derived from software contributed to The NetBSD Foundation
|
|
* by Jason R. Thorpe of the Numerical Aerospace Simulation Facility,
|
|
* NASA Ames Research Center.
|
|
*
|
|
* Redistribution and use in source and binary forms, with or without
|
|
* modification, are permitted provided that the following conditions
|
|
* are met:
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
* notice, this list of conditions and the following disclaimer.
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
* documentation and/or other materials provided with the distribution.
|
|
* 3. All advertising materials mentioning features or use of this software
|
|
* must display the following acknowledgement:
|
|
* This product includes software developed by the NetBSD
|
|
* Foundation, Inc. and its contributors.
|
|
* 4. Neither the name of The NetBSD Foundation nor the names of its
|
|
* contributors may be used to endorse or promote products derived
|
|
* from this software without specific prior written permission.
|
|
*
|
|
* THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
|
|
* ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
|
|
* TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
|
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
|
|
* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
|
|
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
|
|
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
|
|
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
|
|
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
|
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
|
* POSSIBILITY OF SUCH DAMAGE.
|
|
*/
|
|
|
|
/*
|
|
* List of known MII OUIs.
|
|
* For a complete list see http://standards.ieee.org/regauth/oui/
|
|
*
|
|
* XXX Vendors do obviously not agree how OUIs (18 bit) are mapped
|
|
* to the 16 bits available in the id registers. The MII_OUI() macro
|
|
* in "mii.h" reflects the most obvious way. If a vendor uses a
|
|
* different mapping, an "xx" prefixed OUI is defined here which is
|
|
* mangled accordingly to compensate.
|
|
*/
|
|
|
|
oui AMD 0x00001a Advanced Micro Devices
|
|
oui DAVICOM 0x00606e Davicom Semiconductor
|
|
oui ICS 0x00a0be Integrated Circuit Systems
|
|
oui INTEL 0x00aa00 Intel
|
|
oui LEVEL1 0x00207b Level 1
|
|
oui NATSEMI 0x080017 National Semiconductor
|
|
oui QUALSEMI 0x006051 Quality Semiconductor
|
|
oui SEEQ 0x00a07d Seeq
|
|
oui SIS 0x00e006 Silicon Integrated Systems
|
|
oui TI 0x080028 Texas Instruments
|
|
|
|
|
|
/* in the 79c873, AMD uses another OUI (which matches Davicom!) */
|
|
oui xxAMD 0x00606e Advanced Micro Devices
|
|
|
|
/* some vendors have the bits swapped within bytes
|
|
(ie, ordered as on the wire) */
|
|
oui xxICS 0x00057d Integrated Circuit Systems
|
|
oui xxSEEQ 0x0005be Seeq
|
|
oui xxSIS 0x000760 Silicon Integrated Systems
|
|
oui xxTI 0x100014 Texas Instruments
|
|
|
|
/* Level 1 is completely different - from right to left.
|
|
(Two bits get lost in the third OUI byte.) */
|
|
oui xxLEVEL1 0x1e0400 Level 1
|
|
|
|
/* Don't know what's going on here. */
|
|
oui xxDAVICOM 0x006040 Davicom Semiconductor
|
|
|
|
|
|
/*
|
|
* List of known models. Grouped by oui.
|
|
*/
|
|
|
|
/* Advanced Micro Devices PHYs */
|
|
model xxAMD 79C873 0x0000 Am79C873 10/100 media interface
|
|
model AMD 79c973phy 0x0036 Am79c973 internal PHY
|
|
|
|
/* Davicom Semiconductor PHYs */
|
|
model xxDAVICOM DM9101 0x0000 DM9101 10/100 media interface
|
|
|
|
/* Integrated Circuit Systems PHYs */
|
|
model xxICS 1890 0x0002 ICS1890 10/100 media interface
|
|
|
|
/* Intel PHYs */
|
|
model INTEL I82555 0x0015 i82555 10/100 media interface
|
|
|
|
/* Level 1 PHYs */
|
|
model xxLEVEL1 LXT970 0x0000 LXT970 10/100 media interface
|
|
|
|
/* National Semiconductor PHYs */
|
|
model NATSEMI DP83840 0x0000 DP83840 10/100 media interface
|
|
model NATSEMI DP83843 0x0001 DP83843 10/100 media interface
|
|
|
|
/* Quality Semiconductor PHYs */
|
|
model QUALSEMI QS6612 0x0000 QS6612 10/100 media interface
|
|
|
|
/* Seeq PHYs */
|
|
model xxSEEQ 80220 0x0003 Seeq 80220 10/100 media interface
|
|
model xxSEEQ 84220 0x0004 Seeq 84220 10/100 media interface
|
|
|
|
/* Silicon Integrated Systems PHYs */
|
|
model xxSIS 900 0x0000 SiS 900 10/100 media interface
|
|
|
|
/* Texas Instruments PHYs */
|
|
model xxTI TLAN10T 0x0001 ThunderLAN 10baseT media interface
|
|
model xxTI 100VGPMI 0x0002 ThunderLAN 100VG-AnyLan media interface
|