From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: mxs: Do not reconfigure FEC clock in FEC init
Date: Wed, 16 Oct 2013 11:10:23 +0200 [thread overview]
Message-ID: <525E57FF.1020903@denx.de> (raw)
In-Reply-To: <201310152319.34204.marex@denx.de>
Hi Marek,
On 15/10/2013 23:19, Marek Vasut wrote:
>
> Forget this, the issue is still present. Damn!
>
> It's at least a little clearer to me what happens now. The FEC fails to transmit
> an TFTP block ACK packet -> the server waits 5 seconds -> sends ARP packet ->
> FEC replies and resends the TFTP block ACK again. Why does the FEC swallow a TX
> packet, I don't know.
Anyway, it is strange that this happens only with this board. It appears
as the SOC sends or thinks to have sent, but the packet is corrupted or
not sent at all on the physical layer. Maybe you can check on the other
side of the connection on the switch and/or on the server, if some
errors are detected.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2013-10-16 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 15:20 [U-Boot] [PATCH] ARM: mxs: Do not reconfigure FEC clock in FEC init Marek Vasut
2013-10-13 20:20 ` Marek Vasut
2013-10-14 7:46 ` Hector Palacios
2013-10-14 8:17 ` Hector Palacios
2013-10-14 8:34 ` Stefano Babic
2013-10-15 21:19 ` Marek Vasut
2013-10-16 9:10 ` Stefano Babic [this message]
2013-10-16 14:06 ` Marek Vasut
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=525E57FF.1020903@denx.de \
--to=sbabic@denx.de \
--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