We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Our first attempt at embedded protos required gazelle:ignore and an inability to use repeated, we'll need to get that working fairly soon.
repeated
Probably want to get different suffixes used for the generated code.
Additionally, it'd be good to setup useful comparisons (we should be able to check == between 2 structs easily for test, etc.)
==
The text was updated successfully, but these errors were encountered:
Setup our first hardware driver (hw_drivers) for LIS3MDL Magnetometer (…
2425414
…#143) - Use [emboss](https://github.com/google/emboss) to define the register map for the LIS3MDL. - Define proto interfaces to describe how we'd use this device / magnetometers in general. - Setup a focused test as well as a `pw_test` in order to confirm some of the behavior for pw::i2c. - Takes a lot of notes and possible changes in the future Documents copied here for convenience: - [LIS3MDL-AN4602.pdf](https://github.com/user-attachments/files/17693949/LIS3MDL-AN4602.pdf) - [LIS3MDL.pdf](https://github.com/user-attachments/files/17693950/LIS3MDL.pdf) Followups: - #144 - #145 - #147 - #148 - #149
Wire up the sbr service into the app (#155)
e0b6b35
This is the culmination of several PRs, allowing us to bind this service to this app. See #155 (comment) for my log of notes along the way. Here are the related PRs: - #153 - #152 - #151 - #150 - #143 - #142 - #141 - #140 - #138 And the created/related issues: - #154 - #149 - #148 - #147 - #145 - #144 - #139 - #125
No branches or pull requests
Our first attempt at embedded protos required gazelle:ignore and an inability to use
repeated
, we'll need to get that working fairly soon.Probably want to get different suffixes used for the generated code.
Additionally, it'd be good to setup useful comparisons (we should be able to check
==
between 2 structs easily for test, etc.)The text was updated successfully, but these errors were encountered: