From: Roger Luethi <rl@hellgate.ch>
To: Wenping Luo <wluo@fortinet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ethernet Via-rhine driver 1.1.17 duplex detection issue in linux kernel 2.4.25
Date: Thu, 25 Nov 2004 22:54:13 +0100 [thread overview]
Message-ID: <20041125215413.GC1843@k3.hellgate.ch> (raw)
In-Reply-To: <011801c4d270$cca65740$0101140a@fortinet.com>
On Wed, 24 Nov 2004 13:58:58 -0800, Wenping Luo wrote:
> I used crossed ethernet cable to connect one ethernet NIC to a Via Rhine III
> VT6105M NIC. I set the speed mode of Rhine Nic to be "auto" whereas I forced
> the peer NIC to be "100 Full Duplex". The Rhine NIC connected in mode of
> "100 Half Duplex" , instead of "100 Full Duplex", after detecting the peer.
>
> I searched the Internet and I found another reported for similiar issue at
> http://lunar-linux.org/pipermail/lunar/2004-April/003894.html. However,
> there is no answer for this issue yet.
Does it work with 2.6.10-rc? Do other card/driver combinations correctly
detect the setting of your peer NIC?
Roger
next prev parent reply other threads:[~2004-11-27 4:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 21:58 ethernet Via-rhine driver 1.1.17 duplex detection issue in linux kernel 2.4.25 Wenping Luo
2004-11-25 21:54 ` Roger Luethi [this message]
2004-11-26 0:47 ` Wenping Luo
2004-11-27 22:29 ` Lee Revell
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=20041125215413.GC1843@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=wluo@fortinet.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