netdev - RE: [PATCH 1/6] net: phy: add interface modes for XFI, SFI

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]

Date:   Fri, 20 Dec 2019 09:39:08 +0000
From:   "Madalin Bucur (OSS)" <madalin.bucur@....nxp.com>
To:     Andrew Lunn <andrew@...n.ch>,
        Russell King - ARM Linux admin <linux@...linux.org.uk>
CC:     "Madalin Bucur (OSS)" <madalin.bucur@....nxp.com>,
        "antoine.tenart@...e-electrons.com" 
        <antoine.tenart@...e-electrons.com>,
        "jaz@...ihalf.com" <jaz@...ihalf.com>,
        "baruch@...s.co.il" <baruch@...s.co.il>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "f.fainelli@...il.com" <f.fainelli@...il.com>,
        "hkallweit1@...il.com" <hkallweit1@...il.com>,
        "shawnguo@...nel.org" <shawnguo@...nel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: RE: [PATCH 1/6] net: phy: add interface modes for XFI, SFI

> -----Original Message-----
> From: Andrew Lunn <andrew@...n.ch>
> Sent: Friday, December 20, 2019 11:29 AM
> To: Russell King - ARM Linux admin <linux@...linux.org.uk>
> Cc: Madalin Bucur (OSS) <madalin.bucur@....nxp.com>; antoine.tenart@...e-
> electrons.com; jaz@...ihalf.com; baruch@...s.co.il; davem@...emloft.net;
> netdev@...r.kernel.org; f.fainelli@...il.com; hkallweit1@...il.com;
> shawnguo@...nel.org; devicetree@...r.kernel.org
> Subject: Re: [PATCH 1/6] net: phy: add interface modes for XFI, SFI
> 
> > How does this help us when we can't simply change the existing usage?
> > We can update the DT but we can't free up the usage of "10gbase-kr".
> 
> Agreed. Code needs to keep on interpreting "10gbase-kr" as any 10G
> link. If we ever have a true 10gbase-kr, 802.3ap, one meter of copper
> and two connectors, we are going to have to add a new mode to
> represent true 10gbase-kr.
> 
> 	Andrew

Hi, actually we do have that. What would be the name of the new mode
representing true 10GBase-KR that we will need to add when we upstream
support for that?

Thanks,
Madalin