Revert accessing CAN device with a map indexing on dev name
authorRomain Forlot <romain.forlot@iot.bzh>
Wed, 15 Mar 2017 12:04:42 +0000 (13:04 +0100)
committerRomain Forlot <romain.forlot@iot.bzh>
Thu, 16 Mar 2017 16:21:57 +0000 (17:21 +0100)
commit1d464d2a7380248b04c3e734ed5c6e84bbf53ddf
treec75ef10c1a45477f4597e4edd97d0a7fc16a4447
parent56c22348d3af944b68bc7395553b9f8b1a817ba6
Revert accessing CAN device with a map indexing on dev name

Main reason for that behavior revert is because of generator that rely
on CAN device name and so we have point on these object by specify the
device name.

Instead of shared pointer between objects, instead binding is based on
device name. With a device name you can get the shared pointer on it using
new static method from can_bus_t object.

Change-Id: I331e0ad8d03c88a15c697d12a9fce3699b0cd962
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
13 files changed:
src/can/can-bus.cpp
src/can/can-bus.hpp
src/can/can-message-definition.cpp
src/can/can-message-definition.hpp
src/can/can-message.cpp
src/configuration-generated.cpp
src/configuration.cpp
src/configuration.hpp
src/diagnostic/active-diagnostic-request.cpp
src/diagnostic/active-diagnostic-request.hpp
src/diagnostic/diagnostic-manager.cpp
src/diagnostic/diagnostic-manager.hpp
src/low-can-binding.cpp