lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dfff1abf-f506-bffa-8e09-edeebd753be5@neratec.com>
Date:   Wed, 19 Oct 2016 10:55:02 +0200
From:   Zefir Kurtisi <zefir.kurtisi@...atec.com>
To:     Timur Tabi <timur@...eaurora.org>, Andrew Lunn <andrew@...n.ch>
Cc:     Florian Fainelli <f.fainelli@...il.com>, netdev@...r.kernel.org
Subject: Re: Need help with mdiobus_register and phy

On 10/18/2016 02:40 PM, Timur Tabi wrote:
> Zefir Kurtisi wrote:
> 
>>> I have never seen the original problem that you noticed.  When I use the generic
>>> phy driver instead of the at803x driver, everything works great for me.  Perhaps
>>> the problem that you noticed only occurs with the Gianfar NIC?
>>>
>> You mean it works for you in SGMII mode without glitches?
> 
> That is correct.
> 
>> Then it might in fact be
>> an unfortunate rare or unique combination that we chose.
> 
> That is what I expect.
> 
>> I'd need some time to get that tested, and since our device might be the only one
>> requiring the fix, I am fine with keeping the patch private. Feel free to revert
>> it, if required, I'll provide a revised one.
> 
> I'm in no hurry to get this fixed.  Do you need a couple weeks to run some tests? 
> It would be good to know for sure that your fix is needed only on your platform.
> 
Ok then, if you can wait some days, I'll prepare and provide you a more detailed
failure report to allow you testing if the issue happens with other NICs.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ