On 07/03/2017 04:53 PM, Ivan Khoronzhuk wrote:
> On Mon, Jul 03, 2017 at 02:31:06PM -0500, Grygorii Strashko wrote:
>>
>>
>> On 06/30/2017 08:31 PM, Ivan Khoronzhuk wrote:
>>> On Tue, Jun 13, 2017 at 06:16:21PM -0500, Grygorii Strashko wrote:
There are two reasons for this change:
1) en
On Mon, Jul 03, 2017 at 02:31:06PM -0500, Grygorii Strashko wrote:
>
>
> On 06/30/2017 08:31 PM, Ivan Khoronzhuk wrote:
> > On Tue, Jun 13, 2017 at 06:16:21PM -0500, Grygorii Strashko wrote:
> >> There are two reasons for this change:
> >> 1) enabling of HW_TS_PUSH events as suggested by Richard
On 06/30/2017 08:31 PM, Ivan Khoronzhuk wrote:
> On Tue, Jun 13, 2017 at 06:16:21PM -0500, Grygorii Strashko wrote:
>> There are two reasons for this change:
>> 1) enabling of HW_TS_PUSH events as suggested by Richard Cochran and
>> discussed in [1]
>> 2) fixing an TX timestamping miss issue whic
On Tue, Jun 13, 2017 at 06:16:21PM -0500, Grygorii Strashko wrote:
> There are two reasons for this change:
> 1) enabling of HW_TS_PUSH events as suggested by Richard Cochran and
> discussed in [1]
> 2) fixing an TX timestamping miss issue which happens with low speed
> ethernet connections and was
There are two reasons for this change:
1) enabling of HW_TS_PUSH events as suggested by Richard Cochran and
discussed in [1]
2) fixing an TX timestamping miss issue which happens with low speed
ethernet connections and was reproduced on am57xx and am335x boards.
Issue description: With the low Ethe
