thorpej 94e489e277 If the autonegotiation is enabled, the PAR doesn't indicate duplex mode ... properly! Work around this by determing current active media by taking the highest-order common bit of our advertised capabilites and the link partner's. If the link partner doens't do autonegotiation, then parallel detection will pick up the media type, which will never be full-duplex, so reading the PAR is ok in this case. Bug pointed out by Matthias Drochner, work-around inspired by reading the dp83840 manual, section 3.9 (IEEE 802.3u auto-negotiation).		1998-08-12 22:41:21 +00:00
..
Makefile	Adapt to MII layer changes.	1998-08-11 00:03:12 +00:00
Makefile.miidevs	…
devlist2h.awk	…
exphy.c	Make a variable name reflect a register name.	1998-08-12 22:27:42 +00:00
files.mii	Driver for the 3Com internal PHY, found on 3c905B-TX cards (and maybe	1998-08-12 08:46:20 +00:00
inphy.c	If autonegotiation is enabled in the BMSR, and the BMCR doens't claim	1998-08-12 20:56:34 +00:00
inphyreg.h	Device driver for the Intel i82555 PHY.	1998-08-11 00:00:28 +00:00
mii.c	Adapt to attribute name change. Also, deal with 3Com PHYs that report	1998-08-11 00:41:44 +00:00
mii.h	…
miidevs	…
miidevs.h	Initial generation.	1998-08-10 23:56:19 +00:00
miivar.h	…
nsphy.c	If the autonegotiation is enabled, the PAR doesn't indicate duplex mode	1998-08-12 22:41:21 +00:00
nsphyreg.h	Adapt to the new MII layer. This PHY driver now properly supports	1998-08-10 23:58:39 +00:00
qsphy.c	If autonegotiation is enabled in the BMSR, and the BMCR doens't claim	1998-08-12 20:56:34 +00:00
qsphyreg.h	Device driver for the Quality Semiconductor QS6612 PHY, found in	1998-08-11 00:01:03 +00:00
tlphy.c	If autonegotiation is enabled in the BMSR, and the BMCR doens't claim	1998-08-12 20:56:34 +00:00
tlphyreg.h	Adapt to the new MII layer. This PHY driver now properly supports	1998-08-10 23:59:58 +00:00
tlphyvar.h	Adapt to the new MII layer. This PHY driver now properly supports	1998-08-10 23:59:58 +00:00