From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Stefan Roese <sr@denx.de>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
linux-usb@vger.kernel.org, Mark Miesfeld <mmiesfeld@amcc.com>
Subject: Re: [USB] powerpc: Workaround for the PPC440EPX USBH_23 errata [take 3]
Date: Sun, 9 Nov 2008 19:40:00 +0100 [thread overview]
Message-ID: <20081109194000.6bc30e0c@vitb-lp> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0811030951001.2454-100000@iolanthe.rowland.org>
В Mon, 3 Nov 2008 09:51:55 -0500 (EST)
Alan Stern <stern@rowland.harvard.edu> пишет:
> On Mon, 3 Nov 2008, Vitaly Bordug wrote:
>
> > A published errata for ppc440epx states, that when running Linux
> > with both EHCI and OHCI modules loaded, the EHCI module experiences
> > a fatal error when a high-speed device is connected to the USB2.0,
> > and functions normally if OHCI module is not loaded.
> >
> > There used to be recommendation to use only hi-speed or full-speed
> > devices with specific conditions, when respective module was
> > unloaded. Later, it was observed that ohci suspend is enough to
> > keep things going, and it was turned into workaround, as explained
> > below.
>
> Please fix this patch so that it does not cause a build error on
> non-PowerPC architectures.
Sorry for the late reply, I was travelling last week.
The latest patch was of course compile-tested with x86 and across
different powerpcs, and apparently inlined patch was not the latest one,
differing in that one little hunk. That was me confusing branches in
a hurry- big thanks for catching this.
Proper code (with explicit nop in non-ppc case) will follow right away.
-Vitaly
next prev parent reply other threads:[~2008-11-09 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 22:06 [USB] powerpc: Workaround for the PPC440EPX USBH_23 errata [take 3] Vitaly Bordug
2008-11-03 14:51 ` Alan Stern
2008-11-09 18:40 ` Vitaly Bordug [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-09 18:43 Vitaly Bordug
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=20081109194000.6bc30e0c@vitb-lp \
--to=vitb@kernel.crashing.org \
--cc=linux-usb@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).