From: Roger Luethi <rl@hellgate.ch>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: via-rhine unable to send back-to-back packets?
Date: Thu, 2 Dec 2004 12:01:20 +0100 [thread overview]
Message-ID: <20041202110120.GA16597@k3.hellgate.ch> (raw)
In-Reply-To: <20041201200148.GE14470@xi.wantstofly.org>
[Thanks to A.J. from VNT for the answer which I am relaying below.]
On Wed, 01 Dec 2004 21:01:48 +0100, Lennert Buytenhek wrote:
> "Is the hardware capable of sending back-to-back packets (i.e. with
> an inter-packet gap of no more than 96 bit times)?"
=> YES. All the VIA Rhine Fast Ethernet controllers follows the IEEE
standard (inter-frame gap is 96 bit time) and it is hardware fixed and
NOT programmable.
> "Can misprogramming the chip lead to the effect that the inter-packet
> gap is never less than 112 bit times?"
=> NO, it is fixed and neither software nor board level change could
modify the inter-frame gap of VIA Rhine Fast Ethernet controller.
> > Of course, you can always check if VIA's driver has the same issue. If
> > it doesn't, chances are we can borrow the fix.
>
> Hmm, didn't know they had such a driver. Where can I find it?
=> in http://www.viaarena.com/ , choose "downloads" => "Drivers" =>
choose target OS (e.g. Fedora Core Linux) => "Ethernet (Networking/LAN)"
=> choose the type of your Ethernet controller => click to download
the combo driver software package.
next prev parent reply other threads:[~2004-12-02 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 22:27 via-rhine unable to send back-to-back packets? Lennert Buytenhek
2004-11-30 1:25 ` David S. Miller
2004-11-30 6:48 ` Lennert Buytenhek
2004-11-30 17:41 ` Ben Greear
2004-12-01 19:55 ` Lennert Buytenhek
2004-11-30 20:25 ` David S. Miller
2004-11-30 22:06 ` Roger Luethi
2004-12-01 20:01 ` Lennert Buytenhek
2004-12-02 11:01 ` Roger Luethi [this message]
2004-12-02 11:09 ` Lennert Buytenhek
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=20041202110120.GA16597@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=buytenh@wantstofly.org \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.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).