From: Richard Dawe <rich@phekda.gotadsl.co.uk>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@oss.sgi.com, Me <rich@phekda.gotadsl.co.uk>
Subject: Re: Acer Aspire 1524WLMi and RealTek 8169 - very slow
Date: Sat, 05 Feb 2005 13:26:25 +0000 [thread overview]
Message-ID: <4204C981.6050102@phekda.gotadsl.co.uk> (raw)
In-Reply-To: <20050125214725.GA6093@electric-eye.fr.zoreil.com>
Hello.
Francois Romieu wrote:
> Hi,
>
> could you give the patch below some testing ?
>
> Any post-LLTX-revert 2.6.11-rc2-bk should do.
>
> Merge of Realtek's code
> - code dedicated to a new phy (spotted by Richard Dawe);
> - C+ register fiddling seems required for both RTL_GIGA_MAC_VER_{D/E};
> - apart from being reserved, register at address 0xe2 is named 'IntrMitigate';
> - bump version number.
> A bunch of people do not use the vanilla kernel module simply because
> Realtek's driver has a higher revision number. This is not an issue per
> se but their driver is buggy due to some partial merge of in-kernel code.
[snip]
Applied to 2.6.11-rc3. It seems to work fine. I've passed ~20GB of data
at 100Mbps full-duplex with no errors (compared MD5 sums on files). My
data rate test (sftp of Linux kernel source tarball) gave about the same
data rate as 1.6LK + PHY patch - ~7.1MB/sec.
It works fine setting the speed & duplex using "ethtool -s eth0 autoneg
off speed <speed> duplex <duplex>".
I haven't tested the VLAN or jumbo(ish) frames. Let me know if you'd
like me to test those too. Although I'm not sure if I can test jumbo
frames with the equipment I have.
One more thing:
With 1.6LK + my PHY patch, I see the message "eth0: PHY reset until link
up" every 5 seconds or so, when there is no Ethernet cable plugged in.
This is annoying. I think it should only log it once.
I'll repeat my cable removal/insertion tests with 2.2LK later and let
you know what I find.
Bye, Rich =]
--
Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ]
"You can't evaluate a man by logic alone."
-- McCoy, "I, Mudd", Star Trek
next prev parent reply other threads:[~2005-02-05 13:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 13:16 Acer Aspire 1524WLMi and RealTek 8169 - very slow Richard Dawe
2004-11-21 13:24 ` Richard Dawe
2004-11-21 19:47 ` Richard Dawe
2004-11-21 20:58 ` Francois Romieu
2004-11-22 20:42 ` Richard Dawe
2004-11-22 21:30 ` Francois Romieu
2004-11-22 22:07 ` Richard Dawe
2004-11-24 19:36 ` Richard Dawe
2004-11-30 19:52 ` Jon Mason
2004-12-29 10:17 ` Richard Dawe
2004-12-29 23:52 ` Francois Romieu
2005-01-02 13:51 ` Richard Dawe
2005-01-02 15:23 ` Richard Dawe
2005-01-22 13:10 ` Richard Dawe
2005-01-22 15:22 ` Richard Dawe
2005-01-22 23:01 ` Francois Romieu
2005-01-23 19:08 ` Richard Dawe
2005-01-25 21:47 ` Francois Romieu
2005-02-05 13:26 ` Richard Dawe [this message]
2005-02-05 20:41 ` Francois Romieu
2005-02-06 10:54 ` Richard Dawe
2005-02-08 23:00 ` Richard Dawe
2005-02-12 0:07 ` Francois Romieu
2004-11-21 23:28 ` [patch] ethtool (was Re: Acer Aspire 1524WLMi and RealTek 8169 - very slow) Francois Romieu
2005-01-27 20:27 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 22:00 Acer Aspire 1524WLMi and RealTek 8169 - very slow Brandeburg, Jesse
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=4204C981.6050102@phekda.gotadsl.co.uk \
--to=rich@phekda.gotadsl.co.uk \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).