From: Alper YILDIRIM <yildirimalper@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] musb: usb storage: USB device not accepting new address error
Date: Tue, 29 Mar 2011 06:38:04 -0700 (PDT) [thread overview]
Message-ID: <31267662.post@talk.nabble.com> (raw)
In-Reply-To: <AANLkTimGnL7_zw5i3ssy7ciPptY3Dm-WVRuZaHHwTA6X@mail.gmail.com>
Hi,
Remy Bohmer-5 wrote:
>
>
> Have you tried 'git bisect' to find the offending patch already?
>
>
I found the offending patch, it is the following commit that
makes usb broken on OMAPL138. When i revert the patch the
problem no more occurs.
3c0659b535b075be124c3d2a0714e55e65c46737
ARM: Avoid compiler optimization for readb, writeb and friends.
I am working on a proper solution.
Any help will be appreciated
--
View this message in context: http://old.nabble.com/musb%3A-usb-storage%3A-USB-device-not-accepting-new-address-error-tp31245386p31267662.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
next prev parent reply other threads:[~2011-03-29 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 13:15 [U-Boot] musb: usb storage: USB device not accepting new address error Alper YILDIRIM
2011-03-26 18:01 ` Remy Bohmer
2011-03-26 19:19 ` Alper YILDIRIM
2011-03-29 13:38 ` Alper YILDIRIM [this message]
2011-04-29 20:53 ` Wolfgang Denk
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=31267662.post@talk.nabble.com \
--to=yildirimalper@gmail.com \
--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