message: More explicit define about CAN protocols. 19/23219/6
authorRomain Forlot <romain.forlot@iot.bzh>
Wed, 20 Nov 2019 12:02:24 +0000 (13:02 +0100)
committerRomain Forlot <romain.forlot@iot.bzh>
Thu, 9 Jan 2020 14:55:03 +0000 (15:55 +0100)
commit779da0a54b29db5dd4c12387970026a264d2e6cb
treef15bc290e899682a0e2abfd2d7559b3d2cd499e1
parent5b9913d4d7fcf273380b2aeb780cf0a42cc99725
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.

Bug-AGL: SPEC-2988

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