summaryrefslogtreecommitdiffstats
path: root/sys/dev/sound/pcm/mixer.c
diff options
context:
space:
mode:
authorwpaul <wpaul@FreeBSD.org>1999-09-01 03:16:21 +0000
committerwpaul <wpaul@FreeBSD.org>1999-09-01 03:16:21 +0000
commit40676b1f20541a3bc3b49840b0eff5ec547720dd (patch)
tree66e37bfc71ade50ef3b1c0821c65a57946d86795 /sys/dev/sound/pcm/mixer.c
parentfd1aaa60e2636e976b5045cb5bc374a15df1a1d4 (diff)
downloadFreeBSD-src-40676b1f20541a3bc3b49840b0eff5ec547720dd.zip
FreeBSD-src-40676b1f20541a3bc3b49840b0eff5ec547720dd.tar.gz
Just when I thought it was safe. In the original 3c905-TX NICs, the
external NatSemi PHY chip was programmed to respond to MII address 24. In the 3c905B ASICs, the transceiver is internal but it's still mapped to MII address 24. But *some* 3Com 3c905B ASIC revisions map the transceiver control registers to *all* MII addresses (0 through 31). The miibus code probes for PHYs at all MII addresses and because of this unusual behavior, it will attempt to map the same PHY registers several times over, which doesn't work. Naturally, the 3c905B NIC that I tested happened not to exhibit this behavior. The fix is to tweak xl_miibus_readreg() and xl_miibus_writereg() to only respond when attempting to read from MII address 24. This is safe to do since the 3Com documentation indicates that the PHY and/or internal transceiver will always be mapped to address 24, and there are no 3Com XL NICs with more than one PHY.
Diffstat (limited to 'sys/dev/sound/pcm/mixer.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud