From: Peter Tyser <ptyser@xes-inc.com>
Date: Wed, 04 Feb 2009 15:45:37 -0600
Subject: [U-Boot] [PATCH] tsec: Wait for auto-negotiation to complete
 without link
In-Reply-To: <20090204212632.07F0D8322908@gemini.denx.de>
References: <1233782045-488-1-git-send-email-ptyser@xes-inc.com>
	<2acbd3e40902041320l3bce93c1p989c4c33ca8e7ae@mail.gmail.com>
	<20090204212632.07F0D8322908@gemini.denx.de>
Message-ID: <1233783937.7067.387.camel@localhost.localdomain>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Wed, 2009-02-04 at 22:26 +0100, Wolfgang Denk wrote:
> Dear Andy Fleming,
> 
> In message <2acbd3e40902041320l3bce93c1p989c4c33ca8e7ae@mail.gmail.com> you wrote:
> >
> > Hmmm....I made that change for a reason.  Waiting for autonegotiation
> > to finish on a tsec with no link was quite tiresome.  If you've hooked
> > up the 4th tsec, and try to boot, you end up waiting for *three* tsecs
> > to timeout.  If dhcp fails because the link isn't up you can always
> > try again, or add a delay before dhcp starts so that the link is up.
> 
> Why that? Don't you always enable only the interface you are trying to
> use?
> 
> That would be a bug that needs to be fixed.

It seems like the workaround for the "4 tsec autonegotiation delay" you
mention is to set a sane "ethact" value when you know which port you are
going to be using.  However, there is no good workaround for waiting for
link other than adding an arbitrary delay to the boot process which is
pretty hokey, thus the patch.

Best,
Peter