[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240615103038.973-1-paul.barker.ct@bp.renesas.com>
Date: Sat, 15 Jun 2024 11:30:36 +0100
From: Paul Barker <paul.barker.ct@...renesas.com>
To: Sergey Shtylyov <s.shtylyov@....ru>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Niklas Söderlund <niklas.soderlund+renesas@...natech.se>
Cc: Paul Barker <paul.barker.ct@...renesas.com>,
Biju Das <biju.das.jz@...renesas.com>,
Claudiu Beznea <claudiu.beznea.uj@...renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
Mitsuhiro Kimura <mitsuhiro.kimura.kc@...esas.com>,
netdev@...r.kernel.org,
linux-renesas-soc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [net-next PATCH 0/2] Fix maximum TX/RX frame sizes in ravb driver
These patches fix a couple of bugs in the maximum supported TX/RX frame sizes
in the ravb driver.
* For the GbEth IP, we were advertising a maximum TX frame size/MTU that was
larger that the maximum the hardware can transmit.
* For the R-Car AVB IP, we were unnecessarily setting the maximum RX frame
size/MRU based on the MTU, which by default is smaller than the maximum the
hardware can receive.
Paul Barker (2):
net: ravb: Fix maximum MTU for GbEth devices
net: ravb: Set R-Car RX frame size limit correctly
drivers/net/ethernet/renesas/ravb.h | 1 +
drivers/net/ethernet/renesas/ravb_main.c | 10 ++++++++--
2 files changed, 9 insertions(+), 2 deletions(-)
base-commit: 934c29999b57b835d65442da6f741d5e27f3b584
--
2.39.2
Powered by blists - more mailing lists