Minor wording fixes

This commit is contained in:
mrfaptastic 2020-07-30 23:21:08 +01:00
parent 17ded79658
commit 80d5ddff4c
2 changed files with 6 additions and 14 deletions

View file

@ -70,17 +70,9 @@ This library has only been tested with a 64 pixel (wide) and 32 (high) RGB panel
### New Feature ### New Feature
With version 1.1.0 of the library onwards, there is now a 'feature' to split the framebuffer over two memory 'blocks' (mallocs) to work around the fact that typically the ESP32 upon 'boot up' has 2 x ~100kb chunks of memory available to use (ideally we'd want one massive chunk, but for whatever reasons this isn't the case). This allows non-contiguous memory allocations to be joined-up potentially allowing for 512x64 resolution or greater. No guarantees however. With version 1.1.0 of the library onwards, there is now a 'feature' to split the framebuffer over two memory 'blocks' (mallocs) to work around the fact that typically the ESP32 upon 'boot up' has 2 x ~100kb chunks of memory available to use (ideally we'd want one massive chunk, but for whatever reasons this isn't the case). This allows non-contiguous memory allocations to be joined-up potentially allowing for 512x64 resolution or greater (no guarantees however). This is enabled by default.
``` [Refer to this](SPLIT_MEMORY_MODE.md) for more details.
// At the top of 'ESP32-RGB64x32MatrixPanel-I2S-DMA.h':
//
// Experimental: Split the framebuffer into two smaller memory allocations.
// Can allow a bigger resolution due to the fragmented memory
// map of the typical Arduino sketch even before setup().
#define SPLIT_MEMORY_MODE 1
```
Refer to [to this](SPLIT_MEMORY_MODE.md) for more details.
## Ghosting ## Ghosting

View file

@ -1,13 +1,13 @@
# SPLIT_MEMORY_MODE # SPLIT_MEMORY_MODE
To enable split framebuffer memory mode, uncomment line: Aka. the enabling of the 'feature' (enabled by default) with:
``` ```
//#define SPLIT_MEMORY_MODE 1 #define SPLIT_MEMORY_MODE 1
``` ```
in 'ESP32-RGB64x32MatrixPanel-I2S-DMA.h' ...in 'ESP32-RGB64x32MatrixPanel-I2S-DMA.h'
## What is it trying to resolve? ## What is it trying to resolve?
For whatever reason, and this may not be consistent across all ESP32 environments, 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 whatever reason (and this may not be consistent across all ESP32 environments) 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: Heap summary for capabilities 0x00000008: