AP_Camera: runcam backend #26887
AP_Camera: runcam backend #26887
Conversation
|
I like where this is going! |
|
@andyp1per where are you going with this one? What advantages were you seeing from being a camera backend? I'd note that the camera library, even in its most compact form is still going to be pretty chunky, and recent commits have shown we don't really care about keeping it absolutely tight space-wise. Definitely not saying it's a bad idea! |
andyp1per
force-pushed
the
pr-runcam-backend
branch
from
6eb3394
to
302a30b
Compare
|
The main thing is to get the mavlink and other support for free. People keep asking for runcam mission support |
andyp1per
force-pushed
the
pr-runcam-backend
branch
from
2dcb5eb
to
3a267a9
Compare
andyp1per
force-pushed
the
pr-runcam-backend
branch
from
ea11a70
to
bfb7c81
Compare
andyp1per
force-pushed
the
pr-runcam-backend
branch
from
fbb728c
to
098da39
Compare
|
@rmackay9 this is ready to go - any chance of a review? |
rmackay9
dismissed
peterbarker’s stale review
PeterB's requests have been addressed it seems
| @@ -193,6 +209,8 @@ void AP_Camera::init() | |||
| return; | |||
| } | |||
|
|
|||
| memset(_backends, 0, sizeof(void*)*AP_CAMERA_MAX_INSTANCES); | |||
There was a problem hiding this comment.
Why is this being done?!
| memset(_backends, 0, sizeof(void*)*AP_CAMERA_MAX_INSTANCES); |
There was a problem hiding this comment.
Because the array is not zeroed and we check whether the backend has been allocated.
RunCam parameter conversion add RunCam camera settings and control
andyp1per
force-pushed
the
pr-runcam-backend
branch
from
f357ac4
to
dace135
Compare
RunCam as a proper camera backend.
Adds a couple of the mavlink info callbacks
Parameter conversion and operation verified on my RunCam split