| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
The devlist2h.awk tool to do this has been repocopied to sys/tools/.
|
| |
|
|
|
|
|
|
|
| |
and 3com MAC. Specifications for the Altima PHY are available at:
http://www.altimacom.com/products/ac101L.html
Submitted by: Mikko S. Hyvarinen <morphy@morphy.iki.fi>
|
|
|
|
|
| |
Submitted by: marius@alchemy.franken.de
MFC after: 1 week
|
|
|
|
|
| |
Cleanup my earlier de-__P sweep and remove whitespace between function
names and paramters.
|
|
|
|
|
|
| |
static in its prototype, mark it static at the definition too.
Inspired by: FlexeLint warning #512
|
|
|
|
|
|
|
|
| |
cards to test; however the submitter reports that this patch works
with the on-board interface on the IBM x235 server.
Submitted by: Jung-uk Kim <jkim@niksun.com>
MFC after: 1 month
|
|
|
|
|
|
|
|
|
| |
when this is needed. Work around bogus second PHY in the DFE-580 card
via a change in the if_ste.c driver.
Suggested by: jdp
Reviewed by: jdp
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
The D-Link DFE-580 card will otherwise show 2 miibuses for each controller
and therefore 2 ukphy's.
Sponsored by: Vernier Networks
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
internal PHY on the 3COM 3C905B and 3C905C parts, however I've rigged it so
that xlphy (aka exphy) takes precedence for the time being.
If people try this with their xl cards and decide that it's a better choice,
we can switch this later.
This is the PHY used in various iMacs and possibly other GMAC-equipped
Macintoshes with 10/100 PHYs (the ones with 10/100/1000 appear to use brgphy).
Obtained from: NetBSD
|
|
|
|
|
|
| |
in the 3C905C. This is mainly cosmetic.
I'm doing this mainly so we share the same identifier as NetBSD.
|
|
|
|
|
| |
10 seconds is not enough to negotiate a gigE link with a cisco switch which
holds carrier off for several seconds between tries.
|
|
|
|
|
| |
do anything at the end of the day except bloat the drivers which has
copy&pasted it.
|
|
|
|
|
|
|
|
|
|
|
|
| |
well as is, so - just fetch current status upon MII_TICK.
Also do IFM_INST verification at the top of *_service() then doing it
separately for every case in switch.
acphy: do not read MII_ACPHY_DIAG twice, there is nothing latching.
qsphy: always fetch actual link status from MII_QSPHY_PCTL.
MFC after: 1 week
|
|
|
|
| |
get a description printed.
|
|
|
|
| |
exphy is done flying blind, ukphy is tested on one card.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Move fxp and nge drivers over to use the new stuff.
|
|
|
|
| |
function.
|
| |
|
| |
|
| |
|
|
|
|
| |
mistakes like the one brgphy.c (now corrected).
|
| |
|
|
|
|
|
|
| |
are IEEE defined.
Object file comes out the same.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rev 1.56 of if_dc.c removed calls to mii_pollstat() from the dc_tick()
routine. dc_tick() is called regularly to detect link up and link down
status, especially when autonegotiating.
The expectation was that mii_tick() (which is still called from dc_tick())
would update status information automatically in all cases where it would
be sensible to do so.
Unfortunately, with authentic 21143 chips this is not the case, and
the driver never successfully autonegotiates. This is because (despite
what it says in the 21143 manual) the chip always claims that link is not
present while the autonegotiation enable bit is set. Autonegotation takes
place and succeeds, but the driver tests the link bits before it switches
off the autonegotiation enable bit, and success is not recognised.
The simplest solution is to call dcphy_status() more often for MII_TICK
calls by dropping out of the switch statement instead of exiting when
we are autonegotiating and link appears to not be present. When
autonegotiation succeeds, dcphy_status() will note the speed and fdx/hdx
state and turn off the autonegotiation enable bit. The next call to
dcphy_status() will notice that link is present, and the dc driver code
will be notified.
Macronix chips also use this code, but implement link detection as
described in the manual, and hence don't need this patch. However, tests
on a Macronix 98715AEC-C show that it does not adversely affect them.
This could be done better but is the minimal effective change, and most
closely mimics what was happening prior to rev 1.56 of if_dc.c. (Actually
I also deleted a small amount of unnecessary code while I was in the area.)
Reviewed by: wpaul
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
doesn't support NWAY, the RealTek PHY (both the integrated ones on 8139
chips and the RTL8201L 10/100 PHY) will not report the link speed via
the ANLPAR or BMSR registers. For the 8201L, we need to look in magic
vendor-specific PHY register 0x19. For the 8139 MAC+PHY combo, we have
to be able to test the RL_MEDIASTAT register.
The changes to rlphy.c are based largely on the patch from PR 30836,
however I tried to eliminate some magic numbers by creating an entry
for the 8201 PHY in miidevs.
Also updated if_rl.c to allow the rlphy driver to read the RL_MEDIASTAT
register via the rl_miibus_readreg() routine.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
actually works.
Submitted by: Dennis <TD790@aol.com>
Reviewed by: Bill Paul <wpaul@freebsd.org>
MFC after: 7 days
|
|
|
|
| |
Submitted by: Darren Croke <djc@packetdesign.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
with an ifnet structure (so device_get_softc will get one).
If memory allocation fails in mii_phy_probe, don't just march ahead into
a panic- return ENOMEM.
MFC after: 1 week
|
|
|
|
|
|
|
| |
. 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.
|
|
|
|
| |
match the other mii drivers.
|
| |
|
| |
|
| |
|
|
|
|
| |
and BCM5401 PHYs.
|
|
|
|
| |
method uses in the nsgphy driver.
|
| |
|
|
|
|
|
| |
This basically updates the brgphy driver to support 10/100 modes in
addition to 1000Mbps modes.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
| |
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.
|