r8169: hardware flow control

The datasheet suggests that the device handles the hardware flow
control almost automagically. User report a different story, so
let's try to twiddle the mii registers.

Signed-off-by: Francois Romieu <romieu@fr.zoreil.com>

diff --git a/drivers/net/r8169.c b/drivers/net/r8169.c
index ea4f9f7bd071d84ce866248b0a612d1c8d378bbc..3424b3c1083cc2d1280894447fe7755f0b0d9209 100644 (file)
--- a/drivers/net/r8169.c
+++ b/drivers/net/r8169.c
@@ -771,6 +771,8 @@ static int rtl8169_set_speed_xmii(struct net_device *dev,
                        auto_nego &= ~(PHY_Cap_10_Half | PHY_Cap_100_Half);
        }
 
+       auto_nego |= ADVERTISE_PAUSE_CAP | ADVERTISE_PAUSE_ASYM;
+
        tp->phy_auto_nego_reg = auto_nego;
        tp->phy_1000_ctrl_reg = giga_ctrl;
 
@@ -962,6 +964,11 @@ static void rtl8169_gset_xmii(struct net_device *dev, struct ethtool_cmd *cmd)
        else if (status & _10bps)
                cmd->speed = SPEED_10;
 
+       if (status & TxFlowCtrl)
+               cmd->advertising |= ADVERTISED_Asym_Pause;
+       if (status & RxFlowCtrl)
+               cmd->advertising |= ADVERTISED_Pause;
+
        cmd->duplex = ((status & _1000bpsF) || (status & FullDup)) ?
                      DUPLEX_FULL : DUPLEX_HALF;
 }