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

GPS: explicitly disable flow control #9019

Merged
merged 1 commit into from
Mar 5, 2018
Merged

Conversation

bkueng
Copy link
Member

@bkueng bkueng commented Mar 5, 2018

If the GPS driver was used on another port (e.g. TELEM2), it would get stuck in a write call and not return anymore. Disabling flow control fixes that.

CPU usage is unchanged.

Tested on a Pixracer, dual gps now works too: gps start -d /dev/ttyS2 -e /dev/ttyS3 (although for testing I only had one GPS connected at a time).

Fixes #8945

If the GPS driver was used on another port (e.g. TELEM2), it would get
stuck in a `write` call and not return anymore. Disabling flow control
fixes that.

CPU usage is unchanged.
@LorenzMeier LorenzMeier merged commit 03b8cd7 into master Mar 5, 2018
@LorenzMeier LorenzMeier deleted the gps_disable_flow_control branch March 5, 2018 15:43
@Rickyg32
Copy link

Rickyg32 commented May 1, 2018

Anyone have an idea when this fix makes it into a gold version

@Rickyg32
Copy link

Rickyg32 commented May 3, 2018

Has this fix made it into a gold release

@mhkabir
Copy link
Member

mhkabir commented May 3, 2018

@Rickyg32 Please stop spamming. If you need this fix on a stable release version, you will need to cherry-pick it to 1.7.4. You can also directly use master.

We do not yet have a hard release timeline for v1.8.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for reading second GPS instance is broken
4 participants