summaryrefslogtreecommitdiffstats
path: root/sys/dev/mii/nsphy.c
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Clean up mii/phy drivers: Remove the MIIF_DOINGAUTO which doesn't reallyphk2002-05-041-1/+1
| | | | | do anything at the end of the day except bloat the drivers which has copy&pasted it.
* 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-40/+6
| | | | | | | . 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.
* Only touch the PCR register in order to set bits for the fxp driver.jlemon2001-06-021-1/+3
| | | | | | | The 3C509-TX card apparently had a slightly different version of the chip, and has problems when this register is set. The problem does not appear on the 3C509{BC} cards, but since only the fxp driver needs specific bits set, conditionalize on that.
* Enable some undocumented bits in the DP83840 PHY, which is neededjlemon2001-03-161-5/+8
| | | | | | | when using it with the Intel fxp driver. Tested by: peter, Ollivier Robert <roberto@eurocontrol.fr>, Peter Schultz <pete@jocose.org>
* Add QS6612, AC101 and LXT970 personal drivers and register definitions.semenu2001-02-071-6/+0
| | | | Obtained from: NetBSD/OpenBSD
* 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*
* Added Altima Communications OUI and their AC101 10/100semenu2000-06-211-0/+3
| | | | | | media interface to the list of known chips. miidevs.h regenerated also.
* Remove ~25 unneeded #include <sys/conf.h>phk2000-04-191-1/+0
| | | | Remove ~60 unneeded #include <sys/malloc.h>
* Added code to handle QS6612 PHY as standard NS PHYsemenu2000-04-111-5/+8
| | | | for support of tx driver.
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* This commit adds support for the NetBSD MII abstraction layer andwpaul1999-08-211-0/+430
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