From: "Jörg Krause" <jkrause@posteo.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] usb: ci_udc: Allocate the qTD list directly
Date: Tue, 01 Jul 2014 13:22:41 +0200 [thread overview]
Message-ID: <53B29A01.6080108@posteo.de> (raw)
In-Reply-To: <201407011319.37499.marex@denx.de>
On 07/01/2014 01:19 PM, Marek Vasut wrote:
> [snip]
>>> Can you edit arch/arm/cpu/arm926ejs/cache.c and change the debug() to
>>> printf() , then re-test please ? I suspect this might trap something
>>> still. Ah, and please test on u-boot-usb/master with this patch.
>> No additional output on the console.
> What does this mean? Do you see warning messages prefixed with "CACHE: " ?
No messages prefixed with "CACHE: ". Just the usual error message.
=>
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
ERROR: The remote end did not respond in time.
at drivers/usb/gadget/ether.c:2392/usb_eth_init()
> Best regards,
> Marek Vasut
next prev parent reply other threads:[~2014-07-01 11:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 23:53 [U-Boot] [PATCH] usb: ci_udc: Allocate the qTD list directly Marek Vasut
2014-06-30 23:55 ` Marek Vasut
2014-07-01 0:04 ` [U-Boot] [PATCH V2] " Marek Vasut
2014-07-01 6:51 ` Jörg Krause
2014-07-01 10:17 ` Marek Vasut
2014-07-01 11:03 ` Jörg Krause
2014-07-01 11:19 ` Marek Vasut
2014-07-01 11:22 ` Jörg Krause [this message]
2014-07-01 11:35 ` Marek Vasut
2014-07-01 11:48 ` Jörg Krause
2014-07-01 22:34 ` Jörg Krause
2014-07-01 22:36 ` Stephen Warren
2014-07-01 22:47 ` Jörg Krause
2014-07-01 22:51 ` Stephen Warren
2014-07-01 22:57 ` Jörg Krause
2014-07-01 23:10 ` Stephen Warren
2014-07-01 15:03 ` Stephen Warren
2014-07-01 15:13 ` Marek Vasut
2014-07-01 15:16 ` Stephen Warren
2014-07-01 15:22 ` 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=53B29A01.6080108@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox