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.
RingBuffer
is used for many things insidemachine
package and has size128
bytes, hardcoded for optimisation. However,128
bytes is quite big chunk of memory on2k
ram targets (~6%) that many atmel chips are.Among other things,
UART
usesRingBuffer
, so this is an instant tax that end users can't really avoid.Would be nice to cut this tax for targets with low memory budget.
This PR conditionally sets
RingBuffer
's size to32
bytes onatmega
tagged targets.Of course, there can be other targets with small ram and some
atmega
chips have up to16k
ram and128
bytes may be fine for them.So this is a first step, and we may want to adjust the sizes conditionally further, as a follow up.
This also updatessizediff
tool to show ram differences and cleans up unused code.Change in
sizediff
extracted to a separate PR #4023