diff options
| author | Oliver Hartkopp <[email protected]> | 2014-03-01 14:31:53 +0000 |
|---|---|---|
| committer | Marc Kleine-Budde <[email protected]> | 2014-03-03 13:29:52 +0000 |
| commit | 821047c4055cca833c4674f172a9d73003563eb6 (patch) | |
| tree | 28246c9f50757df9ea1efcad0c8210f098aa1c14 /net/unix/af_unix.c | |
| parent | can: flexcan: factor out soft reset into seperate funtion (diff) | |
| download | kernel-821047c4055cca833c4674f172a9d73003563eb6.tar.gz kernel-821047c4055cca833c4674f172a9d73003563eb6.zip | |
can: remove CAN FD compatibility for CAN 2.0 sockets
In commit e2d265d3b587 (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 <[email protected]>
Signed-off-by: Oliver Hartkopp <[email protected]>
Signed-off-by: Marc Kleine-Budde <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions