diff options
author | Scott Murray <scott.murray@konsulko.com> | 2021-01-06 18:30:03 -0500 |
---|---|---|
committer | Scott Murray <scott.murray@konsulko.com> | 2021-01-12 23:07:09 +0000 |
commit | 96c3e18cf1f7ac1da8371e8ca84400d9321d3a6f (patch) | |
tree | 772c254268a4c4b5cd1bb9ae6a872ee6a324b2e3 /images/logo_iot_bzh.svg | |
parent | 9e3940f8de8b2dffd2550fcf5aa3503b9610e441 (diff) |
Restore /etc/dev-mapping.conf supportjellyfish_10.0.3jellyfish_10.0.2jellyfish/10.0.3jellyfish/10.0.210.0.310.0.2jellyfish
Add back the ini-config and config-parser code that existed
previously, and use it in binding init to over-ride the device
mapping from the controller JSON if /etc/dev-mapping.conf exists.
This restores the documented behavior, and is needed for the
existing AGL demo platform support and soon CI.
Additionally:
- Add code to validate the active_message_set, diagnostic_bus, and
bus device mapping configuration values.
- The above required moving plugin loading before the configuration
callback in the controller configuration, but this change seems
rational in that everything required by the generated plugin code
is already initialized before then, and it makes validating the
configuration possible without adding an extra callback.
- Add logging of the used CAN bus to device mappings at info level
to ease debugging any future issues.
- Tweak the log level of the missing configuration file message to
info from error, since it is a legitimate mode of operation if
relying on the default bus values in the controller JSON.
Bug-AGL: SPEC-3755
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I440f5e0fc85be41f7c4c1f47d824a403525a18f9
(cherry picked from commit 9e23caa4c56259044604c38f107f7c637001b846)
Diffstat (limited to 'images/logo_iot_bzh.svg')
0 files changed, 0 insertions, 0 deletions