From: Troy Kisky <troy.kisky@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] TFTP timeouts, i.mx fec problem?
Date: Fri, 31 May 2013 12:09:02 -0700 [thread overview]
Message-ID: <51A8F54E.5020502@boundarydevices.com> (raw)
In-Reply-To: <20130531185808.89E903831BA@gemini.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
next prev parent reply other threads:[~2013-05-31 19:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 6:56 [U-Boot] TFTP timeouts, i.mx fec problem? Ruud Commandeur
2013-05-31 7:56 ` Wolfgang Denk
2013-05-31 8:50 ` Stefano Babic
2013-05-31 10:16 ` Ruud Commandeur
2013-05-31 12:54 ` Ruud Commandeur
2013-05-31 14:19 ` Wolfgang Denk
2013-05-31 14:36 ` Ruud Commandeur
2013-05-31 15:40 ` Stefano Babic
2013-05-31 18:56 ` Wolfgang Denk
2013-05-31 15:46 ` Stefano Babic
2013-05-31 16:00 ` Fabio Estevam
2013-05-31 18:58 ` Wolfgang Denk
2013-05-31 19:09 ` Troy Kisky [this message]
2013-06-01 9:18 ` Ruud Commandeur
2013-06-07 0:15 ` Fabio Estevam
2013-06-07 1:25 ` Marek Vasut
2013-06-07 1:34 ` Fabio Estevam
2013-06-07 1:50 ` Marek Vasut
2013-06-07 9:28 ` Ruud Commandeur
2013-06-07 9:39 ` Eric Bénard
2013-06-14 13:01 ` Ruud Commandeur
2013-06-14 15:30 ` Wolfgang Denk
2013-06-17 6:51 ` Ruud Commandeur
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=51A8F54E.5020502@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=u-boot@lists.denx.de \
/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