2013/12/23 Marek Vasut :
> On Monday, December 23, 2013 at 01:50:36 AM, Kuo-Jung Su wrote:
>> 2013/12/20 Marek Vasut :
>> > On Friday, December 20, 2013 at 05:32:58 AM, Kuo-Jung Su wrote:
>> >> From: Kuo-Jung Su
>> >>
>> >> 1. It's known that EP0 fifo empty indication is not reliable, an extra
>>
On Monday, December 23, 2013 at 01:50:36 AM, Kuo-Jung Su wrote:
> 2013/12/20 Marek Vasut :
> > On Friday, December 20, 2013 at 05:32:58 AM, Kuo-Jung Su wrote:
> >> From: Kuo-Jung Su
> >>
> >> 1. It's known that EP0 fifo empty indication is not reliable, an extra
> >> delay is necessary to avoid d
2013/12/20 Marek Vasut :
> On Friday, December 20, 2013 at 05:32:58 AM, Kuo-Jung Su wrote:
>> From: Kuo-Jung Su
>>
>> 1. It's known that EP0 fifo empty indication is not reliable, an extra
>> delay is necessary to avoid data corruption while handling packets with
>> size greater than 64 bytes.
>>
On Friday, December 20, 2013 at 05:32:58 AM, Kuo-Jung Su wrote:
> From: Kuo-Jung Su
>
> 1. It's known that EP0 fifo empty indication is not reliable, an extra
> delay is necessary to avoid data corruption while handling packets with
> size greater than 64 bytes.
>
> 2. Since hardware revision 1.
From: Kuo-Jung Su
1. It's known that EP0 fifo empty indication is not reliable, an extra delay
is necessary to avoid data corruption while handling packets with size
greater than 64 bytes.
2. Since hardware revision 1.11.0, some fields of interrupt status registers
are now write-1-clear
5 matches
Mail list logo