[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1282169972.3454.148.camel@localhost>
Date: Wed, 18 Aug 2010 23:19:32 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: Rick Jones <rick.jones2@...com>
Cc: Mitchell Erblich <erblichs@...thlink.net>,
Benjamin Li <benli@...adcom.com>, Joe Jin <joe.jin@...cle.com>,
Michael Chan <mchan@...adcom.com>,
"terry.liu@...cle.com" <terry.liu@...cle.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Broadcom 5709 take long time to bring up
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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists