Support lsb0 bit ordering - #1
Open
hacklint wants to merge 1 commit into
Open
Conversation
Add the option of using lsb0-based bit numbering in bitfield-access
Proved useful eg for handling Can data on Intel, "sawtooth" numbering
Rename existing read_field and write_field functions with prepended _,
adding wrapper functions read_filed and read_field_lsb0 (symmetric for
write), essentially extending the api with functions read_field_lsb0
and write_field_lsb0. Not sure if it is the best way to extend, but it
works.
Also add basic tests for the new capabilities.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the option of using lsb0-based bit numbering in bitfield-access
Proved useful eg for handling Can data on Intel, "sawtooth" numbering
Rename existing read_field and write_field functions with prepended _,
adding wrapper functions read_filed and read_field_lsb0 (symmetric for
write), essentially extending the api with functions read_field_lsb0
and write_field_lsb0. Not sure if it is the best way to extend, but it
works.
Also add basic tests for the new capabilities.