netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: rl@hellgate.ch, netdev@oss.sgi.com
Subject: Re: via-rhine unable to send back-to-back packets?
Date: Tue, 30 Nov 2004 12:25:03 -0800	[thread overview]
Message-ID: <20041130122503.0adac947.davem@davemloft.net> (raw)
In-Reply-To: <20041130064823.GA27872@xi.wantstofly.org>

On Tue, 30 Nov 2004 07:48:23 +0100
Lennert Buytenhek <buytenh@wantstofly.org> wrote:

> Yeah, preamble (8 bytes), CRC (4 bytes), inter-packet gap (12 bytes).

Ok.

> Perhaps the via-rhine simply can't send out packets back-to-back and
> needs 14 byte times of inter-packet gap.  I couldn't find any stray +2
> in the driver anywhere but I'm just checking.

Or the via-rhine driver is not programming one of the registers
proper to get optimal spacing.

As with most Donald Becker drivers, many of the register layouts
are not documented in the sources so it's not possible to just
scan the driver looking for potential problems like this.
For example, maybe the TxConfig register has an "IPG" field but
we'll never know by reading anything in the driver source.

  parent reply	other threads:[~2004-11-30 20:25 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 [this message]
2004-11-30 22:06       ` Roger Luethi
2004-12-01 20:01         ` Lennert Buytenhek
2004-12-02 11:01           ` Roger Luethi
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=20041130122503.0adac947.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=buytenh@wantstofly.org \
    --cc=netdev@oss.sgi.com \
    --cc=rl@hellgate.ch \
    /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).