[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <GV1P190MB201956D5D1C194DC1264CCA9E48B9@GV1P190MB2019.EURP190.PROD.OUTLOOK.COM>
Date: Fri, 15 Jul 2022 09:35:40 +0000
From: Oleksandr Mazur <oleksandr.mazur@...ision.eu>
To: Andrew Lunn <andrew@...n.ch>,
"Russell King (Oracle)" <linux@...linux.org.uk>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
Yevhen Orlov <yevhen.orlov@...ision.eu>,
Taras Chornyi <taras.chornyi@...ision.eu>
Subject: Re: [PATCH V2 net-next] net: marvell: prestera: add phylink support
Hello Andrew,
>And also think about forward/backward compatibility. At some point
>your FW will support it. Do you need to do anything now in order to
>smoothly add support for it in the future?
thanks for the comment, that's a good point;
We currently have AN restart HW API call, you are right, however whenever we add AN restart support for 1000basex,
we won't change the ABI nature of HW API calls between FW and Driver.
So yes, the transition for adding 1000basex AN restart functionality would be indeed smooth without ABI changes.
Powered by blists - more mailing lists