| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
it seems to be possible to collide with FRAMELEN from machine/frame.h.
Found by: zec
|
|
|
|
| |
establishment of 10/100Mbps link on Atheros AR8121(L1E).
|
|
|
|
|
|
|
| |
not recognized by ciphy(4) due to the incorrect OUI.
Reported by: nork
Tested by: nork
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bank instead of copper/fiber bank which in turn resulted in
wrong registers were accessed during PHY operation. It is
believed that page 0 should be used for copper PHY so reinitialize
E1000_EADR to select default copper PHY.
This fixes link establishment issue of nfe(4) on Sun Fire X4140.
OpenBSD also has similimar patch but they just reset the E1000_EADR
register to page 0. However some Marvell PHYs((88E3082, 88E1000)
don't have the extended address register and the meaning of the
register is quite different for each PHY model. So selecting copper
PHY is limited to 88E1149 PHY which seems to be the only one that
exhibits link establishment problem. If parent device know the type
of PHY(either copper or fiber) that information should be notified
to PHY driver but there is no good way to pass this information yet.
Reported by: thompsa
Reviewed by: thompsa
|
|
|
|
|
|
|
|
|
| |
Asus EeePC and some Asus mainboards.
Reviewed by: yongari, rpaulo, jhb
Tested by: many
Approved by: kib (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
only mode and restore original value of extended address register
instead of overwriting it with page 1. There are still instance
information passing issue(e.g configured media type: fiber or
copper) from driver to PHY layer but this change make the selected
PHY work with 88E1112 PHY.
Reported by: Krzysztof Jedruczyk < beaker <at> hot dot pl >
Tested by: Krzysztof Jedruczyk < beaker <at> hot dot pl >
|
|
|
|
| |
HW donated by: nork
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Obtained from: Semihalf
|
|
|
|
|
| |
sure we get the error handling right in both places. This also
simplifies the code somewhat.
|
|
|
|
|
|
|
| |
When there's an error, we don't want to free the children, since it
will be stack garbage. While we did fail to dereference it by setting
devs to 0, we didn't fail to call free. We never failed to fail, it
was the easiest thing to do.
|
| |
|
|
|
|
| |
to do here is nothing in that case...
|
|
|
|
|
|
|
|
|
|
|
| |
Also report current link state while auto-negotiation is in
progress.
With this change link loss should be reported within a second
and drivers that rely on link state should work.
Reported by: Pete French < petefrench at ticketswitch dot com >
Tested by: Pete French < petefrench at ticketswitch dot com >
MFC after: 1 week
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Disable advanced link-down power saving in phy reset.
Reported by: nork
Tested by: nork
|
|
|
|
|
|
|
|
| |
Ethernet device driver, written by sephe@
Obtained from: DragonFly
Sponsored by: iXsystems
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
Ethernet device driver, written by sephe@
Obtained from: DragonFly
Sponsored by: iXsystems
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
| |
found on various Apple G3 models.
Submitted by: Nathan Whitehorn
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sn(4) driver and also looking at newer drivers. The reason for the rewrite is
to support MII and to try and resolve some performance issues found when trying
to use the sn(4) driver on the Gumstix network boards.
For reference, the SMSC LAN91C111 is a non-PCI ethernet part whose lineage
dates back to Ye Olde Days of ISA. It seems to get some use in the embedded
space these days on parts lacking on-board MACs or on-board PCI controllers,
such as the XScale PXA line of ARM CPUs.
This also includes a driver for the SMSC LAN83C183 10/100 PHY.
Man page to follow.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
10/100 operation and place the mailbox registers at a different offset.
They also do not have an EEPROM, so the MAC address must be read from
NVRAM instead.
MFC after: 1 month
PR: kern/118975
Submitted by: benjsc, Thomas Nyström thn at saeab dot se
Submitted by: sephe (original patch for DragonflyBSD)
|
|
|
|
|
|
| |
development systems).
Obtained from: Freescale, Semihalf
|
|
|
|
| |
Tested by: Stuart Fraser < stuart AT stuartfraser DOT net >
|
|
|
|
|
|
|
| |
the specific ASIC revision.
MFC after: 1 week
Obtained from: OpenBSD (mii/phy bits)
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
PR: kern/76710
|
|
|
|
|
|
|
|
| |
This PHY is found on many embedded development boards: among others MPC8555CDS
evaluation systems use it.
Approved by: cognet (mentor)
MFp4: e500
|
|
|
|
|
|
|
|
|
| |
- Fix whitespace according to style(9).
- Sync the comment describing why we have to wait in nsphy_reset()
with nsphyter_reset(). It's true that the manual tells to not do a
reset within 500us of applying power but that's unlikely the cause
of problems seen here. Generally having to wait 500us after a reset
however is.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
DP83847 PHYs. The main reason for using a specific driver for these
PHYs are reset quirks similar to the nsphy(4) driven DP83840A.
PR: 112654
Obtained from: NetBSD
MFC after: 2 weeks
Thanks to: mlaier for testing w/ DP83815
|
|
|
|
| |
The idea was taken from OpenBSD and cross-referenced with Linux driver.
|
|
|
|
|
| |
Make mii_ticks advance, autonegiation is retried every
mii_anegticks seconds.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
priorities of the technologies supported by 802.3 Selector Field
value.
1000BASE-T full duplex
1000BASE-T
100BASE-T2 full duplex
100BASE-TX full duplex
100BASE-T2
100BASE-T4
100BASE-TX
10BASE-T full duplex
10BAST-T
However PHY drivers didn't honor the order such that 100BASE-T4 had
higher priority than 100BASE-TX full duplex. Fix that long standing
bugs such that have PHY drivers choose the highest common denominator
ability.
Fix a bug in dcphy which inadvertently aceepts 100BASE-T4.
PR: 92599
|
|
|
|
|
|
| |
is redundant. mii_phy_add_media() already takes care of that.
Pointed out by: marius
|
|
|
|
|
|
|
|
|
|
| |
set this flag and it was more or less just copied and pasted from
another FreeBSD driver while porting this driver from NetBSD, whose
gentbi(4) doesn't set MIIF_NOISOLATE either.
- Fix spelling in a comment.
OK'ed by: yongari
MFC after: 3 months
|
|
|
|
|
|
|
| |
power-down mode.
PR: kern/114086
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
made by Michael Eisele and the patch was slightly modified by me.
With this change several NVIDIA ethernet controllers(e.g. MCP61)
works.
RTL8211B(L) is RealTek's new gigabit PHY. The PHY has several
features including crossover correction, polarity correction as
well as supporting triple speed(10/100/1000bps). Data transfer
between MAC and PHY is via RGMII for 1000baseT, MII for
10baseT/100baseTX.
Unfortunately, RealTek used the same model number for RTL8211B(L)
PHY so there is no way to discriminate between RTL8211B(L) and its
predecessors. ATM RTL8211B uses revision number 2 so checking the
revision number seems to be only way to identify it.
Obtained from: Michael Eisele [1]
Tested by: clemens fischer < ino-qc AT spotteswoode DOT de DOT eu DOT org >
|
|
|
|
|
|
|
|
|
|
|
| |
mii_anegticks to MII_ANEGTICKS_GIGE and use it. Previously it used
to MII_ANEGTICKS which may not be enough to wait before retrying
autonegotiation process at 1000bps.
o Reset autonegotation timer if media option is not IFM_AUTO or we
got a valid link.
o Announce link loss right after it happends.
o Autonegiation is retried every mii_anegticks seconds.
o Report link state changes right after setting autonegotiation.
|
|
|
|
|
|
|
| |
NetBSD. ATM the only consumer of the PHY is XBox with nfe(4) driver.
Submitted by: Ed Schouten <ed@fxq.nl>
Tested by: Ed Schouten <ed@fxq.nl>
|
|
|
|
| |
Submitted by: Ed Schouten <ed@fxq.nl>
|
|
|
|
|
| |
Submitted by: tor.egge@cvsup.no.freebsd.org
MFC after: 4 weeks
|