Mason writes:
> One thing I find confusing... If the 8035 could work with the generic
> PHY driver, what's the point of the at803x.ko driver?
Almost all Ethernet PHYs support the basic operation defined the by the
standard. Many have additional non-standardised features that require a
specific
On 01/19/2017 09:56 AM, Måns Rullgård wrote:
> Mason writes:
>
>> One thing I find confusing... If the 8035 could work with the generic
>> PHY driver, what's the point of the at803x.ko driver?
>
> Almost all Ethernet PHYs support the basic operation defined the by the
> standard. Many have addi
On 18/01/2017 11:29, Zefir Kurtisi wrote:
> On 01/13/2017 06:35 PM, Mason wrote:
>> On 13/01/2017 17:28, Zefir Kurtisi wrote:
>>
>>> As for your specific problem: since I fought myself with the PHY/ETH
>>> subsystems
>>> over the past months, I might remember something relevant to your issue.
>>>
On 01/13/2017 06:35 PM, Mason wrote:
> On 13/01/2017 17:28, Zefir Kurtisi wrote:
>
>> As for your specific problem: since I fought myself with the PHY/ETH
>> subsystems
>> over the past months, I might remember something relevant to your issue.
>> Could you
>> give some more info on your setup (
On 13/01/2017 17:28, Zefir Kurtisi wrote:
> As for your specific problem: since I fought myself with the PHY/ETH
> subsystems
> over the past months, I might remember something relevant to your issue.
> Could you
> give some more info on your setup (PHY driver, opmode (SGMII, RGMII, etc.),
> ET
On 01/13/2017 04:17 PM, Mason wrote:
> On 13/01/2017 10:20, Zefir Kurtisi wrote:
>> On 01/12/2017 04:16 PM, Mason wrote:
>>> On 12/01/2017 14:05, Mason wrote:
>>>
I'm wondering what are the semantics of calling
ip link set dev eth0 down
I was expecting that to somehow in
On 13/01/2017 10:20, Zefir Kurtisi wrote:
> On 01/12/2017 04:16 PM, Mason wrote:
>> On 12/01/2017 14:05, Mason wrote:
>>
>>> I'm wondering what are the semantics of calling
>>>
>>> ip link set dev eth0 down
>>>
>>> I was expecting that to somehow instruct the device's ethernet driver
>>> to shu
On 01/12/2017 04:16 PM, Mason wrote:
> On 12/01/2017 14:05, Mason wrote:
>
>> I'm wondering what are the semantics of calling
>>
>> ip link set dev eth0 down
>>
>> I was expecting that to somehow instruct the device's ethernet driver
>> to shut everything down, have the PHY tell the peer that
On Thu, 2017-01-12 at 16:28 +0100, Andrew Lunn wrote:
> > Here's an example of "Link is Down" printed when I set link up:
> >
> > At [ 62.750220] I run ip link set dev eth0 down
> > Then leave the system idle for 10 minutes.
> > At [ 646.263041] I run ip link set dev eth0 up
> > At [ 647.36407
> Whatever the reason for the symptoms I'm seeing, some kind of race
> condition must be involved, because it occurs randomly.
The PHY is polled once a second for its status. So it would depend on
who fast autoneg happens if you see the down.
Andrew
On 12/01/2017 16:28, Andrew Lunn wrote:
> Mason wrote:
>
>> Here's an example of "Link is Down" printed when I set link up:
>>
>> At [ 62.750220] I run ip link set dev eth0 down
>> Then leave the system idle for 10 minutes.
>> At [ 646.263041] I run ip link set dev eth0 up
>> At [ 647.364079]
> Here's an example of "Link is Down" printed when I set link up:
>
> At [ 62.750220] I run ip link set dev eth0 down
> Then leave the system idle for 10 minutes.
> At [ 646.263041] I run ip link set dev eth0 up
> At [ 647.364079] it prints "Link is Down"
> At [ 649.417434] it prints "Link is
On 12/01/2017 14:05, Mason wrote:
> I'm wondering what are the semantics of calling
>
> ip link set dev eth0 down
>
> I was expecting that to somehow instruct the device's ethernet driver
> to shut everything down, have the PHY tell the peer that it's going
> away, maybe even put the PHY i
Hello,
I'm wondering what are the semantics of calling
ip link set dev eth0 down
I was expecting that to somehow instruct the device's ethernet driver
to shut everything down, have the PHY tell the peer that it's going
away, maybe even put the PHY in some low-power mode, etc.
But it doe
14 matches
Mail list logo
