zrzk/zr-v4 - zr-v4 - Gitea: Brown's Gitea

Author	SHA1	Message	Date
Randy Mackay	1b0f0a7559	AP_RangeFinder: support last_reading_ms Benewake, LeddarOne, LightWareSerial, MAVLink, MaxsonarI2CXL, MaxsonarSerialLV, NMEA, PX4_PWM, uLanding and Wasp already stored the last read time so for these drivers, this change just moves that storage to the state structure analog, BBB_PRU, Bebop, LightWareI2C, PulsedLightLRF, TeraRangerI2C, VL53L0X did not store the last read time so this was added	7 years ago
Peter Barker	30c4ea8123	AP_RangeFinder: stop storing sensor type as a variable And change method name	8 years ago
Peter Barker	0b1c67d170	AP_RangeFinder: remove unused parameters from detect and constructors	8 years ago
Pierre Kancir	8b38bd2e33	AP_RangeFinder: add sensor type to backend	8 years ago
Lucas De Marchi	932d1ae244	AP_RangeFinder: add O_CLOEXEC in places missing it By opening with O_CLOEXEC we make sure we don't leak the file descriptor when we are exec'ing or calling out subprograms. Right now we currently don't do it so there's no harm, but it's good practice in Linux to have it.	8 years ago
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
mirkix	2d9b230be1	AP_RangeFinder: Load .data section for HC-SR04 PRU driver used by BBBMINI This adds .data section loading to the HC-SR04 range finder driver used by BBBMINI. The firmware is running inside a PRU. It is necessary to develop more complex driver software inside the PRU.	9 years ago
Gustavo Jose de Sousa	5d39587469	AP_RangeFinder: 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
mirkix	1b0f482d37	AP_RangeFinder: Add support for HC-SR04 Range Finder connected to BBB	10 years ago