From mboxrd@z Thu Jan  1 00:00:00 1970
From: Troy Kisky <troy.kisky@boundarydevices.com>
Date: Fri, 31 May 2013 12:09:02 -0700
Subject: [U-Boot] TFTP timeouts, i.mx fec problem?
In-Reply-To: <20130531185808.89E903831BA@gemini.denx.de>
References: <15AE5A936F5E3A42A9144E66875A0A893090E4@server1-derijp.CLB-Benelux.lokaal>
	<51A86445.3040703@denx.de>
	<20130531141902.698623831C2@gemini.denx.de>
	<51A8C5DA.3090605@denx.de>
	<20130531185808.89E903831BA@gemini.denx.de>
Message-ID: <51A8F54E.5020502@boundarydevices.com>
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 5/31/2013 11:58 AM, Wolfgang Denk wrote:
> Dear Stefano Babic,
>
> In message <51A8C5DA.3090605@denx.de> you wrote:
>>> The question is if there is no better way to wait for the PHY to
>>> become (really) ready?
>> The phy is reinitialized after each transaction - the safiest condition
>> to boot afterwards the kernel. Or we need a way to stop the phy only
> Yes, that is clear, we fully agree on that.
>
> But can we not test for "autoneogitation completed, link up and
> running" before we send the first packet?
>
> Or rather - why do we have this issue appearently only on i.MX?  We
> don't see this on other ARM or on PowerPC?
>
> Best regards,
>
> Wolfgang Denk
>
Think of this as incentive to convert to the board to  PHYLIB.

Troy