public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] TFTP timeouts, i.mx fec problem?
Date: Fri, 7 Jun 2013 03:25:08 +0200	[thread overview]
Message-ID: <201306070325.08776.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5A2t_o8F7f71P2=-t3PBPFAARvap=Yphc8xn9rBBeYLbw@mail.gmail.com>

Dear Fabio Estevam,

> Hi Ruud,
> 
> On Fri, May 31, 2013 at 3:56 AM, Ruud Commandeur <RCommandeur@clb.nl> wrote:
> > Hi everyone,
> > 
> > I have been testing for a while now on the i.mx28 evk, and I noticed
> > that almost all tftp transfers take some time before they actually
> > start. It will show a 'T' as first character, then followed by '#'
> 
> Besides the initial timeout you mentioned, I also see some timeouts
> during the kernel transfer.
> 
> I have just sent two patches converting mx28evk to use phylib, but I
> still see the timeouts there.
> 
> I see that in the kernel there is a workaround for LAN8270 low por
> mode and I will try it when I have a chance.
> 
> Please let me know if you make any progress on this.

I'm also having issues when pulling stuff from my main system via TFTP 
sometimes. This is manifesting by _lots_ of timeouts. The problem in this case 
is some weirdness in e1000e in my system, after I force-switch the main system 
to 100baseT (using ethtool -s eth0 speed 100 duplex full), I no longer get 
timeouts (even after I force-switch it back to 1000baseT later). But I suspect 
this is some network issue on my end.

Best regards,
Marek Vasut

  reply	other threads:[~2013-06-07  1:25 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
2013-06-01  9:18           ` Ruud Commandeur
2013-06-07  0:15 ` Fabio Estevam
2013-06-07  1:25   ` Marek Vasut [this message]
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=201306070325.08776.marex@denx.de \
    --to=marex@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