[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200701041209.09081.arvidjaar@mail.ru>
Date: Thu, 4 Jan 2007 12:09:08 +0300
From: Andrey Borzenkov <arvidjaar@...l.ru>
To: David Brownell <david-b@...bell.net>
Cc: linux-usb-devel@...ts.sourceforge.net,
Alan Stern <stern@...land.harvard.edu>,
Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] OHCI: disallow autostop when wakeup is not available
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 04 January 2007 00:50, David Brownell wrote:
> On Tuesday 02 January 2007 7:16 am, Alan Stern wrote:
> > On Mon, 1 Jan 2007, Andrey Borzenkov wrote:
> > > Is the original problem (OHCI constantly attempting and failing to
> > > suspend root hub) supposed to be fixed in 2.6.20?
> >
> > No. It can't be fixed in the kernel because it is a hardware bug.
>
> I'm curious though: did older kernels, say 2.6.18, have such issues?
Yes. It is hardware problem all right.
[...]
>
> Not just that ... it also fixed the problem where quirk entries
> saying "don't even try using remote wakeup" stopped working.
>
Exactly. I am sorry for being unclear - actually the question was, whether
quirks are implemented in 2.6.20 (because I remember them being mentioned
before).
> Once some pending PPC-related OHCI patches merge (support for
> PS3 and other CELL systems), there will be infrastructure that
> makes it easier to add quirk entries that say "this board can't
> do remote wakeup properly". At that point, we can start to
> collect quirks for boards like this one.
>
OK so this answers the question - it is not yet being implemented.
thank you
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFnMQ1R6LMutpd94wRAqayAKDQrqfpERc4F5LjqWMQgI6oxqqOmACdH++H
r6aDgoAQDw2SHRq+2yLaoyw=
=95Oh
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists