From 04feb9809138b5d46ef2fecc705a17414a5a6d9e Mon Sep 17 00:00:00 2001 From: Peter Barker Date: Tue, 18 Apr 2023 17:24:17 +1000 Subject: [PATCH] AP_KDECAN: move and rename CAN Driver_Type enumeration --- libraries/AP_KDECAN/AP_KDECAN.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libraries/AP_KDECAN/AP_KDECAN.cpp b/libraries/AP_KDECAN/AP_KDECAN.cpp index 88cffb1157..db0afdf4ab 100644 --- a/libraries/AP_KDECAN/AP_KDECAN.cpp +++ b/libraries/AP_KDECAN/AP_KDECAN.cpp @@ -62,7 +62,7 @@ void AP_KDECAN::init() } for (uint8_t i = 0; i < HAL_NUM_CAN_IFACES; i++) { - if (CANSensor::get_driver_type(i) == AP_CANManager::Driver_Type_KDECAN) { + if (CANSensor::get_driver_type(i) == AP_CAN::Protocol::KDECAN) { _driver = new AP_KDECAN_Driver(); return; } @@ -79,7 +79,7 @@ void AP_KDECAN::update() AP_KDECAN_Driver::AP_KDECAN_Driver() : CANSensor("KDECAN") { - register_driver(AP_CANManager::Driver_Type_KDECAN); + register_driver(AP_CAN::Protocol::KDECAN); // start thread for receiving and sending CAN frames. Tests show we use about 640 bytes of stack hal.scheduler->thread_create(FUNCTOR_BIND_MEMBER(&AP_KDECAN_Driver::loop, void), "kdecan", 2048, AP_HAL::Scheduler::PRIORITY_CAN, 0);