From: Roger Luethi <rl@hellgate.ch>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>
Subject: Re: [0/4][via-rhine] Improvements
Date: Sat, 15 Feb 2003 21:53:02 +0100 [thread overview]
Message-ID: <20030215205302.GB4627@k3.hellgate.ch> (raw)
In-Reply-To: <3E4E9028.3090601@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
On Sat, 15 Feb 2003 14:08:24 -0500, Jeff Garzik wrote:
> Looks good, all patches applied to 2.5.
Thx. Patch to bump the version number up attached.
> Should these apply to 2.4, too?
Yes. I'm trying to keep the drivers in both trees in sync.
> Just a general comment, the reset logic seems a bit too much like voodoo
> magic ;-)
Look at the rest of the driver and you will find the reset voodoo magic is
a perfect fit. We'd be waving dead chickens if only tar could handle them.
Actually, the reset logic is slightly better because for every line I have
some reasoning and actual tests conducted. The underlying problem is that
the Rhine is only loosely documented and various revisions differ in
amazing ways from each other and from the documentation that supposedly
describes them.
I've named the magic register in the patch below, does that ease your
voodoo pain?
I've been considering for a while to document the driver somewhat better.
Are documentation patches welcome, or do you just want to have official
word from VIA that they agree with the reset code? And if I need a few
lines to explain some voodoo magic, is the prefered way to put it into the
source or would a freshly created Documentation/network/via-rhine.txt be
(my first choice but the directory typically contains user rather than
developer documentation) the better place?
> It would be nice long-term to get an official answer from Via
> about the proper reset sequence and time limits. [regardless, like I
Heh. If I had a contact at VIA I'd have many and more important questions
than the reset sequence that actually works now, unlike lots of other
stuff. Yes, reliable information from within VIA -- official or not --
would be a big help.
Roger
[-- Attachment #2: via-rhine-1.16rc-05_changelog.diff --]
[-- Type: text/plain, Size: 1298 bytes --]
--- 04_reset/drivers/net/via-rhine.c Fri Feb 14 19:13:04 2003
+++ 05_changelog/drivers/net/via-rhine.c Sat Feb 15 21:33:55 2003
@@ -101,11 +101,18 @@
LK1.1.15 (jgarzik):
- Use new MII lib helper generic_mii_ioctl
+ LK1.1.16 (Roger Luethi)
+ - Etherleak fix
+ - Handle Tx buffer underrun
+ - Fix bugs in full duplex handling
+ - New reset code uses "force reset" cmd on Rhine-II
+ - Various clean ups
+
*/
#define DRV_NAME "via-rhine"
-#define DRV_VERSION "1.1.15"
-#define DRV_RELDATE "November-22-2002"
+#define DRV_VERSION "1.1.16"
+#define DRV_RELDATE "February-15-2003"
/* A few user-configurable values.
@@ -395,7 +402,7 @@ enum register_offsets {
MIIPhyAddr=0x6C, MIIStatus=0x6D, PCIBusConfig=0x6E,
MIICmd=0x70, MIIRegAddr=0x71, MIIData=0x72, MACRegEEcsr=0x74,
ConfigA=0x78, ConfigB=0x79, ConfigC=0x7A, ConfigD=0x7B,
- RxMissed=0x7C, RxCRCErrs=0x7E,
+ RxMissed=0x7C, RxCRCErrs=0x7E, MiscCmd=0x81,
StickyHW=0x83, WOLcrClr=0xA4, WOLcgClr=0xA7, PwrcsrClr=0xAC,
};
@@ -532,7 +539,7 @@ static void wait_for_reset(struct net_de
/* Rhine-II needs to be forced sometimes */
if (chip_id == VT6102)
- writeb(0x40, ioaddr + 0x81);
+ writeb(0x40, ioaddr + MiscCmd);
/* VT86C100A may need long delay after reset (dlink) */
/* Seen on Rhine-II as well (rl) */
next prev parent reply other threads:[~2003-02-15 20:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 11:17 [0/4][via-rhine] Improvements Roger Luethi
2003-02-15 11:18 ` [1/4][via-rhine][PATCH] Trivial changes; not affecting functionality Roger Luethi
2003-02-15 11:18 ` [2/4][via-rhine][PATCH] Fix broken Tx underrun handling Roger Luethi
2003-02-15 11:18 ` [3/4][via-rhine][PATCH] Various duplex related fixes Roger Luethi
2003-02-15 11:18 ` [4/4][via-rhine][PATCH] Reset function rewrite Roger Luethi
2003-02-15 19:08 ` [0/4][via-rhine] Improvements Jeff Garzik
2003-02-15 20:53 ` Roger Luethi [this message]
2003-02-15 21:49 ` Jeff Garzik
2003-02-15 22:52 ` Roger Luethi
2003-02-16 0:16 ` Linus Torvalds
2003-02-16 11:01 ` Roger Luethi
2003-02-17 18:44 ` Jeff Garzik
2003-02-15 21:40 ` Jeff Garzik
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=20030215205302.GB4627@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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