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  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:   Tue, 24 Jan 2017 21:28:47 +0100
From:   Andrew Lunn <>
To:     Gregory CLEMENT <>
Cc:     Vivien Didelot <>,
        Florian Fainelli <>,,,
        "David S. Miller" <>,
        Jason Cooper <>,
        Sebastian Hesselbarth <>,
        Thomas Petazzoni <>,,
        Nadav Haklai <>,
        Wilson Ding <>,
        Kostya Porotchkin <>,
        Joe Zhou <>,
        Jon Pannell <>
Subject: Re: [PATCH net-next v6 4/4] phy: marvell: Add support for the PHY
 embedded in the topaz switch

On Tue, Jan 24, 2017 at 09:10:26PM +0100, Gregory CLEMENT wrote:
> The PHY with the ID 0x1410C00


I don't have a better reference, but
Linux/Documentation/devicetree/bindings/net/phy.txt says:

 22   If the phy's identifier is known then the list may contain an entry
 23   of the form: "ethernet-phy-idAAAA.BBBB" where
 24      AAAA - The value of the 16 bit Phy Identifier 1 register as
 25             4 hex digits. This is the chip vendor OUI bits 3:18
 26      BBBB - The value of the 16 bit Phy Identifier 2 register as
 27             4 hex digits. This is the chip vendor OUI bits 19:24,
 28             followed by 10 bits of a vendor specific ID.

So the lower 10 bits of 0x1410C00 are 0. So we know it is a Marvell
PHY from the OUI, but the vendor specific bits are all 0.

Please take a look at:


Maybe i should submit these two independently, so you can extend it
for the 88E6341 family.


Powered by blists - more mailing lists