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

Allow configuring maximum frame length more precisely #609

Merged
merged 1 commit into from
Dec 5, 2020

Conversation

matthijskooijman
Copy link

This deprecates the LMIC_ENABLE_long_messages configuration macro and
allows configuring LMIC_MAX_FRAME_LENGTH instead, allowing a more
fine-grained balance between memory usage and maximum frame length.

I originally started this because I was a bit confused with the documentation for LMIC_ENABLE_long_messages (it wasn't entirely clear what the default setting was), but while rewriting the README entry about this, I realized it was weird that you could only choose between two maximum sizes, when there's no technical reason (that I could see) to limit this to specific values (other than that the value should not be too small).

This deprecates the `LMIC_ENABLE_long_messages` configuration macro and
allows configuring LMIC_MAX_FRAME_LENGTH instead, allowing a more
fine-grained balance between memory usage and maximum frame length.
@terrillmoore
Copy link
Member

I agree, we can change this.

@terrillmoore terrillmoore merged commit 09437d1 into mcci-catena:master Dec 5, 2020
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.

None yet

2 participants