aboutsummaryrefslogtreecommitdiff
path: root/framebuffer_memory.md
diff options
context:
space:
mode:
authormrfaptastic <12006953+mrfaptastic@users.noreply.github.com>2020-11-28 08:39:35 +0000
committermrfaptastic <12006953+mrfaptastic@users.noreply.github.com>2020-11-28 08:39:35 +0000
commitb6da8ea09a84004354edf720cbd2c7d76f20d767 (patch)
treea4e0d2765d92cb4967971b243831bbac128dbe24 /framebuffer_memory.md
parent9f9150183619ae755a0d27449ab594b561e22918 (diff)
Change library name
Diffstat (limited to 'framebuffer_memory.md')
-rw-r--r--framebuffer_memory.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/framebuffer_memory.md b/framebuffer_memory.md
index 9f31088..982d40f 100644
--- a/framebuffer_memory.md
+++ b/framebuffer_memory.md
@@ -48,4 +48,4 @@ Given it's possible to display 128x32 with double buffering in approx. 100kB of
# Caveats
-Experimentation will be required as available memory is highly dependant on other stuff you have in your sketch. It is best to include and use the 'ESP32-RGB64x32MatrixPanel-I2S-DMA' library as early as possible in your code and analyse the serial output of `heap_caps_print_heap_info(MALLOC_CAP_DMA)` to see what DMA memory blocks are available.
+Experimentation will be required as available memory is highly dependant on other stuff you have in your sketch. It is best to include and use the 'ESP32-HUB75-MatrixPanel-I2S-DMA' library as early as possible in your code and analyse the serial output of `heap_caps_print_heap_info(MALLOC_CAP_DMA)` to see what DMA memory blocks are available.