From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Realtek 8110S/8169S driver.
Date: Thu, 16 Dec 2004 18:05:03 -0500 [thread overview]
Message-ID: <57e9e658d475caccf8ab040000248fe1@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0412161559310.8411@linux.site>
On Thu Dec 16 18:00:57 EST 2004, rminnich@lanl.gov wrote:
> any change it is half/full duplex nonsense? This is also a common source
> of badness in performance.
>
> ron
there are no transmission/reception errors reported. the phy says
it has negotiated correctly, e.g. it reports the correct speed and
duplex on both the 100 and 1000 links i've tried. the nic+phy require
no real management, they are very tightly bound and there's nothing
the driver has to do to the nic which depends on what the phy negotiates
as far as i can see.
--jim
next prev parent reply other threads:[~2004-12-16 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 21:29 jmk
2004-12-16 22:43 ` andrey mirtchovski
2004-12-16 22:50 ` jmk
2004-12-16 22:59 ` Ronald G. Minnich
2004-12-16 23:05 ` jmk [this message]
2004-12-21 15:17 ` jmk
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=57e9e658d475caccf8ab040000248fe1@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).