Oliver Hartkopp 821047c405 can: remove CAN FD compatibility for CAN 2.0 sockets ... In commit e2d265d3b5 (canfd: add support for CAN FD in CAN_RAW sockets) CAN FD frames with a payload length up to 8 byte are passed to legacy sockets where the CAN FD support was not enabled by the application. After some discussions with developers at a fair this well meant feature leads to confusion as no clean switch for CAN / CAN FD is provided to the application programmer. Additionally a compatibility like this for legacy CAN_RAW sockets requires some compatibility handling for the sending, e.g. make CAN2.0 frames a CAN FD frame with BRS at transmission time (?!?). This will become a mess when people start to develop applications with real CAN FD hardware. This patch reverts the bad compatibility code together with the documentation describing the removed feature. Acked-by: Stephane Grosjean <s.grosjean@peak-system.com> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>		2014-03-03 14:29:52 +01:00
..
af_can.c	can: add destructor for self generated skbs	2014-01-30 16:25:49 -08:00
af_can.h	net: 8021q/bluetooth/bridge/can/ceph: Remove extern from function prototypes	2013-10-19 19:12:11 -04:00
bcm.c	can: add destructor for self generated skbs	2014-01-30 16:25:49 -08:00
gw.c	can: use __dev_get_by_index instead of dev_get_by_index to find interface	2014-01-14 18:50:47 -08:00
Kconfig
Makefile
proc.c
raw.c	can: remove CAN FD compatibility for CAN 2.0 sockets	2014-03-03 14:29:52 +01:00