Tree: cd8661c665

c415-sdk

celiu-4.0

celiu-4.0.17-rc8

master

mission-4.1.18

zr-sdk-4.1.16

zr-sdk-4.3.1

zr-v4.1.17

zr-v5.0

zr-v5.1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'cd8661c665'

${ noResults }

Commit Graph

12 Commits (cd8661c66520898aeb3f59e1ba5793ffe4bb1fd3)

Author	SHA1	Message	Date
murata	c808ee2f49	Global: To nullptr from NULL. ... RC_Channel: To nullptr from NULL. AC_Fence: To nullptr from NULL. AC_Avoidance: To nullptr from NULL. AC_PrecLand: To nullptr from NULL. DataFlash: To nullptr from NULL. SITL: To nullptr from NULL. GCS_MAVLink: To nullptr from NULL. DataFlash: To nullptr from NULL. AP_Compass: To nullptr from NULL. Global: To nullptr from NULL. Global: To nullptr from NULL.	8 years ago
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.	8 years ago
Gustavo Jose de Sousa	f9cb760691	AP_Mount: use ARRAY_SUBSCRIPT instead of bytes field ... That fixed compilation issues and seems more semantically correct. Using array of length 0 fails compilation because of -Werror=array-bounds in GCC 6.1.	9 years ago
Andrew Tridgell	f377787444	AP_Mount: always build with MAVLink2 headers	9 years ago
Andrew Tridgell	0ef5d8995b	AP_Mount: support mavlink2 build	9 years ago
Caio Marcelo de Oliveira Filho	0b2184b818	AP_Mount: use millis/micros/panic functions	9 years ago
fillycheezstake	39dae7a156	Mount: fix for STORM32 serial ver 78e and higher ... This fixes the structs to be compatible with the changes OlliW made to the gimbal firmware. http://www.olliw.eu/storm32bgc-wiki/Serial_Communication	10 years ago
Lucas De Marchi	2011c4d988	AP_HAL_Mount: standardize inclusion of libaries headers ... Do the missing header changes due to changing the code before the pr getting accepted.	10 years ago
Gustavo Jose de Sousa	8011579c5a	AP_Mount: 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.	10 years ago
Randy Mackay	fb2d29364e	Mount_SToRM32_serial: fix angle request	10 years ago
Randy Mackay	9b04a67e63	Mount_SToRM32_serial: rename sent_do_mount_control	10 years ago
Sergey Kirillov	c133511431	Mount: add SToRM32 serial support	10 years ago