From: Andrew Lunn <andrew@lunn.ch>
To: 曹煜 <cao88yu@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: [PATCH net] dsa: mv88e6xxx: 6161: Use chip wide MAX MTU
Date: Tue, 27 Apr 2021 03:35:02 +0200 [thread overview]
Message-ID: <YIdqRlY+2iSqQ8lW@lunn.ch> (raw)
In-Reply-To: <CACu-5+0bnMJPOUZHKfSTEQiFgAVX9kjbgTTQtqLDT57yv0MDHQ@mail.gmail.com>
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
next prev parent reply other threads:[~2021-04-27 1:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 23:34 [PATCH net] dsa: mv88e6xxx: 6161: Use chip wide MAX MTU Andrew Lunn
2021-04-26 23:36 ` Andrew Lunn
2021-04-27 0:18 ` 曹煜
2021-04-27 1:35 ` Andrew Lunn [this message]
2021-04-30 14:01 ` Andrew Lunn
2021-05-03 2:38 ` Chris Packham
2021-05-03 12:16 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YIdqRlY+2iSqQ8lW@lunn.ch \
--to=andrew@lunn.ch \
--cc=cao88yu@gmail.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).