summaryrefslogtreecommitdiffstats
path: root/sys/dev/mii/exphy.c
Commit message (Collapse)AuthorAgeFilesLines
* - Take advantage of mii_phy_dev_probe().marius2007-01-121-39/+19
| | | | | | | | | | - In exphy_service() for the MII_TICK case don't bother to check whether the currently selected media is of type IFM_AUTO as auto-negotiation doesn't need to be kicked anyway. - Remove #if 0'ed unapplicable code. - Fix some whitespace nits. MFC after: 1 week
* Use mii_phy_add_media()/mii_phy_setmedia()-compatible media tablemarius2007-01-121-1/+1
| | | | | | indices when manually adding media. Some of these I've missed while converting drivers to take advantage of said fuctions recently, others where longstanding bugs.
* Replace hard-coded magic constants to system defined constantsyongari2006-07-031-1/+1
| | | | | | | (BUS_PROBE_DEFAULT, BUS_PROBE_GENERIC etc). There is no functional changes. Reviewed by: oleg, scottl
* Use ansi function definitions in preference to K&R to reduce diffsimp2005-09-301-8/+3
| | | | with NetBSD (and cause it looks cooler).
* Start each of the license/copyright comments with /*-, minor shuffle of linesimp2005-01-061-1/+1
|
* Remove double __FBSDID and move the remaining one into a common place aftermarius2004-05-291-6/+3
| | | | | the license(s) and before the driver comment (the latter only in drivers not having __FBSDID at that location).
* Use __FBSDID().obrien2003-08-241-0/+3
| | | | Also some minor style cleanups.
* Use __FBSDID rather than rcsid[].obrien2003-04-031-5/+3
|
* Remove miidevs.h and generate it from miidevs at compile time.obrien2003-01-191-1/+1
| | | | The devlist2h.awk tool to do this has been repocopied to sys/tools/.
* Put function return types on a line by themselves.alfred2002-10-141-4/+6
| | | | | Cleanup my earlier de-__P sweep and remove whitespace between function names and paramters.
* Use 3C905C instead of 3c905Cphy as the identifier for the Broadcom PHY usedbenno2002-07-051-2/+2
| | | | | | in the 3C905C. This is mainly cosmetic. I'm doing this mainly so we share the same identifier as NetBSD.
* Convert exphy and ukphy over to the new code.phk2002-04-291-25/+3
| | | | exphy is done flying blind, ukphy is tested on one card.
* Make one generic mii_phy_detach() to replace 19 slightly different ones.phk2002-04-291-17/+1
| | | | | | | Rename mii_phy_auto_stop() mii_phy_down(). Introduce mii_down(), use it from nge. Do not indirect it to 19 identical case's in 19 switchstatements like NetBSD did.
* Don't pass three args when one will do just fine, and even preventphk2002-04-281-1/+1
| | | | mistakes like the one brgphy.c (now corrected).
* Improve an API by about 4 lines per driver.phk2002-04-281-5/+1
|
* Remove __P.alfred2002-03-201-5/+5
|
* Cleanup pass for mii drivers.jlemon2001-09-291-13/+10
| | | | | | | . Make internal service routines static. . Use a consistent ordering of checks in MII_TICK. Do the work in the mii_phy_tick() subroutine if appropriate. . Call mii_phy_update() to trigger the callbacks.
* Grrrrr. That last commit was supposed to be to the head, not to -stablewpaul2000-12-121-0/+1
| | | | | | (even though I want the fixes in -stable anyway). I'm sure I'm going to get flamed now for committing to -stable and -current too quickly. *sigh*
* Remove ~25 unneeded #include <sys/conf.h>phk2000-04-191-1/+0
| | | | Remove ~60 unneeded #include <sys/malloc.h>
* Re-arrange things in the attach routines of the 3Com and RealTek PHYwpaul1999-09-011-7/+7
| | | | | | | drivers so that we don't clobber things or leave them uninitialized if we abort due a failure. Submitted by: Luoqi Chen
* The ASIC on the 3c905C appears to be manufactured by Broadcom (previouswpaul1999-08-291-4/+9
| | | | | | | | | ones were made by Lucent). The Broadcom chip also appears to use an internal PHY made by Broadcom which uses the Broadcom OUI. This is different from previous ASICs which always returned 0 in the PHY ID registers. To account for this, I added the necessary ID values for the Broadcom PHY so that it can be detected and attached using the 3Com PHY driver instead of defaulting to the generic one.
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* This commit adds support for the NetBSD MII abstraction layer andwpaul1999-08-211-0/+311
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.
OpenPOWER on IntegriCloud