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

AP_RobotisServo: Send register write values as little-endian #23689

Closed

Conversation

nexton-winjeel
Copy link
Contributor

@nexton-winjeel nexton-winjeel force-pushed the upstream/fix-robotis-endianness branch from 12adf00 to 075e09e Compare May 15, 2023 05:31
@peterbarker
Copy link
Contributor

Was this tested?

I'm really guessing you tested this on a little-endian machine where this is a no-op.

Was this seriously causing someone trouble?

I mean, yeah, we'll merge this, but I am curious why the patch was proposed.

@nexton-winjeel
Copy link
Contributor Author

nexton-winjeel commented Sep 12, 2024

I'm really guessing you tested this on a little-endian machine where this is a no-op.

Yeah, tested on a little-endian machine, but not on a big-endian machine.

Was this seriously causing someone trouble?

I doubt it, but if someone happens to run this driver on a big-endian device, it won't end well.

I mean, yeah, we'll merge this, but I am curious why the patch was proposed.

Because it's a bug with a trivial fix.

@peterbarker
Copy link
Contributor

I'm really guessing you tested this on a little-endian machine where this is a no-op.
Yeah, tested on a little-endian machine, but not on a big-endian machine.

The latter are becoming hard-to-find. Or at least find ones that can't be switched.

Was this seriously causing someone trouble?
I doubt it, but if someone happens to run this driver on a big-endian device, it won't end well.

We gave up the pretense of supporting big-endian a while back - this bit's only the tip of the iceberg, I assure you!

I mean, yeah, we'll merge this, but I am curious why the patch was proposed.
Because it's a bug with a trivial fix.

Yep, agreed, it is a bugfix, and I will merge it.

But there's two commits in here, and I don't trust that merge commit to just go away. I also can't force-push your branch to fix the problem. Could you rebase this such that there's only a single commit, please?

@peterbarker
Copy link
Contributor

Replaced by #28243 as I can't force-push this branch

The new PR is marked as merge-on-ci-pass

@peterbarker
Copy link
Contributor

I've merged the other PR with the single commit in it. Thanks!

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

Successfully merging this pull request may close these issues.

3 participants