Hi Matthias,
On Wed, 18 Jan 2012 14:42:20 +0100
Matthias Fuchs wrote:
...
> > Can you try the attached patch? Does it have an impact?
>
> Yes, in deed, it solved my problem :-) Finally I noticed that
> the problem is listed in the CPU's errata document.
>
> You could update the comment and comm
Hi Anatolij,
On 18.01.2012 12:08, Anatolij Gustschin wrote:
> Hi Matthias,
>
> On Tue, 17 Jan 2012 15:12:50 +0100
> Matthias Fuchs wrote:
>
>> On 06.01.2012 19:03, Alan Stern wrote:
>>> On Fri, 6 Jan 2012, Matthias Fuchs wrote:
>>>
For my eyes it does not really look like a general USB iss
Hi Matthias,
On Tue, 17 Jan 2012 15:12:50 +0100
Matthias Fuchs wrote:
> On 06.01.2012 19:03, Alan Stern wrote:
> > On Fri, 6 Jan 2012, Matthias Fuchs wrote:
> >
> >> For my eyes it does not really look like a general USB issue.
> >> It looks like a problem with the Freescale EHCI implementation
On 06.01.2012 19:03, Alan Stern wrote:
> On Fri, 6 Jan 2012, Matthias Fuchs wrote:
>
>> For my eyes it does not really look like a general USB issue.
>> It looks like a problem with the Freescale EHCI implementation that is
>> influenced by high interrupt or internal bus load caused by the flood p
On Fri, 6 Jan 2012, Matthias Fuchs wrote:
> For my eyes it does not really look like a general USB issue.
> It looks like a problem with the Freescale EHCI implementation that is
> influenced by high interrupt or internal bus load caused by the flood ping.
Indeed, it might be a problem with the b
On 22.12.2011 18:39, Greg KH wrote:
> On Thu, Dec 22, 2011 at 12:48:45PM +0100, Matthias Fuchs wrote:
>> Hi,
>>
>> I ran into trouble when using the MPC5121 with full speed
>> USB devices. I've seen the issue with USB serial converters
>> based on FTDI and Prolific chips.
>>
>> After connecting the
