[top posting because context may be missing otherwise, over a week later]
Excellent analysis, Willy. Quite frankly, I am not keen on making this
driver any more complex, especially if the gains are marginal at best. VIA
Rhine will never be high-performance hardware, and we have too much special
ca
submit a report and/or patch.
I believe vda may have been referring to this. I can send you the
original thread if it's not in your mail archive.
Roger
-- cut here ------
From: Roger Luethi <[EMAIL PROTECTED]>
Subject: Re: via-rhine + l
> @@ -31,7 +31,7 @@
> #define APC_BPORT_REG 0x30
>
> #define APC_REGMASK0x01
> -define APC_BPMASK 0x03
> +#define APC_BPMASK 0x03
Color me skeptical. I've seen some weird bit flips and data corruption;
"paramters" to "paramEters" I could buy. But data corru
Jeff, can you tune in for a moment?
First of all, many thanks to vda for tracking this down, and to everyone
else who helped with it.
I had a look at my code and at 8139cp (which is one of only a handful
of drivers that have been converted to use the generic MII stuff).
Turns out 8139cp doesn't
On Thu, 24 Mar 2005 01:37:55 +0100, Thomas Skora wrote:
> The via-rhine driver in the actual kernel release 2.6.11.5 resets
> wake-on-lan-settings of the chip. This leads to the fact, that wol is
> disabled after the first reboot. I've attached a little patch, that
> fixes the problem.
This patch
5 matches
Mail list logo
