linux-kernel - Re: [PATCH net-next v2 5/5] net: phy: add driver for built-in 2.5G ethernet PHY on MT7988

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: Mon, 20 May 2024 15:02:21 +0200
From: Andrew Lunn <andrew@...n.ch>
To: SkyLake Huang (黃啟澤) <SkyLake.Huang@...iatek.com>
Cc: "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-mediatek@...ts.infradead.org" <linux-mediatek@...ts.infradead.org>,
	"linux@...linux.org.uk" <linux@...linux.org.uk>,
	"kuba@...nel.org" <kuba@...nel.org>,
	"pabeni@...hat.com" <pabeni@...hat.com>,
	"edumazet@...gle.com" <edumazet@...gle.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"dqfext@...il.com" <dqfext@...il.com>,
	Steven Liu (劉人豪) <steven.liu@...iatek.com>,
	"matthias.bgg@...il.com" <matthias.bgg@...il.com>,
	"davem@...emloft.net" <davem@...emloft.net>,
	"hkallweit1@...il.com" <hkallweit1@...il.com>,
	"daniel@...rotopia.org" <daniel@...rotopia.org>,
	"angelogioacchino.delregno@...labora.com" <angelogioacchino.delregno@...labora.com>
Subject: Re: [PATCH net-next v2 5/5] net: phy: add driver for built-in 2.5G
 ethernet PHY on MT7988

> > Is there a version available anywhere for the firmware?
> > 
> Currently, I use "$md5sum /lib/firmware/mediatek/mt7988/i2p5ge-phy-
> pmb.bin" command to check version.

An md5sum is not really a version. How do you tell if one md5sum is
newer or older than another?

Is there is an MDIO register you can read to get the version? Or a
version in a header in the firmware file?

> > > +static int mt798x_2p5ge_phy_get_features(struct phy_device
> > *phydev)
> > > +{
> > > +int ret;
> > > +
> > > +ret = genphy_c45_pma_read_abilities(phydev);
> > > +if (ret)
> > > +return ret;
> > > +
> > > +/* We don't support HDX at MAC layer on mt7988.
> > 
> > That is a MAC limitation, so it should be the MAC which disables
> > this,
> > not the Phy.
> > 
> Actually this phy is strictly binded to (XFI)MAC on this platform.
> So I directly disable HDX feature of PHY.

Sorry, i don't follow your answer:

Can the PHY do half duplex?
Can the MAC do half duplex?

The part which cannot do half-duplex should be the part which disables
half-duplex.

You should be able to take any vendors MAC and any vendors PHY and put
them together, if they have the same MII interface. Say this PHY does
support half duplex. And some other vendors MAC supports half
duplex. We want it to work.

	Andrew