From: Martin Mueller <martin@pfump.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] NEC OHCI chip bug
Date: Wed, 15 Dec 2010 11:19:25 +0100 (MET) [thread overview]
Message-ID: <201012151019.oBFAJPE5024913@post.webmailer.de> (raw)
Hi Gavin ,
> We need NEC pci-to-usb host controller work on U-boot. Because
> using Faraday technology PCI controller, I need to complete the PCI
> driver first. Now the PCI driver is completed. At this time, the
> NEC host controller can work. When plugging a keyboard, 2 devices
> can be found showing on console. But things are not as easy as we
> think, OHCI host controller encounter an "Unrecoverable Error"
> when getting device descriptor from keyboard. In the Linux kernel,
> I found that there is a workaround if the OHCI host controller is
> NEC's. The following link explain more detail:
> http://www.mail-archive.com/linux-usb-devel at lists.sourceforge.net/msg54465.html
> After looking at the source code in U-boot, it seems that there
> isn't any workaround about the NEC's bug ? Any idea about how to
> get the controller, or do I need to implement the workaround by
> myself ??
are you sure it is that NEC bug? We had a similar error message when
the PCI bridge was not properly setup and the OHCI could not access
RAM through PCI (DMA), hence the "unrecoverable error".
Martin
next reply other threads:[~2010-12-15 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 10:19 Martin Mueller [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-17 9:39 [U-Boot] NEC OHCI chip bug Martin Mueller
2010-12-21 6:43 ` Macpaul Lin
2010-12-17 9:25 gavinguo at andestech.com
2010-12-17 3:49 gavinguo at andestech.com
2010-12-17 7:49 ` Martin Mueller
2010-12-16 9:46 Martin Mueller
2010-12-16 2:11 gavinguo at andestech.com
2010-12-15 8:32 gavinguo at andestech.com
2010-12-15 6:21 gavinguo at andestech.com
2010-12-15 7:26 ` 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=201012151019.oBFAJPE5024913@post.webmailer.de \
--to=martin@pfump.org \
--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