message: More explicit define about CAN protocols.
authorRomain Forlot <romain.forlot@iot.bzh>
Wed, 20 Nov 2019 12:02:24 +0000 (13:02 +0100)
committerRomain Forlot <romain.forlot@iot.bzh>
Tue, 3 Dec 2019 18:46:26 +0000 (19:46 +0100)
commit7eb266ac372a3ccfc0857a6a63d9f6c88afa1ffd
treed572278bab152ebf7f6681034cd1e8124f976e3c
parentabd185676c3ace3c7d6427e1a1cf4964a4edae1b
message: More explicit define about CAN protocols.

Change a bit CAN binding define about used protocol. There was a mistake
about BCM define which isn't a protocol at all but a maner to filter
and retrieve CAN message through SocketCAN. Also FD_FRAME was using the
same name than SocketCAN which isn't a good idea, better to distinguis both
of them.

Change-Id: I255fa03029c7d5f90a33448e5e7692d8c249279b
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
low-can-binding/binding/low-can-cb.cpp
low-can-binding/binding/low-can-subscription.cpp
low-can-binding/can/message-definition.cpp
low-can-binding/can/message/message.hpp