2005-01-06 01:43:34 +00:00
|
|
|
/*-
|
1999-08-31 14:43:30 +00:00
|
|
|
* Copyright (c) 1997, 1998, 1999
|
|
|
|
* Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
* 3. All advertising materials mentioning features or use of this software
|
|
|
|
* must display the following acknowledgement:
|
|
|
|
* This product includes software developed by Bill Paul.
|
|
|
|
* 4. Neither the name of the author nor the names of any co-contributors
|
|
|
|
* may be used to endorse or promote products derived from this software
|
|
|
|
* without specific prior written permission.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
|
|
|
|
* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
|
|
|
|
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
|
|
|
|
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
|
|
|
|
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
|
|
|
|
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
|
|
|
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
|
|
|
|
* THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
*/
|
|
|
|
|
2003-08-24 17:55:58 +00:00
|
|
|
#include <sys/cdefs.h>
|
|
|
|
__FBSDID("$FreeBSD$");
|
|
|
|
|
1999-08-31 14:43:30 +00:00
|
|
|
/*
|
|
|
|
* driver for RealTek 8139 internal PHYs
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <sys/param.h>
|
|
|
|
#include <sys/systm.h>
|
|
|
|
#include <sys/kernel.h>
|
2004-05-30 17:57:46 +00:00
|
|
|
#include <sys/module.h>
|
1999-08-31 14:43:30 +00:00
|
|
|
#include <sys/socket.h>
|
|
|
|
#include <sys/bus.h>
|
|
|
|
|
|
|
|
#include <net/if.h>
|
2002-04-07 20:55:50 +00:00
|
|
|
#include <net/if_arp.h>
|
1999-08-31 14:43:30 +00:00
|
|
|
#include <net/if_media.h>
|
|
|
|
|
|
|
|
#include <dev/mii/mii.h>
|
|
|
|
#include <dev/mii/miivar.h>
|
2003-01-19 02:59:34 +00:00
|
|
|
#include "miidevs.h"
|
2002-04-07 20:55:50 +00:00
|
|
|
|
|
|
|
#include <machine/bus.h>
|
|
|
|
#include <pci/if_rlreg.h>
|
1999-08-31 14:43:30 +00:00
|
|
|
|
|
|
|
#include "miibus_if.h"
|
|
|
|
|
2002-10-14 22:31:52 +00:00
|
|
|
static int rlphy_probe(device_t);
|
|
|
|
static int rlphy_attach(device_t);
|
1999-08-31 14:43:30 +00:00
|
|
|
|
|
|
|
static device_method_t rlphy_methods[] = {
|
|
|
|
/* device interface */
|
|
|
|
DEVMETHOD(device_probe, rlphy_probe),
|
|
|
|
DEVMETHOD(device_attach, rlphy_attach),
|
2002-04-29 13:07:38 +00:00
|
|
|
DEVMETHOD(device_detach, mii_phy_detach),
|
1999-08-31 14:43:30 +00:00
|
|
|
DEVMETHOD(device_shutdown, bus_generic_shutdown),
|
|
|
|
{ 0, 0 }
|
|
|
|
};
|
|
|
|
|
|
|
|
static devclass_t rlphy_devclass;
|
|
|
|
|
|
|
|
static driver_t rlphy_driver = {
|
|
|
|
"rlphy",
|
|
|
|
rlphy_methods,
|
|
|
|
sizeof(struct mii_softc)
|
|
|
|
};
|
|
|
|
|
|
|
|
DRIVER_MODULE(rlphy, miibus, rlphy_driver, rlphy_devclass, 0, 0);
|
|
|
|
|
2002-03-20 02:08:01 +00:00
|
|
|
static int rlphy_service(struct mii_softc *, struct mii_data *, int);
|
2002-04-07 20:55:50 +00:00
|
|
|
static void rlphy_status(struct mii_softc *);
|
1999-08-31 14:43:30 +00:00
|
|
|
|
2002-10-14 22:31:52 +00:00
|
|
|
static int
|
2005-09-30 19:39:27 +00:00
|
|
|
rlphy_probe(device_t dev)
|
1999-08-31 14:43:30 +00:00
|
|
|
{
|
|
|
|
struct mii_attach_args *ma;
|
|
|
|
device_t parent;
|
|
|
|
|
|
|
|
ma = device_get_ivars(dev);
|
|
|
|
parent = device_get_parent(device_get_parent(dev));
|
|
|
|
|
2002-04-07 20:55:50 +00:00
|
|
|
/* Test for RealTek 8201L PHY */
|
|
|
|
if (MII_OUI(ma->mii_id1, ma->mii_id2) == MII_OUI_REALTEK &&
|
|
|
|
MII_MODEL(ma->mii_id2) == MII_MODEL_REALTEK_RTL8201L) {
|
|
|
|
device_set_desc(dev, MII_STR_REALTEK_RTL8201L);
|
|
|
|
return(0);
|
|
|
|
}
|
|
|
|
|
1999-08-31 14:43:30 +00:00
|
|
|
/*
|
|
|
|
* RealTek PHY doesn't have vendor/device ID registers:
|
|
|
|
* the rl driver fakes up a return value of all zeros.
|
|
|
|
*/
|
|
|
|
if (MII_OUI(ma->mii_id1, ma->mii_id2) != 0 ||
|
|
|
|
MII_MODEL(ma->mii_id2) != 0)
|
|
|
|
return (ENXIO);
|
|
|
|
|
|
|
|
/*
|
Take the support for the 8139C+/8169/8169S/8110S chips out of the
rl(4) driver and put it in a new re(4) driver. The re(4) driver shares
the if_rlreg.h file with rl(4) but is a separate module. (Ultimately
I may change this. For now, it's convenient.)
rl(4) has been modified so that it will never attach to an 8139C+
chip, leaving it to re(4) instead. Only re(4) has the PCI IDs to
match the 8169/8169S/8110S gigE chips. if_re.c contains the same
basic code that was originally bolted onto if_rl.c, with the
following updates:
- Added support for jumbo frames. Currently, there seems to be
a limit of approximately 6200 bytes for jumbo frames on transmit.
(This was determined via experimentation.) The 8169S/8110S chips
apparently are limited to 7.5K frames on transmit. This may require
some more work, though the framework to handle jumbo frames on RX
is in place: the re_rxeof() routine will gather up frames than span
multiple 2K clusters into a single mbuf list.
- Fixed bug in re_txeof(): if we reap some of the TX buffers,
but there are still some pending, re-arm the timer before exiting
re_txeof() so that another timeout interrupt will be generated, just
in case re_start() doesn't do it for us.
- Handle the 'link state changed' interrupt
- Fix a detach bug. If re(4) is loaded as a module, and you do
tcpdump -i re0, then you do 'kldunload if_re,' the system will
panic after a few seconds. This happens because ether_ifdetach()
ends up calling the BPF detach code, which notices the interface
is in promiscuous mode and tries to switch promisc mode off while
detaching the BPF listner. This ultimately results in a call
to re_ioctl() (due to SIOCSIFFLAGS), which in turn calls re_init()
to handle the IFF_PROMISC flag change. Unfortunately, calling re_init()
here turns the chip back on and restarts the 1-second timeout loop
that drives re_tick(). By the time the timeout fires, if_re.ko
has been unloaded, which results in a call to invalid code and
blows up the system.
To fix this, I cleared the IFF_UP flag before calling ether_ifdetach(),
which stops the ioctl routine from trying to reset the chip.
- Modified comments in re_rxeof() relating to the difference in
RX descriptor status bit layout between the 8139C+ and the gigE
chips. The layout is different because the frame length field
was expanded from 12 bits to 13, and they got rid of one of the
status bits to make room.
- Add diagnostic code (re_diag()) to test for the case where a user
has installed a broken 32-bit 8169 PCI NIC in a 64-bit slot. Some
NICs have the REQ64# and ACK64# lines connected even though the
board is 32-bit only (in this case, they should be pulled high).
This fools the chip into doing 64-bit DMA transfers even though
there is no 64-bit data path. To detect this, re_diag() puts the
chip into digital loopback mode and sets the receiver to promiscuous
mode, then initiates a single 64-byte packet transmission. The
frame is echoed back to the host, and if the frame contents are
intact, we know DMA is working correctly, otherwise we complain
loudly on the console and abort the device attach. (At the moment,
I don't know of any way to work around the problem other than
physically modifying the board, so until/unless I can think of a
software workaround, this will have do to.)
- Created re(4) man page
- Modified rlphy.c to allow re(4) to attach as well as rl(4).
Note that this code works for the sample 8169/Marvell 88E1000 NIC
that I have, but probably won't work for the 8169S/8110S chips.
RealTek has sent me some sample NICs, but they haven't arrived yet.
I will probably need to add an rlgphy driver to handle the on-board
PHY in the 8169S/8110S (it needs special DSP initialization).
2003-09-08 02:11:25 +00:00
|
|
|
* Make sure the parent is an `rl' or an `re'.
|
1999-08-31 14:43:30 +00:00
|
|
|
*/
|
Take the support for the 8139C+/8169/8169S/8110S chips out of the
rl(4) driver and put it in a new re(4) driver. The re(4) driver shares
the if_rlreg.h file with rl(4) but is a separate module. (Ultimately
I may change this. For now, it's convenient.)
rl(4) has been modified so that it will never attach to an 8139C+
chip, leaving it to re(4) instead. Only re(4) has the PCI IDs to
match the 8169/8169S/8110S gigE chips. if_re.c contains the same
basic code that was originally bolted onto if_rl.c, with the
following updates:
- Added support for jumbo frames. Currently, there seems to be
a limit of approximately 6200 bytes for jumbo frames on transmit.
(This was determined via experimentation.) The 8169S/8110S chips
apparently are limited to 7.5K frames on transmit. This may require
some more work, though the framework to handle jumbo frames on RX
is in place: the re_rxeof() routine will gather up frames than span
multiple 2K clusters into a single mbuf list.
- Fixed bug in re_txeof(): if we reap some of the TX buffers,
but there are still some pending, re-arm the timer before exiting
re_txeof() so that another timeout interrupt will be generated, just
in case re_start() doesn't do it for us.
- Handle the 'link state changed' interrupt
- Fix a detach bug. If re(4) is loaded as a module, and you do
tcpdump -i re0, then you do 'kldunload if_re,' the system will
panic after a few seconds. This happens because ether_ifdetach()
ends up calling the BPF detach code, which notices the interface
is in promiscuous mode and tries to switch promisc mode off while
detaching the BPF listner. This ultimately results in a call
to re_ioctl() (due to SIOCSIFFLAGS), which in turn calls re_init()
to handle the IFF_PROMISC flag change. Unfortunately, calling re_init()
here turns the chip back on and restarts the 1-second timeout loop
that drives re_tick(). By the time the timeout fires, if_re.ko
has been unloaded, which results in a call to invalid code and
blows up the system.
To fix this, I cleared the IFF_UP flag before calling ether_ifdetach(),
which stops the ioctl routine from trying to reset the chip.
- Modified comments in re_rxeof() relating to the difference in
RX descriptor status bit layout between the 8139C+ and the gigE
chips. The layout is different because the frame length field
was expanded from 12 bits to 13, and they got rid of one of the
status bits to make room.
- Add diagnostic code (re_diag()) to test for the case where a user
has installed a broken 32-bit 8169 PCI NIC in a 64-bit slot. Some
NICs have the REQ64# and ACK64# lines connected even though the
board is 32-bit only (in this case, they should be pulled high).
This fools the chip into doing 64-bit DMA transfers even though
there is no 64-bit data path. To detect this, re_diag() puts the
chip into digital loopback mode and sets the receiver to promiscuous
mode, then initiates a single 64-byte packet transmission. The
frame is echoed back to the host, and if the frame contents are
intact, we know DMA is working correctly, otherwise we complain
loudly on the console and abort the device attach. (At the moment,
I don't know of any way to work around the problem other than
physically modifying the board, so until/unless I can think of a
software workaround, this will have do to.)
- Created re(4) man page
- Modified rlphy.c to allow re(4) to attach as well as rl(4).
Note that this code works for the sample 8169/Marvell 88E1000 NIC
that I have, but probably won't work for the 8169S/8110S chips.
RealTek has sent me some sample NICs, but they haven't arrived yet.
I will probably need to add an rlgphy driver to handle the on-board
PHY in the 8169S/8110S (it needs special DSP initialization).
2003-09-08 02:11:25 +00:00
|
|
|
if (strcmp(device_get_name(parent), "rl") != 0 &&
|
|
|
|
strcmp(device_get_name(parent), "re") != 0)
|
1999-08-31 14:43:30 +00:00
|
|
|
return (ENXIO);
|
|
|
|
|
|
|
|
device_set_desc(dev, "RealTek internal media interface");
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
2002-10-14 22:31:52 +00:00
|
|
|
static int
|
2005-09-30 19:39:27 +00:00
|
|
|
rlphy_attach(device_t dev)
|
1999-08-31 14:43:30 +00:00
|
|
|
{
|
|
|
|
struct mii_softc *sc;
|
|
|
|
struct mii_attach_args *ma;
|
|
|
|
struct mii_data *mii;
|
|
|
|
|
|
|
|
sc = device_get_softc(dev);
|
|
|
|
ma = device_get_ivars(dev);
|
|
|
|
sc->mii_dev = device_get_parent(dev);
|
|
|
|
mii = device_get_softc(sc->mii_dev);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* The RealTek PHY can never be isolated, so never allow non-zero
|
|
|
|
* instances!
|
|
|
|
*/
|
|
|
|
if (mii->mii_instance != 0) {
|
|
|
|
device_printf(dev, "ignoring this PHY, non-zero instance\n");
|
|
|
|
return(ENXIO);
|
|
|
|
}
|
|
|
|
|
1999-09-01 17:07:27 +00:00
|
|
|
LIST_INSERT_HEAD(&mii->mii_phys, sc, mii_list);
|
|
|
|
|
|
|
|
sc->mii_inst = mii->mii_instance;
|
|
|
|
sc->mii_phy = ma->mii_phyno;
|
|
|
|
sc->mii_service = rlphy_service;
|
|
|
|
sc->mii_pdata = mii;
|
1999-08-31 14:43:30 +00:00
|
|
|
mii->mii_instance++;
|
|
|
|
|
|
|
|
sc->mii_flags |= MIIF_NOISOLATE;
|
|
|
|
|
|
|
|
#define ADD(m, c) ifmedia_add(&mii->mii_media, (m), (c), NULL)
|
|
|
|
|
|
|
|
#if 0 /* See above. */
|
|
|
|
ADD(IFM_MAKEWORD(IFM_ETHER, IFM_NONE, 0, sc->mii_inst),
|
|
|
|
BMCR_ISO);
|
|
|
|
#endif
|
|
|
|
|
|
|
|
ADD(IFM_MAKEWORD(IFM_ETHER, IFM_100_TX, IFM_LOOP, sc->mii_inst),
|
|
|
|
BMCR_LOOP|BMCR_S100);
|
|
|
|
|
2002-02-27 02:11:34 +00:00
|
|
|
mii_phy_reset(sc);
|
1999-08-31 14:43:30 +00:00
|
|
|
|
|
|
|
sc->mii_capabilities =
|
|
|
|
PHY_READ(sc, MII_BMSR) & ma->mii_capmask;
|
|
|
|
device_printf(dev, " ");
|
2002-04-28 19:25:07 +00:00
|
|
|
mii_add_media(sc);
|
1999-08-31 14:43:30 +00:00
|
|
|
printf("\n");
|
|
|
|
#undef ADD
|
|
|
|
MIIBUS_MEDIAINIT(sc->mii_dev);
|
|
|
|
return(0);
|
|
|
|
}
|
|
|
|
|
2001-09-29 19:18:52 +00:00
|
|
|
static int
|
2005-09-30 19:39:27 +00:00
|
|
|
rlphy_service(struct mii_softc *sc, struct mii_data *mii, int cmd)
|
1999-08-31 14:43:30 +00:00
|
|
|
{
|
|
|
|
struct ifmedia_entry *ife = mii->mii_media.ifm_cur;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We can't isolate the RealTek PHY, so it has to be the only one!
|
|
|
|
*/
|
|
|
|
if (IFM_INST(ife->ifm_media) != sc->mii_inst)
|
|
|
|
panic("rlphy_service: can't isolate RealTek PHY");
|
|
|
|
|
|
|
|
switch (cmd) {
|
|
|
|
case MII_POLLSTAT:
|
|
|
|
break;
|
|
|
|
|
|
|
|
case MII_MEDIACHG:
|
|
|
|
/*
|
|
|
|
* If the interface is not up, don't do anything.
|
|
|
|
*/
|
|
|
|
if ((mii->mii_ifp->if_flags & IFF_UP) == 0)
|
|
|
|
break;
|
|
|
|
|
|
|
|
switch (IFM_SUBTYPE(ife->ifm_media)) {
|
|
|
|
case IFM_AUTO:
|
|
|
|
/*
|
|
|
|
* If we're already in auto mode, just return.
|
|
|
|
*/
|
|
|
|
if (PHY_READ(sc, MII_BMCR) & BMCR_AUTOEN)
|
|
|
|
return (0);
|
2002-05-04 11:00:30 +00:00
|
|
|
(void) mii_phy_auto(sc);
|
1999-08-31 14:43:30 +00:00
|
|
|
break;
|
|
|
|
case IFM_100_T4:
|
|
|
|
/*
|
|
|
|
* XXX Not supported as a manual setting right now.
|
|
|
|
*/
|
|
|
|
return (EINVAL);
|
|
|
|
default:
|
|
|
|
/*
|
|
|
|
* BMCR data is stored in the ifmedia entry.
|
|
|
|
*/
|
|
|
|
PHY_WRITE(sc, MII_ANAR,
|
|
|
|
mii_anar(ife->ifm_media));
|
|
|
|
PHY_WRITE(sc, MII_BMCR, ife->ifm_data);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
|
|
|
|
case MII_TICK:
|
|
|
|
/*
|
|
|
|
* Is the interface even up?
|
|
|
|
*/
|
|
|
|
if ((mii->mii_ifp->if_flags & IFF_UP) == 0)
|
|
|
|
return (0);
|
|
|
|
|
|
|
|
/*
|
2001-09-29 19:18:52 +00:00
|
|
|
* Only used for autonegotiation.
|
1999-08-31 14:43:30 +00:00
|
|
|
*/
|
2001-09-29 19:18:52 +00:00
|
|
|
if (IFM_SUBTYPE(ife->ifm_media) != IFM_AUTO)
|
|
|
|
break;
|
1999-08-31 14:43:30 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* The RealTek PHY's autonegotiation doesn't need to be
|
|
|
|
* kicked; it continues in the background.
|
|
|
|
*/
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Update the media status. */
|
2002-04-07 20:55:50 +00:00
|
|
|
rlphy_status(sc);
|
1999-08-31 14:43:30 +00:00
|
|
|
|
|
|
|
/* Callback if something changed. */
|
2001-09-29 19:18:52 +00:00
|
|
|
mii_phy_update(sc, cmd);
|
1999-08-31 14:43:30 +00:00
|
|
|
return (0);
|
|
|
|
}
|
2002-04-07 20:55:50 +00:00
|
|
|
|
2002-09-28 17:15:38 +00:00
|
|
|
static void
|
2005-09-30 19:39:27 +00:00
|
|
|
rlphy_status(struct mii_softc *phy)
|
2002-04-07 20:55:50 +00:00
|
|
|
{
|
|
|
|
struct mii_data *mii = phy->mii_pdata;
|
|
|
|
int bmsr, bmcr, anlpar;
|
|
|
|
device_t parent;
|
|
|
|
|
|
|
|
mii->mii_media_status = IFM_AVALID;
|
|
|
|
mii->mii_media_active = IFM_ETHER;
|
|
|
|
|
|
|
|
bmsr = PHY_READ(phy, MII_BMSR) | PHY_READ(phy, MII_BMSR);
|
|
|
|
if (bmsr & BMSR_LINK)
|
|
|
|
mii->mii_media_status |= IFM_ACTIVE;
|
|
|
|
|
|
|
|
bmcr = PHY_READ(phy, MII_BMCR);
|
|
|
|
if (bmcr & BMCR_ISO) {
|
|
|
|
mii->mii_media_active |= IFM_NONE;
|
|
|
|
mii->mii_media_status = 0;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (bmcr & BMCR_LOOP)
|
|
|
|
mii->mii_media_active |= IFM_LOOP;
|
|
|
|
|
|
|
|
if (bmcr & BMCR_AUTOEN) {
|
|
|
|
/*
|
|
|
|
* NWay autonegotiation takes the highest-order common
|
|
|
|
* bit of the ANAR and ANLPAR (i.e. best media advertised
|
|
|
|
* both by us and our link partner).
|
|
|
|
*/
|
|
|
|
if ((bmsr & BMSR_ACOMP) == 0) {
|
|
|
|
/* Erg, still trying, I guess... */
|
|
|
|
mii->mii_media_active |= IFM_NONE;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if ((anlpar = PHY_READ(phy, MII_ANAR) &
|
|
|
|
PHY_READ(phy, MII_ANLPAR))) {
|
|
|
|
if (anlpar & ANLPAR_T4)
|
|
|
|
mii->mii_media_active |= IFM_100_T4;
|
|
|
|
else if (anlpar & ANLPAR_TX_FD)
|
|
|
|
mii->mii_media_active |= IFM_100_TX|IFM_FDX;
|
|
|
|
else if (anlpar & ANLPAR_TX)
|
|
|
|
mii->mii_media_active |= IFM_100_TX;
|
|
|
|
else if (anlpar & ANLPAR_10_FD)
|
|
|
|
mii->mii_media_active |= IFM_10_T|IFM_FDX;
|
|
|
|
else if (anlpar & ANLPAR_10)
|
|
|
|
mii->mii_media_active |= IFM_10_T;
|
|
|
|
else
|
|
|
|
mii->mii_media_active |= IFM_NONE;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
/*
|
|
|
|
* If the other side doesn't support NWAY, then the
|
|
|
|
* best we can do is determine if we have a 10Mbps or
|
|
|
|
* 100Mbps link. There's no way to know if the link
|
|
|
|
* is full or half duplex, so we default to half duplex
|
|
|
|
* and hope that the user is clever enough to manually
|
|
|
|
* change the media settings if we're wrong.
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
* The RealTek PHY supports non-NWAY link speed
|
|
|
|
* detection, however it does not report the link
|
|
|
|
* detection results via the ANLPAR or BMSR registers.
|
|
|
|
* (What? RealTek doesn't do things the way everyone
|
|
|
|
* else does? I'm just shocked, shocked I tell you.)
|
|
|
|
* To determine the link speed, we have to do one
|
|
|
|
* of two things:
|
|
|
|
*
|
|
|
|
* - If this is a standalone RealTek RTL8201(L) PHY,
|
|
|
|
* we can determine the link speed by testing bit 0
|
|
|
|
* in the magic, vendor-specific register at offset
|
|
|
|
* 0x19.
|
|
|
|
*
|
|
|
|
* - If this is a RealTek MAC with integrated PHY, we
|
|
|
|
* can test the 'SPEED10' bit of the MAC's media status
|
|
|
|
* register.
|
|
|
|
*/
|
|
|
|
parent = device_get_parent(phy->mii_dev);
|
|
|
|
if (strcmp(device_get_name(parent), "rl") != 0) {
|
|
|
|
if (PHY_READ(phy, 0x0019) & 0x01)
|
|
|
|
mii->mii_media_active |= IFM_100_TX;
|
|
|
|
else
|
|
|
|
mii->mii_media_active |= IFM_10_T;
|
|
|
|
} else {
|
|
|
|
if (PHY_READ(phy, RL_MEDIASTAT) &
|
|
|
|
RL_MEDIASTAT_SPEED10)
|
|
|
|
mii->mii_media_active |= IFM_10_T;
|
|
|
|
else
|
|
|
|
mii->mii_media_active |= IFM_100_TX;
|
|
|
|
}
|
|
|
|
|
|
|
|
} else
|
|
|
|
mii->mii_media_active = mii_media_from_bmcr(bmcr);
|
|
|
|
}
|