[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2phohBqYR5juqBn@lunn.ch>
Date: Tue, 8 Nov 2022 15:03:14 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Lukasz Majewski <lukma@...x.de>
Cc: Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org
Subject: Re: [PATCH 9/9] net: dsa: mv88e6071: Set .set_max_frame_size callback
On Tue, Nov 08, 2022 at 09:23:30AM +0100, Lukasz Majewski wrote:
> The .set_max_frame_size is now set to the
> mv88e6185_g1_set_max_frame_size() function.
>
> The global switch control register (0x4 offset) used
> as well as the bit (10) are the same.
>
> The only difference is the misleading suffix (1632)
> as the mv88e6071/mv88e6020 supports 2048 bytes
> as a maximal size of the frame.
Are you really sure that different members of the 6250 family have
different maximum frame sizes?
Marvells GPL DSDT SDK has:
#define G1_DEV_88ESPANNAK_FAMILY (DEV_88E3020 | DEV_88E6020 | DEV_88E6070 | DEV_88E6071 | DEV_88E6220 | DEV_88E6250 )
The differences within a family tend to be the number of ports, if PTP
is provided, if AVB is provided etc.
Andrew
Powered by blists - more mailing lists