Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate OSD layout responses over MSP by layout #3420

Merged
merged 1 commit into from Jun 24, 2018

Conversation

Projects
None yet
1 participant
@fiam
Copy link
Member

commented Jun 22, 2018

Since sending the whole layouts over MSP was making the layouts
response too big (bigger than the default 512 bytes MSP TX buffer),
each OSD layout is now sent separately via by making
MSP2_INAV_OSD_LAYOUTS an in/out message.

Also, all 5 in/out messages have now been moved to a function which
handles all of them (mspFCProcessInOutCommand()).

Fixes crash when retriving the OSD layouts via MSP.

Configurator PR iNavFlight/inav-configurator#486

@fiam fiam added this to the 2.0 milestone Jun 22, 2018

Separate OSD layout responses over MSP by layout
Since sending the whole layouts over MSP was making the layouts
response too big (bigger than the default 512 bytes MSP TX buffer),
each OSD layout is now sent separately via by making
MSP2_INAV_OSD_LAYOUTS an in/out message.

Also, all 5 in/out messages have now been moved to a function which
handles all of them (mspFCProcessInOutCommand()).

Fixes crash when retriving the OSD layouts via MSP.

@fiam fiam force-pushed the agh_msp_osd_separate_layouts branch from c018f03 to 414cd2f Jun 23, 2018

@fiam fiam merged commit 90e0c4b into development Jun 24, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@fiam fiam deleted the agh_msp_osd_separate_layouts branch Jun 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.