[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YIdqRlY+2iSqQ8lW@lunn.ch>
Date: Tue, 27 Apr 2021 03:35:02 +0200
From: Andrew Lunn <andrew@...n.ch>
To: 曹煜 <cao88yu@...il.com>
Cc: David Miller <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
Chris Packham <chris.packham@...iedtelesis.co.nz>,
Vivien Didelot <vivien.didelot@...il.com>
Subject: Re: [PATCH net] dsa: mv88e6xxx: 6161: Use chip wide MAX MTU
On Tue, Apr 27, 2021 at 08:18:00AM +0800, 曹煜 wrote:
> Hi Andrew,
> I'll test the patch later, but what about the 88e6171r switch chip,
> this chip also got this issue since kernel 5.9.0 Many thanks.
Saying the 6171 is wrong i have problems with.
The 6161 is part of the 6165 family, consisting of 6123, 6161 and
6165. The 6123 was already using mv88e6185_g1_set_max_frame_size, and
the documentation is ambiguous.
The 6171 is part of the 6351 family: 6171 6175 6350 6351. It is a
couple of generations newer, and all the other members of the family
also use mv88e6165_port_set_jumbo_size. I have the GPL licensed SDK
from Marvell. If i'm reading the SDK correctly, it has a function to
access the per port register for jumbo settings for the 6351 family.
Do you have a 6171 we can test code on?
Andrew
Powered by blists - more mailing lists