[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <086a01d9ca8d$94387df0$bca979d0$@trustnetic.com>
Date: Wed, 9 Aug 2023 14:49:00 +0800
From: Jiawen Wu <jiawenwu@...stnetic.com>
To: "'Andrew Lunn'" <andrew@...n.ch>,
"'Russell King \(Oracle\)'" <linux@...linux.org.uk>
Cc: <netdev@...r.kernel.org>,
<davem@...emloft.net>,
<edumazet@...gle.com>,
<kuba@...nel.org>,
<pabeni@...hat.com>,
<hkallweit1@...il.com>,
<Jose.Abreu@...opsys.com>,
<mengyuanlou@...-swift.com>
Subject: RE: [PATCH net-next v2 1/7] net: pcs: xpcs: add specific vendor supoprt for Wangxun 10Gb NICs
On Wednesday, August 9, 2023 4:42 AM, Andrew Lunn wrote:
> > > > If the answer to that is yes, it would be preferable to use that
> > > > rather than adding a bitarray of flags to indicate various "quirks".
> > >
> > > It has not been implemented yet. We could implement it in flash if it's wanted.
> > > But it would require upgrading to the new firmware.
> >
> > Andrew, do you any opinions? Do you think it would be a good idea to
> > use the device/package identifiers, rather than a bitfield of quirks?
>
> Using identifiers would be cleaner.
>
> Does trustnetic or net-swift have an OUI?
Yes, net-swift's OUI is 30:09:F9.
But if we want to read OUI from PCS to identify the vendor, we need the
next version of firmware to do this. How can this be compatible with the
old firmware version?
Powered by blists - more mailing lists