From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Juergen Wolf <JuWo@N-Club.de>
Cc: Francois Romieu <romieu@cogenit.fr>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: [PATCH] Re: Problem with SMC Etherpower II + kernel newer 2.4.2
Date: Fri, 06 Jul 2001 08:59:12 -0400 [thread overview]
Message-ID: <3B45B61F.BA6AA1BF@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0107021014230.15054-100000@flash.datafoundation.com> <3B42DEC2.AAB1E65B@N-Club.de> <20010704145752.A29311@se1.cogenit.fr> <3B456D45.FBF10C1A@N-Club.de> <20010706134421.B20614@se1.cogenit.fr> <3B45AEBD.8D0599E3@N-Club.de>
[-- Attachment #1: Type: text/plain, Size: 202 bytes --]
Here is the patch I have in CVS, against kernel 2.4.7-pre3.
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024 | can cause malaise in laboratory mice.
MandrakeSoft |
[-- Attachment #2: epic100-2.4.7.3.patch --]
[-- Type: text/plain, Size: 870 bytes --]
--- /spare/tmp/linux-2.4.7-pre3/drivers/net/epic100.c Mon Jul 2 21:03:04 2001
+++ linux/drivers/net/epic100.c Fri Jul 6 12:56:40 2001
@@ -48,13 +48,16 @@
* ethtool driver info support (jgarzik)
LK1.1.9:
- * MII ioctl support (jgarzik)
+ * ethtool media get/set support (jgarzik)
+
+ LK1.1.10:
+ * revert MII transceiver init change (jgarzik)
*/
#define DRV_NAME "epic100"
-#define DRV_VERSION "1.11+LK1.1.9"
-#define DRV_RELDATE "July 2, 2001"
+#define DRV_VERSION "1.11+LK1.1.10"
+#define DRV_RELDATE "July 6, 2001"
/* The user-configurable values.
@@ -448,7 +451,7 @@
outl(0x0008, ioaddr + TEST1);
/* Turn on the MII transceiver. */
- outl(dev->if_port == 1 ? 0x13 : 0x12, ioaddr + MIICfg);
+ outl(0x12, ioaddr + MIICfg);
if (chip_idx == 1)
outl((inl(ioaddr + NVCTL) & ~0x003C) | 0x4800, ioaddr + NVCTL);
outl(0x0200, ioaddr + GENCTL);
next prev parent reply other threads:[~2001-07-06 12:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 11:55 Problem with SMC Etherpower II + kernel newer 2.4.2 Juergen Wolf
2001-07-02 14:18 ` John Jasen
2001-07-04 9:15 ` Juergen Wolf
2001-07-04 12:57 ` Francois Romieu
2001-07-06 7:48 ` Juergen Wolf
2001-07-06 11:44 ` Francois Romieu
2001-07-06 12:27 ` Juergen Wolf
2001-07-06 12:34 ` Jeff Garzik
2001-07-06 12:51 ` Juergen Wolf
2001-07-06 12:59 ` Jeff Garzik [this message]
2001-07-06 15:04 ` [PATCH] " Francois Romieu
2001-07-03 9:31 ` Florian Schmitt
2001-07-03 14:57 ` Olivier Sessink
2001-07-04 9:19 ` Francois Romieu
2001-07-04 15:30 ` Florian Schmitt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B45B61F.BA6AA1BF@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=JuWo@N-Club.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@cogenit.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox