[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <187506b6-f6a1-4e50-b287-f01984c1e334@lunn.ch>
Date: Sat, 12 Aug 2023 16:19:44 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Florian Fainelli <florian.fainelli@...adcom.com>
Cc: Giulio Benetti <giulio.benetti@...ettiengineering.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@...adcom.com>,
Heiner Kallweit <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Russell King <linux@...linux.org.uk>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, Jim Reinhart <jimr@...vox.com>,
James Autry <jautry@...vox.com>,
Matthew Maron <matthewm@...vox.com>
Subject: Re: [PATCH] net: phy: broadcom: add support for BCM5221 phy
> > This table has some sort of sorting. I would put this new entry before
> > PHY_ID_BCM5241.
> >
> > > #define PHY_ID_BCM50610 0x0143bd60
> > > #define PHY_ID_BCM50610M 0x0143bd70
> > > #define PHY_ID_BCM5241 0x0143bc30
> > > +#define PHY_ID_BCM5221 0x004061e0
> >
> > The value looks odd. Is the OUI correct? Is that a broadcom OUI?
>
> Yes it is correct and yes it is assigned to Broadcom.
I found a datasheet for this PHY and it does list this OUI. I just
noticed it is the only device supported by this driver which uses this
OUI, so i just wanted to check.
Andrew
Powered by blists - more mailing lists