From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: linuxppc-dev@ozlabs.org
Cc: Stefan Roese <sr@denx.de>, Mark Miesfeld <mmiesfeld@amcc.com>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [RFC][USB] powerpc: Workaround for the PPC440EPX USBH_23 errata
Date: Fri, 29 Aug 2008 19:56:02 +0200 [thread overview]
Message-ID: <200808291956.03269.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <48B71497.30500@harris.com>
Hi,
please see my comment below. It might be helpful for some of you.
On Thursday 28 August 2008 23:11:51 Steven A. Falco wrote:
> Alan Stern wrote:
> > Your original post mentioned that the 440EPx has only one USB 2.0 host
> > port. Then how can you use a keyboard and memory stick at the same
> > time? You'd have to plug them into a hub -- in which case only one
> > controller would be needed, the one driving the hub. The patch would
> > be unnecessary.
>
> I have one of these processors on a Sequoia board. What happens is that
> if you build the kernel with both EHCI and OHCI support, then plug in
> a modern USB memory stick, it initially tries EHCI, the driver fails, and
> the whole thing falls back to OHCI. So you wind up running at 12 Mbps.
> The only way to make high speed work is to turn off the OHCI driver, and
> then you cannot support slow devices with that kernel.
There is a simple trick to get all types (full, low ang high speed) of
devices work: use a USB hub with transaction translators. We are doing so on
a custom design based on the 440EPx. So we only build the kernel with EHCI
support and there was no need for this ugly hack.
>
> So, hile you cannot plug two devices in at one time, you can plug in
> different speed devices at different times, and my understanding is that
> this patch will let that work seamlessly.
That's true.
Matthias
prev parent reply other threads:[~2008-08-29 17:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 22:23 [RFC][USB] powerpc: Workaround for the PPC440EPX USBH_23 errata Vitaly Bordug
2008-08-27 14:36 ` Alan Stern
2008-08-28 19:32 ` Vitaly Bordug
2008-08-28 20:13 ` Alan Stern
2008-08-28 21:11 ` Steven A. Falco
2008-08-28 21:33 ` Alan Stern
2008-08-28 22:43 ` Benjamin Herrenschmidt
2008-08-29 15:26 ` Alan Stern
2008-08-29 18:20 ` Vitaly Bordug
2008-08-29 21:30 ` Alan Stern
2008-09-04 20:48 ` Vitaly Bordug
2008-09-04 21:40 ` Alan Stern
2008-09-05 1:35 ` Benjamin Herrenschmidt
2008-09-05 13:01 ` Vitaly Bordug
2008-09-05 15:17 ` Alan Stern
2008-09-06 9:02 ` Vitaly Bordug
2008-08-29 13:25 ` Steven A. Falco
2008-08-29 17:56 ` Matthias Fuchs [this message]
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=200808291956.03269.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mmiesfeld@amcc.com \
--cc=sr@denx.de \
--cc=stern@rowland.harvard.edu \
/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.