From: Marek Vasut <marex@denx.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 22:45:21 +0200 [thread overview]
Message-ID: <201406282245.21271.marex@denx.de> (raw)
In-Reply-To: <53AF278F.80403@posteo.de>
On Saturday, June 28, 2014 at 10:37:35 PM, J?rg Krause wrote:
> On 06/28/2014 09:59 PM, Marek Vasut wrote:
> > I would actually be really glad if you could test plain u-boot-usb/master
> > and see if your USB problem is present there. Also, it would be really
> > nice to isolate the sequence of commands which triggers the bug, so we
> > have a proper reproducible testcase.
> >
> > Anyway, this thread is not a place where I would like to discuss this.
> > This should be discussed in the "original" thread, that is:
> >
> > Subj: [PATCH] usb: ci_udc: fix interaction with CONFIG_USB_ETH_CDC
>
> I cloned u-boot-usb/master and tested it. I am running "tftpd
> rootfs.ubifs" several times. Here is the log (I shortened the loading
> process bar):
[...]
> => tftp rootfs.ubifs
> using ci_udc, OUT ep- IN ep- STATUS ep-
> MAC 00:19:b8:00:00:02
> HOST MAC 00:19:b8:00:00:01
> high speed config #1: 2 mA, Ethernet Gadget, using CDC Ethernet
> USB network up!
> Using usb_ether device
> TFTP from server 10.0.0.1; our IP address is 10.0.0.2
> Filename 'rootfs.ubifs'.
> Load address: 0x40008000
> Loading: [snip]
> ##############################################################T ###
> [snip]
> 1.7 MiB/s
Here it's 1.7MB/s ...
> done
> Bytes transferred = 13205504 (c98000 hex)
> => tftp rootfs.ubifs
> using ci_udc, OUT ep- IN ep- STATUS ep-
> MAC 00:19:b8:00:00:02
> HOST MAC 00:19:b8:00:00:01
> high speed config #1: 2 mA, Ethernet Gadget, using CDC Ethernet
> USB network up!
> Using usb_ether device
> TFTP from server 10.0.0.1; our IP address is 10.0.0.2
> Filename 'rootfs.ubifs'.
> Load address: 0x40008000
> Loading:
> #################################################################
> [snip]
> 5.6 MiB/s
... and here it's 5.6 MB/s ... that's weird.
[...]
> The error always appears after calling tftp the third time! The first
> two runs work fine, but the third one always fails. I run this test
> about 20 times.
And finally, what is the contents of 'rootfs.ubifs' ?
Best regards,
next prev parent reply other threads:[~2014-06-28 20:45 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
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 [this message]
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=201406282245.21271.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