From: Ben Hutchings <bhutchings@solarflare.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: Mitchell Erblich <erblichs@earthlink.net>,
Benjamin Li <benli@broadcom.com>, Joe Jin <joe.jin@oracle.com>,
Michael Chan <mchan@broadcom.com>,
"terry.liu@oracle.com" <terry.liu@oracle.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Broadcom 5709 take long time to bring up
Date: Wed, 18 Aug 2010 23:19:32 +0100 [thread overview]
Message-ID: <1282169972.3454.148.camel@localhost> (raw)
In-Reply-To: <4C6C4FE5.20509@hp.com>
On Wed, 2010-08-18 at 14:25 -0700, Rick Jones wrote:
> Mitchell Erblich wrote:
> > On Aug 18, 2010, at 9:08 AM, Benjamin Li wrote:
> >
> >
> >>Hi Joe,
> >>
> >>Just a couple of quick questions:
> >>
> >>1. It is possible that autonegotiation could take in the orders of
> >>seconds depending on the remote partner.
> >
> >
> > No. It happens in ms.
> >
> > Mitchell Erblich
>
> Both may be correct, depending on the context. The IEEE specs likely mandate
> that autonegotiation take no longer than N ms, but there may indeed be kit out
> there that takes rather longer...
Autonegotiation per se should not take very long, but 1000BASE-T or
10GBASE-T also require the PHYs to sync clocks, detect and cancel
echoes, and so on. I believe that that link training normally takes a
few seconds after AN is done.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-08-18 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 14:34 Broadcom 5709 take long time to bring up Joe Jin
2010-08-18 16:08 ` Benjamin Li
2010-08-18 20:44 ` Mitchell Erblich
2010-08-18 21:25 ` Rick Jones
2010-08-18 22:19 ` Ben Hutchings [this message]
2010-08-19 1:13 ` Joe Jin
2010-08-19 8:11 ` Joe Jin
2010-08-23 14:21 ` Joe Jin
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=1282169972.3454.148.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=benli@broadcom.com \
--cc=erblichs@earthlink.net \
--cc=joe.jin@oracle.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=terry.liu@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.