17 Commits

Author	SHA1	Message	Date
stephan	0b24dc239f	GCS_MAVlink: correct routing for Solo Gimbal ... Check for a opro camera in a Solo gimbal added and re-enable the routing of Gopro Mavlink commands	2023-10-17 10:02:49 +11:00
Peter Barker	b55664034f	GCS_MAVLink: use GCS_MAVLINK& when routing	2023-03-08 19:30:22 +11:00
olliw42	c034f8a099	GCS_MAVLink: add find_by_mavtype_and_compid	2022-09-12 08:44:38 +09:00
Peter Barker	17ad710866	GCS_MAVLink: tidy includes	2022-05-03 09:14:58 +10:00
Peter Barker	a96a4c0510	GCS_MAVLink: correct encoding used for send_to_components ... These have to be packed onto the channel - otherwise they may ge tencoded as mavlink1 instead of mavlink2 (or vice-versa)	2019-11-26 12:10:12 +11:00
Pierre Kancir	b1506ca652	GCS_MAVLink: pass mavlink_message_t by const reference	2019-07-16 20:51:42 +10:00
Mathieu OTHACEHE	152edf7189	Global: remove mode line from headers ... Using a global .dir-locals.el file is a better alternative than reincluding the same emacs header in every file of the project.	2016-10-24 09:42:01 -02:00
Tom Pittenger	fc02908c0d	Revert "GCS_MAVLink: coverity scan - variables not initialized in constructor" ... This reverts commit bd8debdf8b.	2016-07-11 22:01:50 -07:00
Tom Pittenger	bd8debdf8b	GCS_MAVLink: coverity scan - variables not initialized in constructor	2016-07-05 13:32:24 -07:00
proficnc	c8b3c527f9	GCS_MAVLink: add route mask for blocking MAVlink forwading	2016-05-12 17:44:06 +10:00
Lucas De Marchi	c2b5ad46b4	GCS_MAVLink: replace header guard with pragma once	2016-03-16 18:40:44 +11:00
Lucas De Marchi	45c472205b	GCS_MAVLink: remove check for AVR CPUs ... Remove the checks for HAL_CPU_CLASS > HAL_CPU_CLASS_16 and HAL_CPU_CLASS >= HAL_CPU_CLASS_75. Corresponding dead code will be removed on separate commits.	2015-11-04 12:14:14 +11:00
Gustavo Jose de Sousa	d7a2ef3e35	GCS_MAVLink: standardize inclusion of libaries headers ... This commit changes the way libraries headers are included in source files: - If the header is in the same directory the source belongs to, so the notation '#include ""' is used with the path relative to the directory containing the source. - If the header is outside the directory containing the source, then we use the notation '#include <>' with the path relative to libraries folder. Some of the advantages of such approach: - Only one search path for libraries headers. - OSs like Windows may have a better lookup time.	2015-08-11 16:38:25 +10:00
Randy Mackay	e092902613	GCS_MAVLink: add find_by_mavtype	2015-07-25 10:52:59 +09:00
Randy Mackay	1f705eb6a3	GCS_MAVLink: add send_to_components method	2015-04-20 13:50:04 +09:00
Andrew Tridgell	b5a5b71512	GCS_MAVLink: reverse sense of check_and_forward() ... also increase number of routes on larger systems and improved route learning logic	2014-12-17 10:32:28 +11:00
Andrew Tridgell	b91529622b	GCS_MAVLink: initial implementation of MAVLink routing object ... will be used to auto-route packets over all available links	2014-12-11 12:30:50 +09:00