From: David Gundersen <gundy@iinet.net.au>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: netdev@vger.kernel.org
Subject: Re: r8169 tx problem (1s pause with ping)
Date: Tue, 19 Jun 2007 20:45:44 +1000 [thread overview]
Message-ID: <4677B3D8.1000102@iinet.net.au> (raw)
In-Reply-To: <20070618151430.GE10418@kvack.org>
> Out of curiousity, does it work if you just do a single read (ie
> RTL_R8(TxPoll);) of the register before writing to it? That would clear
> things up if it is a PCI posting problem.
Hi Ben,
I tried your suggestion but it didn't seem to make any difference :(
I tried the following combinations:
- realtek original [broken]
- realtek original with the RTL_R8(TxPoll)
before RTL_W8(TxPoll, NPQ); [broken]
- my patched version without the ndelay
loop but including the RTL_R8(TxPoll)
(to see if my messing with the frag logic
was having any impact) [broken]
- my patched version including the
ndelay loop [full speed transfers]
Also, I'm not sure if I made it clear in my first post, but I'm testing
these changes on a 8168B (it's built in to my GA-945G-S3 motherboard).
I'm not sure if we can assume that the same change applied to the 8169
driver would have the same effect on the 8169 too? (is the 8168 just a
PCI express version of the [pci] 8169?)
Dave.
prev parent reply other threads:[~2007-06-19 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 0:41 r8169 tx problem (1s pause with ping) Benjamin LaHaise
2007-06-13 21:18 ` Francois Romieu
2007-06-14 15:33 ` David Gundersen
2007-06-14 22:00 ` Francois Romieu
2007-06-19 23:06 ` Francois Romieu
2007-06-20 8:57 ` David Gundersen
2007-06-20 21:15 ` Francois Romieu
2007-06-18 15:14 ` Benjamin LaHaise
2007-06-19 10:45 ` David Gundersen [this message]
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=4677B3D8.1000102@iinet.net.au \
--to=gundy@iinet.net.au \
--cc=bcrl@kvack.org \
--cc=netdev@vger.kernel.org \
/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).