forked from Archive/PX4-Autopilot
mavlink-ftp: Add extra padding because the ringbuffer implementation relies on its use
This commit is contained in:
parent
f9db1723e3
commit
7546b99a24
|
@ -1903,8 +1903,11 @@ Mavlink::task_main(int argc, char *argv[])
|
||||||
|
|
||||||
/* if we are passing on mavlink messages, we need to prepare a buffer for this instance */
|
/* if we are passing on mavlink messages, we need to prepare a buffer for this instance */
|
||||||
if (_passing_on || _ftp_on) {
|
if (_passing_on || _ftp_on) {
|
||||||
/* initialize message buffer if multiplexing is on */
|
/* initialize message buffer if multiplexing is on or its needed for FTP.
|
||||||
if (OK != message_buffer_init(2 * MAVLINK_MAX_PACKET_LEN)) {
|
* make space for two messages plus off-by-one space as we use the empty element
|
||||||
|
* marker ring buffer approach.
|
||||||
|
*/
|
||||||
|
if (OK != message_buffer_init(2 * MAVLINK_MAX_PACKET_LEN + 2)) {
|
||||||
errx(1, "can't allocate message buffer, exiting");
|
errx(1, "can't allocate message buffer, exiting");
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue