From: David Miller <davem@davemloft.net>
To: eilong@broadcom.com
Cc: yaniv.rosner@broadcom.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/8] bnx2x: Minor link related fixes
Date: Wed, 01 Sep 2010 12:01:37 -0700 (PDT) [thread overview]
Message-ID: <20100901.120137.84370412.davem@davemloft.net> (raw)
In-Reply-To: <1283366622.5874.1.camel@lb-tlvb-eilong.il.broadcom.com>
From: "Eilon Greenstein" <eilong@broadcom.com>
Date: Wed, 1 Sep 2010 21:43:42 +0300
> On Wed, 2010-09-01 at 10:45 -0700, David Miller wrote:
>> Can you explain why 10mbit/100mbit links have to use forced link mode
>> and do not use autonegotiation by default? I could understand for
>> 10mbit but 100mbit too?
>>
> Our understanding of the requirements is that if the user selects force
> speed of 1G or higher, it is recommended to use autonegotiation with
> only that speed advertized. However, when the user selects force speed
> of 10M or 100M, assuming the other side is actually forcing the speed,
> using autonegotiation will fail and fall back to parallel detect and
> that will establish link in HD mode (as required) while the other side
> is likely to be using FD this will cause duplex mismatch and many
> errors, so it is best to keep 10M/100M truly forced to support older
> link partners.
I see, thanks for the explanation.
next prev parent reply other threads:[~2010-09-01 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 19:51 [PATCH net-next 0/8] bnx2x: Minor link related fixes Yaniv Rosner
2010-09-01 17:45 ` David Miller
2010-09-01 18:43 ` Eilon Greenstein
2010-09-01 19:01 ` David Miller [this message]
2010-09-02 11:13 ` Ben Hutchings
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=20100901.120137.84370412.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=yaniv.rosner@broadcom.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).