linux-kernel - [PATCH] r8169 fix regression on ASUS motherboards (updated)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <47323B6B.9000909@rtr.ca>
Date:	Wed, 07 Nov 2007 17:25:47 -0500
From:	Mark Lord <lkml@....ca>
To:	Francois Romieu <romieu@...zoreil.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jeff Garzik <jgarzik@...ox.com>,
	Linus Torvalds <torvalds@...l.org>
Subject: [PATCH] r8169 fix regression on ASUS motherboards (updated)

Mark Lord wrote:
> Francois Romieu wrote:
>..
>> I am not convinced, the broken ones include some RTL_GIGA_MAC_VER_12
>> too, namely XID = 0x38000000.
..

Here is the updated patch for both VER_11 and VER_12.
Let's get this in, as the driver has been broken for weeks now.

* * * *

Fix r8169 regression on ASUS motherboards.

Second attempt.  This one fixes both VER_11 and VER_12 MACs.

The r8169 ethernet driver worked fine in 2.6.23, but fails
in 2.6.24-rc* for the onboard ethernet of ASUS P5B series motherboards.
This patch fixes it again.

Signed-off-by: Mark Lord <mlord@...ox.com>

--- broken/drivers/net/r8169.c	2007-11-03 16:24:16.000000000 -0400
+++ linux/drivers/net/r8169.c	2007-11-07 17:22:59.000000000 -0500
@@ -1326,6 +1326,7 @@
 		break;
 	case RTL_GIGA_MAC_VER_11:
 	case RTL_GIGA_MAC_VER_12:
+		break;
 	case RTL_GIGA_MAC_VER_17:
 		rtl8168b_hw_phy_config(ioaddr);
 		break;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/