[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6e8034d9-cd60-2846-ef33-f8a04069e1ee@huawei.com>
Date: Sat, 5 Jan 2019 11:28:19 +0800
From: Yunsheng Lin <linyunsheng@...wei.com>
To: Russell King - ARM Linux <linux@...linux.org.uk>
CC: Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Weiwei Deng <dengweiwei@...wei.com>,
"Yisen.Zhuang@...wei.com" <Yisen.Zhuang@...wei.com>,
"huangdaode@...ilicon.com" <huangdaode@...ilicon.com>,
"lipeng321@...wei.com" <lipeng321@...wei.com>,
"salil.mehta@...wei.com" <salil.mehta@...wei.com>,
lijianhua 00216010 <lijianhua@...wei.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Question: pause mode disabled for marvell 88e151x phy
On 2018/12/17 22:36, Russell King - ARM Linux wrote:
> I'll try to do further diagnosis over Christmas in case I've missed
> something, but I suspect it may be one of those "weird behaviour" issues
> where the safest action is to disable pause mode as per my commit -
> which is far saner than having mismatched pause status on either end
> of a link. However, given that Marvell specs are all NDA-only, it's
> very difficult to investigate beyond "this is the observed behaviour".
Hi,
Is there any update on the further diagnosis?
>
Powered by blists - more mailing lists