From 779da0a54b29db5dd4c12387970026a264d2e6cb Mon Sep 17 00:00:00 2001 From: Romain Forlot Date: Wed, 20 Nov 2019 13:02:24 +0100 Subject: 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 --- low-can-binding/can/message/message.hpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'low-can-binding/can/message/message.hpp') diff --git a/low-can-binding/can/message/message.hpp b/low-can-binding/can/message/message.hpp index 7f13ac47..af34615a 100644 --- a/low-can-binding/can/message/message.hpp +++ b/low-can-binding/can/message/message.hpp @@ -37,13 +37,13 @@ */ #define INVALID_FLAG 0x0001 -#define BCM_PROTOCOL 0x0002 +#define CAN_PROTOCOL 0x0002 #define J1939_PROTOCOL 0x0004 #define J1939_ADDR_CLAIM_PROTOCOL 0x0008 #define ISOTP_PROTOCOL 0x0010 #define ISOTP_SEND 0x0020 #define ISOTP_RECEIVE 0x0040 -#define FD_FRAME 0x0080 +#define CAN_PROTOCOL_WITH_FD_FRAME 0x0080 /// @class message_t /// -- cgit 1.2.3-korg