All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <jkrause@posteo.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] usb: ci_udc: fix interaction with CONFIG_USB_ETH_CDC
Date: Sat, 28 Jun 2014 01:27:25 +0200	[thread overview]
Message-ID: <53ADFDDD.30900@posteo.de> (raw)
In-Reply-To: <53ADE8AA.8070907@wwwdotorg.org>


On 06/27/2014 11:56 PM, Stephen Warren wrote:
> On 06/27/2014 03:52 PM, J?rg Krause wrote:
>> I have tested a little bit more.
>>
>> It does NOT help waiting some seconds before running tftp again.
>> Sometimes it just works running tfpd immediately after a previous tfpd.
>> Sometimes waiting even a minute ends up in the described error.
>>
>> Odd, very odd, sorry :-)
> OK, that makes a little more sense. Intermittent issues are fine, but
> intermittent issues affected by time delays are odd!
>
> Does the *first* invocation of "tftp" after the board is powered on
> always work perfectly?
Yes, always! The next runs of tftp sometimes works perfectly, sometimes 
I have timeouts, but it runs to end, and sometimes it did not even 
start, throwing the described error. But there are no crashes while 
running tfpd anymore :-)

FYI: I applied a series of patches from Heiko Schocher: [PATCH v5 0/5] 
mtd, ubi, ubifs: resync with Linux-3.14 on top of the patches for 
ci_udc. Now the USB Ethernet driver is completely broken. It does not 
even run a first time.
>> On 06/27/2014 11:37 PM, J?rg Krause wrote:
>> [snip]

  reply	other threads:[~2014-06-27 23:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 18:02 [U-Boot] [PATCH] usb: ci_udc: fix interaction with CONFIG_USB_ETH_CDC Stephen Warren
2014-06-23 19:03 ` Eric Nelson
2014-06-25 13:51 ` Marek Vasut
2014-06-25 16:06   ` Stephen Warren
2014-06-27 21:37     ` Jörg Krause
2014-06-27 21:52       ` Jörg Krause
2014-06-27 21:56         ` Stephen Warren
2014-06-27 23:27           ` Jörg Krause [this message]
2014-06-27 21:55       ` Stephen Warren
2014-06-27 23:16         ` Jörg Krause
2014-06-27 23:37           ` Stephen Warren
2014-06-28  0:09             ` Jörg Krause
2014-06-28  1:34             ` Jörg Krause
2014-06-28 20:37               ` Jörg Krause
2014-06-28 20:45                 ` Marek Vasut
2014-06-28 20:53                   ` Jörg Krause
2014-06-29 20:33                     ` Jörg Krause
2014-06-30  9:37                       ` Marek Vasut
2014-06-30 13:34                         ` Jörg Krause
2014-06-30 16:02               ` Stephen Warren
2014-06-30 19:55                 ` Stephen Warren
2014-06-30 22:44                   ` Jörg Krause
2014-06-30 22:51                     ` Stephen Warren
2014-06-30 23:17                       ` Jörg Krause
2014-06-30 23:56                         ` Marek Vasut
2014-06-30 20:55                 ` Jörg Krause
2014-06-30 21:15                   ` Marek Vasut
2014-06-30 21:43                     ` Jörg Krause
2014-06-30 21:50                       ` Marek Vasut
2014-06-25 20:20 ` 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=53ADFDDD.30900@posteo.de \
    --to=jkrause@posteo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.