From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] USB: EHCI: hot-fix OMAP and Orion multiplatform config
Date: Mon, 18 Mar 2013 17:32:18 +0000 [thread overview]
Message-ID: <201303181732.18438.arnd@arndb.de> (raw)
In-Reply-To: <878v5kd503.fsf@lebrac.rtp-net.org>
On Monday 18 March 2013, Arnaud Patard wrote:
> Arnd Bergmann <arnd@arndb.de> writes:
> > Sure, it's your decision. I just don't want to be accused of abandoning the
> > issue that I caused. It's not strictly a regression because no configuration
> > that was working in 3.8 is broken in 3.9, and embedded systems won't normally
> > run a multiplatform kernel anyway. Also, the patch is really an ugly hack,
> > which is probably enough reason not to take it. ;-)
>
> Given that the omap patch has been accepted and that the patch is an
> "ugly hack", how hard it would be to provide a working patch for mvebu
> (well, orion usb driver) ?
The OMAP patch was accepted for 3.10, and I'm sure we will have good
patches for the other bus glues as well, but the bug is also present on
3.9, and the proper patches are too invasive now to get merged there.
> > platforms that are already working. Peter Robinson is doing this on for
> > Fedora right now[1] and I assume the Debian/Ubuntu/OpenSUSE/Gentoo
> > people will be in a similar situation, but they can all apply the
> > patch
>
> fwiw, I've mentionned this usb issue few days ago when talking about
> multiplatform on the debian-arm ml.
Yes, we've known about it for a long time, but failed to get the proper
patches out in time :(
> > manually if it doesn't make it into 3.9. It won't be the only patch they
>
> it can applied in the debian kernel, as long as the patch is merged
> upstream.
It won't be merged in 3.10, but in that case Debian can backport the proper
patches from 3.10.
Arnd
next prev parent reply other threads:[~2013-03-18 17:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 15:44 [RFC] USB: EHCI: hot-fix OMAP and Orion multiplatform config Arnd Bergmann
2013-03-15 16:07 ` Arnd Bergmann
2013-03-15 16:25 ` Alan Stern
2013-03-15 17:00 ` Arnd Bergmann
2013-03-15 17:40 ` Alan Stern
2013-03-15 20:11 ` Arnd Bergmann
2013-03-18 16:03 ` Alan Stern
2013-03-15 19:19 ` Alan Stern
2013-03-15 19:25 ` Greg Kroah-Hartman
2013-03-15 21:13 ` Arnd Bergmann
2013-03-16 0:09 ` Greg Kroah-Hartman
2013-03-18 15:45 ` Arnd Bergmann
2013-03-18 15:48 ` [PATCH v2] " Arnd Bergmann
2013-03-18 16:53 ` [RFC] " Arnaud Patard (Rtp)
2013-03-18 17:32 ` Arnd Bergmann [this message]
2013-03-15 20:15 ` Arnd Bergmann
2013-03-15 22:08 ` Sergei Shtylyov
2013-03-15 21:11 ` Arnd Bergmann
2013-03-15 22:24 ` Sergei Shtylyov
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=201303181732.18438.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).