summaryrefslogtreecommitdiffstats
path: root/low-can-binding/can/message-definition.cpp
diff options
context:
space:
mode:
authorRomain Forlot <romain.forlot@iot.bzh>2019-11-20 13:02:24 +0100
committerRomain Forlot <romain.forlot@iot.bzh>2020-01-09 15:55:03 +0100
commit779da0a54b29db5dd4c12387970026a264d2e6cb (patch)
treef15bc290e899682a0e2abfd2d7559b3d2cd499e1 /low-can-binding/can/message-definition.cpp
parent5b9913d4d7fcf273380b2aeb780cf0a42cc99725 (diff)
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>
Diffstat (limited to 'low-can-binding/can/message-definition.cpp')
-rw-r--r--low-can-binding/can/message-definition.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/low-can-binding/can/message-definition.cpp b/low-can-binding/can/message-definition.cpp
index 80609827..63541277 100644
--- a/low-can-binding/can/message-definition.cpp
+++ b/low-can-binding/can/message-definition.cpp
@@ -79,12 +79,12 @@ uint32_t message_definition_t::get_id() const
bool message_definition_t::is_fd() const
{
- return (flags_&FD_FRAME);
+ return (flags_ & CAN_PROTOCOL_WITH_FD_FRAME);
}
bool message_definition_t::is_j1939() const
{
- return (flags_&J1939_PROTOCOL);
+ return (flags_ & J1939_PROTOCOL);
}
bool message_definition_t::is_isotp() const