-
Notifications
You must be signed in to change notification settings - Fork 2
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
BMA421 and BMA425 integration RFC #8
base: main
Are you sure you want to change the base?
BMA421 and BMA425 integration RFC #8
Conversation
…ecific type aliases for generic Bma42x struct
Hi! Awesome work, thanks a lot :) I won't have time to test it in the next two weeks, but I hope to be able to do it then. In the meantime, I have two comments:
|
Does this have any implications for me or is it merely meant as an information?
Great idea! I will look into this, thanks for the suggestion. |
It's only an information, I will do it on my side. You might have to rebase your branch once this is done though. I'll keep you informed |
Hi, I added the compiler errors as requested. |
This is a first draft of the BMA421 and BMA425 integration as discussed in this issue.
Scope
I have implemented and briefly tested the modifications within my pinetime-rust project. There’s definitely more thorough testing needed but I haven’t been able to spend a lot of time on that project lately.
For now, I’d like to get your feedback on my implementation. Please let me know if there’s anything you would like to change or you have suggestions for improvements.
Overview
Additional Notes
I already changed the package name in the draft to bma42x to prevent confusion with the modules, which I have named after the models.