Re: [PATCH net-next 5/5 v2] net: gemini: Indicate that we can handle jumboframes

2018-07-11 Thread Linus Walleij
On Wed, Jul 4, 2018 at 10:35 PM Andrew Lunn wrote: > > On Wed, Jul 04, 2018 at 08:33:24PM +0200, Linus Walleij wrote: > > The hardware supposedly handles frames up to 10236 bytes and > > implements .ndo_change_mtu() so accept 10236 minus the ethernet > > header for a VLAN tagged frame on the

Re: [PATCH net-next 5/5 v2] net: gemini: Indicate that we can handle jumboframes

2018-07-04 Thread Andrew Lunn
On Wed, Jul 04, 2018 at 08:33:24PM +0200, Linus Walleij wrote: > The hardware supposedly handles frames up to 10236 bytes and > implements .ndo_change_mtu() so accept 10236 minus the ethernet > header for a VLAN tagged frame on the netdevices. Use > ETH_MIN_MTU as minimum MTU. > > Signed-off-by:

[PATCH net-next 5/5 v2] net: gemini: Indicate that we can handle jumboframes

2018-07-04 Thread Linus Walleij
The hardware supposedly handles frames up to 10236 bytes and implements .ndo_change_mtu() so accept 10236 minus the ethernet header for a VLAN tagged frame on the netdevices. Use ETH_MIN_MTU as minimum MTU. Signed-off-by: Linus Walleij --- ChangeLog v1->v2: - Change the min MTU from 256 (vendor