netdev - Re: [PATCH][net-next v2] gianfar: Add flow control support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20130813.152916.1256175758105854594.davem@davemloft.net>
Date:	Tue, 13 Aug 2013 15:29:16 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	claudiu.manoil@...escale.com
Cc:	netdev@...r.kernel.org, bhutchings@...arflare.com,
	ljaenicke@...ominate.com
Subject: Re: [PATCH][net-next v2] gianfar: Add flow control support

From: Claudiu Manoil <claudiu.manoil@...escale.com>
Date: Mon, 12 Aug 2013 13:53:26 +0300

> eTSEC has Rx and Tx flow control capabilities that may be enabled
> through MACCFG1[Rx_Flow, Tx_Flow] bits.  These bits must not be set
> however when eTSEC is operated in Half-Duplex mode.  Unfortunately,
> the driver currently sets these bits unconditionally.
> This patch adds the proper handling of the PAUSE frame capability
> register bits by implementing the ethtool -A interface.  When pause
> autoneg is enabled, the controller uses the phy's capability to
> negotiate PAUSE frame settings with the link partner and reconfigures
> its Rx_Flow and Tx_Flow settings to match the capabilities of the
> link partner.  If pause autoneg is off, the PAUSE frame generation
> may be forced manually (ethtool -A).  Flow control is disabled by
> default now.
> This implementation is inspired by the tg3 driver.
> 
> Signed-off-by: Lutz Jaenicke <ljaenicke@...ominate.com>
> Signed-off-by: Claudiu Manoil <claudiu.manoil@...escale.com>

Applied to net-next, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html