> -Original Message-
> From: Florian Fainelli [mailto:f.faine...@gmail.com]
> Sent: Saturday, September 02, 2017 7:25 AM
> To: Bhadram Varka ; and...@lunn.ch
> Cc: linux-netdev
> Subject: Re: netdev carrier changes is one even after ethernet link up.
>
> On 08/3
Hi Florian,
> -Original Message-
> From: Florian Fainelli [mailto:f.faine...@gmail.com]
> Sent: Saturday, September 02, 2017 7:25 AM
> To: Bhadram Varka ; and...@lunn.ch
> Cc: linux-netdev
> Subject: Re: netdev carrier changes is one even after ethernet link up.
>
gt; Cc: linux-netdev
>> Subject: Re: netdev carrier changes is one even after ethernet link up.
>>
>> On 08/30/2017 10:53 PM, Bhadram Varka wrote:
>>> Hi,
>>>
>>>
>>>
>>> I have observed that carrier_changes is one even in case o
Thanks for responding. Now responding inline
> -Original Message-
> From: Florian Fainelli [mailto:f.faine...@gmail.com]
> Sent: Friday, September 01, 2017 5:53 AM
> To: Bhadram Varka ; and...@lunn.ch
> Cc: linux-netdev
> Subject: Re: netdev carrier changes is one e
Thanks for responding.
-Original Message-
From: Florian Fainelli [mailto:f.faine...@gmail.com]
Sent: Friday, September 01, 2017 5:53 AM
To: Bhadram Varka ; and...@lunn.ch
Cc: linux-netdev
Subject: Re: netdev carrier changes is one even after ethernet link up.
On 08/30/2017 10:53 PM
On 08/30/2017 10:53 PM, Bhadram Varka wrote:
> Hi,
>
>
>
> I have observed that carrier_changes is one even in case of the ethernet
> link is up.
>
>
>
> After investigating the code below is my observation –
>
>
>
> ethernet_driver_probe()
>
> +--->phy_connect()
>
> | +--->phy_at
+ netdev
From: Bhadram Varka
Sent: Thursday, August 31, 2017 11:24 AM
To: 'and...@lunn.ch' ; 'f.faine...@gmail.com'
Cc: linux-netdev
Subject: netdev carrier changes is one even after ethernet link up.
Hi,
I have observed that carrier_changes is one even in case of the ethernet link
is up.
