| Message ID | 20240615103038.973-1-paul.barker.ct@bp.renesas.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | Fix maximum TX/RX frame sizes in ravb driver | expand |
On 6/15/24 1:30 PM, Paul Barker wrote: > 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 > DaveM & Co, I'm planning to review these patches on Monday evening... MBR, Sergey
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