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: <20200309124018.GA8942@lunn.ch>
Date:   Mon, 9 Mar 2020 13:40:18 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Russell King - ARM Linux admin <linux@...linux.org.uk>
Cc:     David Miller <davem@...emloft.net>, f.fainelli@...il.com,
        hkallweit1@...il.com, kuba@...nel.org, netdev@...r.kernel.org,
        vivien.didelot@...il.com
Subject: Re: [PATCH net-next 0/10] net: dsa: improve serdes integration

> Yep - it comes from the poor integration of phylink into DSA for CPU
> and inter-DSA ports which is already causing regressions in today's
> kernels. That needs resolving somehow before this patch series can
> be merged, but it isn't something that can be fixed from the phylink
> side of things.

Hi Russell

What do you think about my proposal to solve it? Only instantiate
phylink for CPU and DSA ports if there is a fixed-link or phy-handle
in DT?

I also looked at the code before this integration. I had the open
question of if it was possible to just have a phy-mode property,
without fixed link. And the answer is no.

So i will formally propose my solution.

   Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ