From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linuxppc-dev@ozlabs.org, USB list <linux-usb@vger.kernel.org>,
abhishekkumar <abhishekkumar@tataelxsi.co.in>,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 13304] New: ehci_hcd module causing problems in using usb head phone
Date: Fri, 26 Jun 2009 15:05:10 -0700 [thread overview]
Message-ID: <4A454616.7040501@am.sony.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0906261638370.4155-100000@iolanthe.rowland.org>
On 06/26/2009 01:42 PM, Alan Stern wrote:
> On Fri, 26 Jun 2009, Geoff Levand wrote:
>
>> There is a known but yet unfixed bug for the PS3's EHCI Async Periodic
>> (typically audio recording) device handling. There are a few related
>> hardware errata that I have not yet implemented driver fixes for that
>> I think are causing it.
>>
>> I guess it is the same problem as reported by Abhishek since Andrew's
>> dmesg (http://www.osl.iu.edu/~afriedle/dmesg.txt) shows similar
>> results.
>
> Yes, it definitely looks the same.
>
>> More info is here:
>>
>> http://ozlabs.org/pipermail/cbe-oss-dev/2009-February/006365.html
>>
>> I have bought a ART Tube USB device but have not had time to fix
>> this bug. It is on my todo list. Please feel free to make an
>> attempt.
>
> Where is the information about the hardware errata you mentioned?
Sorry, I should have mentioned it. Unfortunately, that info is not
in the public as far as I know. I think only someone with access
to those will be able to work on this fix.
-Geoff
next prev parent reply other threads:[~2009-06-26 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A44CB89.8040802@tataelxsi.co.in>
2009-06-26 15:54 ` [Bugme-new] [Bug 13304] New: ehci_hcd module causing problems in using usb head phone Alan Stern
2009-06-26 17:14 ` Geoff Levand
2009-06-26 20:42 ` Alan Stern
2009-06-26 22:05 ` Geoff Levand [this message]
2009-06-27 1:33 ` Alan Stern
2009-06-29 16:07 ` Geoff Levand
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=4A454616.7040501@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=abhishekkumar@tataelxsi.co.in \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--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.