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
This archive was generated by hypermail 2b29 : Sat Feb 15 2003 - 22:01:04 EST