| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
quad port hme(4)'s and other newer Sun systems with hme(4)'s.
derived from a diff posted to freebsd-sparc64 by
Marius Strobl <marius at alchemy dot franken dot de>
ok mickey@
|
|
|
|
|
|
tested & ok pvalchev@
|
|
for auto negotiation ticks code. No functional change.
ok brad@
|
|
Mainly remove space between locators parens, replace spaces with tabs
where appropriate and consistently align dependencies.
|
|
|
|
|
|
and on-board Netra T1 105's, etc.
|
|
carp directly.
ok brad@ mpf@
|
|
|
|
|
|
|
|
|
|
|
|
found attaching to some vr devices.
From NetBSD.
ok brad@
|
|
|
|
|
|
- use mii_phy_reset() instead of bmtphy_reset()
- use mii_phy_match()
- sync bmtphyreg.h to NetBSD
Tested on a few bce(4), gem(4), xl(4)
|
|
an adhoc basis in a couple of PHY drivers, this fixes it more generally.
From NetBSD
Fixes panics with aue(4) NICs.
|
|
|
|
|
|
|
|
From NetBSD
|
|
|
|
From NetBSD
|
|
|
|
some clean up. fixes issue with axe@usb.
Tested by a number of developers and users.
|
|
|
|
|
|
|
|
- reorder operations and a few return (0)'s to break's with MII_TICK switch case
|
|
callback is made.
From NetBSD
|
|
|
|
dealing with a carp interface.
|
|
|
|
from FreeBSD
|
|
From NetBSD
|
|
Do not call mii_pollstat() from within device tick routines; the status
information is updated by mii_tick().
dcphy.c rev 1.13
Work around an Intel 21143 chip bug.
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.
From FreeBSD
ok deraadt@
|
|
Add support for BCM5705K
rev 1.74
Add support for the BCM5750/5751. Unfortunately the documentation
I have from Broadcom does not give much information on these devices,
so the Broadcom Linux driver was used for clues to what these chips
support. It turns out they are similar to the 5705 with the 5751
being the PCI-Express version and needing special work-arounds and
settings.
From FreeBSD
|
|
|
|
|
|
|
|
|
|
|
|
|
|
already deals with.
|
