Commit 97edec3a authored Jun 02, 2017 by Oliver Hartkopp Committed by Marc Kleine-Budde Jun 09, 2017

can: enable CAN FD for virtual CAN devices by default

CAN FD capable CAN interfaces can handle (classic) CAN 2.0 frames too.
New users usually fail at their first attempt to explore CAN FD on
virtual CAN interfaces due to the current CAN_MTU default.

Set the MTU to CANFD_MTU by default to reduce this confusion.
If someone *really* needs a 'classic CAN'-only device this can be set
with the 'ip' tool with e.g. 'ip link set vcan0 mtu 16' as before.

Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

parent 74b7b490

drivers/net/can/vcan.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -152,7 +152,7 @@ static const struct net_device_ops vcan_netdev_ops = {
		static void vcan_setup(struct net_device *dev)
		{
		dev->type = ARPHRD_CAN;
		dev->mtu = CAN_MTU;
		dev->mtu = CANFD_MTU;
		dev->hard_header_len = 0;
		dev->addr_len = 0;
		dev->tx_queue_len = 0;

drivers/net/can/vxcan.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -150,7 +150,7 @@ static const struct net_device_ops vxcan_netdev_ops = {
		static void vxcan_setup(struct net_device *dev)
		{
		dev->type = ARPHRD_CAN;
		dev->mtu = CAN_MTU;
		dev->mtu = CANFD_MTU;
		dev->hard_header_len = 0;
		dev->addr_len = 0;
		dev->tx_queue_len = 0;

Admin message