From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
hkallweit1@gmail.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: Synchronize c45_ids to phy_id
Date: Sat, 24 May 2025 01:36:16 +0000 [thread overview]
Message-ID: <4c14bb4887acf67ec5a4893c8e3f736c2a77a4a3@linux.dev> (raw)
In-Reply-To: <aDCyQOdcREDJTa-V@shell.armlinux.org.uk>
May 24, 2025 at 1:37 AM, "Russell King (Oracle)" <linux@armlinux.org.uk> wrote:
>
> On Fri, May 23, 2025 at 02:10:00AM +0000, Yajun Deng wrote:
>
> >
> > I noticed that. I tested the BCM89890, 88X3310 and 88Q2110 PHY devices,
> >
> > and the ID is always the same in different MMDs.
> >
>
> The 88x3310 PHY uses:
>
> Device ID Package ID OUI
>
> MMD 1: 0x002b09aa 0x002b09aa 00:0a:c2
>
> MMD 3: 0x002b09aa 0x002b09aa 00:0a:c2
>
> MMD 4: 0x01410daa 0x01410daa 00:50:43
>
> MMD 7: 0x002b09aa 0x002b09aa 00:0a:c2
>
> other MMDs do not contain an ID.
>
> According to https://hwaddress.com/oui-iab/00-0A-C2/, 00:0a:c2 is/was
>
> Wuhan FiberHome Digital Technology Co.
>
> 00:50:43 is Marvell Semiconductor.
>
> Not all PHYs have a single ID. IEEE 802.3 allows for this.
>
Okay, thank you. I'll add the c45_ids entry for the c45 device.
> --
>
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
>
> FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
>
next prev parent reply other threads:[~2025-05-24 1:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 13:19 [PATCH net-next] net: phy: Synchronize c45_ids to phy_id Yajun Deng
2025-05-22 13:26 ` Russell King (Oracle)
2025-05-22 13:39 ` Andrew Lunn
2025-05-23 2:10 ` Yajun Deng
2025-05-23 13:03 ` Andrew Lunn
2025-05-23 17:39 ` Russell King (Oracle)
2025-05-23 17:37 ` Russell King (Oracle)
2025-05-24 1:36 ` Yajun Deng [this message]
2025-05-28 6:35 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c14bb4887acf67ec5a4893c8e3f736c2a77a4a3@linux.dev \
--to=yajun.deng@linux.dev \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).