diff options
| author | mrfaptastic <12006953+mrfaptastic@users.noreply.github.com> | 2020-08-20 11:11:19 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-08-20 11:11:19 +0100 |
| commit | 501211ca6d81238b5a262586512353d5ce049028 (patch) | |
| tree | 01e36ae5507ffa0f6bf1670fd582596a6ccbe9b6 | |
| parent | 80770043f6ed79c014063b99a9d8d5c422096c6c (diff) | |
Update framebuffer_memory.md
| -rw-r--r-- | framebuffer_memory.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/framebuffer_memory.md b/framebuffer_memory.md index ddc228b..9f31088 100644 --- a/framebuffer_memory.md +++ b/framebuffer_memory.md @@ -2,7 +2,7 @@ With version 1.2.2 of the library onwards, the framebuffer is split over multiple 'blocks' (mallocs) as a workaround to the fact the typical Arduino sketch can have a fragmented memory map whereby a single contiguous memory allocation may not be available to fit the entire display. -Foe example when `heap_caps_print_heap_info(MALLOC_CAP_DMA)` is executed to print information about the available memory blocks that are DMA capable (which we need for a DMA-enabled pixel framebuffer), you may see something like this: +For example when `heap_caps_print_heap_info(MALLOC_CAP_DMA)` is executed to print information about the available memory blocks that are DMA capable (which we need for a DMA-enabled pixel framebuffer), you may see something like this: ``` Heap summary for capabilities 0x00000008: |