summaryrefslogtreecommitdiffstats
path: root/sys/i386/include/pc
diff options
context:
space:
mode:
authorwpaul <wpaul@FreeBSD.org>1999-08-27 18:58:27 +0000
committerwpaul <wpaul@FreeBSD.org>1999-08-27 18:58:27 +0000
commitfa6cd402be7d460f6b95f56163ae7a0605ac238a (patch)
tree159ea99f0e8c4ccfbaed73b8663969d0ba97027b /sys/i386/include/pc
parentea005100f82a3cf7703048fcbfcff58781b81f55 (diff)
downloadFreeBSD-src-fa6cd402be7d460f6b95f56163ae7a0605ac238a.zip
FreeBSD-src-fa6cd402be7d460f6b95f56163ae7a0605ac238a.tar.gz
Convert the ThunderLAN driver to miibus. This took me a while because I
had to get the ML 6692 PHY driver working correctly, which is harder than it sounds. "Bitrate" ThunderLAN devices should still be supported (i.e the older 10Mbps Netflex 3/P, which use the TNETE110 chip that has no MII support). The ThunderLAN has an internal PHY which makes things a little complicated, but these are the basic rules: - For devices with just the ThunderLAN, the internal PHY is used to provide 10baseT, and 10base5/10baseT support. Autonegotiation will work, but only with 10baseT links. The only thing that really gets negotiated is whether the link is full or half duplex. - For devices with the ThunderLAN and an external 10/100 PHY (like the Compaq Netelligent 100Mbps cards, or the internal Netflex 3/P with 100Mbps upgrade daughter card), the external PHY is used for 10baseT and 100baseTX modes. The internal PHY is still used to support 10base5/10base2, though you have to select them manual with ifconfig. - For devices with the ThunderLAN and the ML6692 PHY, both the internal and external PHYs are used, though it will appear as though the 6692 PHY will be used to support 10baseT and 100baseTX modes. In reality, the internal PHY will be used for 10baseT, but this fact will be hidden from the user. The 10base5/10base2 modes can also be selected manually as with above.
Diffstat (limited to 'sys/i386/include/pc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud