Skip to content

Conversation

@ke5gdb
Copy link
Contributor

@ke5gdb ke5gdb commented Jul 20, 2025

No description provided.

@ke5gdb ke5gdb marked this pull request as ready for review August 21, 2025 02:40
@ke5gdb
Copy link
Contributor Author

ke5gdb commented Aug 21, 2025

This is ready for review. One change that I implemented that may need discussion is the use of preprocessor commands to enable certain features rather than mapping them to boolean values. GCC didn't do a great job with optimizations if they weren't written as preprocessor commands.

@mikaelnousiainen
Copy link
Owner

@ke5gdb Thanks for the contribution, this looks mostly good! Did you test the code on all variants of the sensor?

We'll probably have to decide on whether we'd use booleans vs preprocessor logic for feature flags and refactor this code a bit. Now it's a bit mixed.

@ke5gdb
Copy link
Contributor Author

ke5gdb commented Sep 4, 2025

I only tested it on the BMP680 since that's what I have handy (I thought I had a 690, wrote the interface for a 690, and then realized that it got subbed for a 680). It has been well tested (including two flights) with the 680 though.

I agree on coming to a decision on boolean vs preprocessor logic. It seems like some optimization just isn't taking place that should allow constant boolean expressions to be factored out as if they were a preprocessor command, but I lack experience in that domain.

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.

2 participants