françois romieu eb2dc35d99 r8169: RxConfig hack for the 8168evl. ... The 8168evl (RTL_GIGA_MAC_VER_34) based Gigabyte GA-990FXA motherboards are very prone to NETDEV watchdog problems without this change. See https://bugzilla.kernel.org/show_bug.cgi?id=42899 for instance. I don't know why it *works*. It's depressingly effective though. For the record: - the problem may go along IOMMU (AMD-Vi) errors but it really looks like a red herring. - the patch sets the RX_MULTI_EN bit. If the 8168c doc is any guide, the chipset now fetches several Rx descriptors at a time. - long ago the driver ignored the RX_MULTI_EN bit. e542a2269f changed the RxConfig settings. Whatever the problem it's now labeled a regression. - Realtek's own driver can identify two different 8168evl devices (CFG_METHOD_16 and CFG_METHOD_17) where the r8169 driver only sees one. It sucks. Signed-off-by: Francois Romieu <romieu@fr.zoreil.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2012-06-22 21:48:32 -07:00
..
8139cp.c	8139cp/8139too: terminate the eeprom access with the right opmode	2012-06-01 14:22:11 -04:00
8139too.c	8139cp/8139too: terminate the eeprom access with the right opmode	2012-06-01 14:22:11 -04:00
atp.c	Remove all #inclusions of asm/system.h	2012-03-28 18:30:03 +01:00
atp.h
Kconfig	drivers/net: fix up stale paths from driver reorg	2012-01-30 12:54:40 -05:00
Makefile	net/ethernet: sc92031 is not Realtek	2011-11-01 19:30:38 -04:00
r8169.c	r8169: RxConfig hack for the 8168evl.	2012-06-22 21:48:32 -07:00