Mahavir Jain 0ba529d267 fix(esp_mm): for existing mmap region, consider new offset for virtual addr ... While returning virtual address for existing memory mapped region, newly supplied offset from the physical address was not getting considered. This was a regression present from ESP-IDF 5.1 release. Added test case in spi_flash component that fails without this fix. Closes https://github.com/espressif/esp-idf/issues/13929		2024-07-15 12:42:27 +08:00
..
include	fix(esp_mm): for existing mmap region, consider new offset for virtual addr	2024-07-15 12:42:27 +08:00
port	change(soc): added SOC_ prefix to mmu defs	2023-09-05 15:47:26 +08:00
test_apps	refactor(esp_mm): reformat code with astyle_py 2	2023-10-09 15:29:31 +08:00
cache_esp32.c	refactor(esp_mm): reformat code with astyle_py	2023-10-08 10:36:04 +08:00
CMakeLists.txt	refactor(linux): excluded all non-Linux components from build	2023-10-16 17:06:54 +08:00
esp_cache.c	bugfix(cache): don't allow M2C direction ESP_CACHE_MSYNC_FLAG_UNALIGNED	2024-03-25 16:06:44 +08:00
esp_mmu_map.c	fix(esp_mm): for existing mmap region, consider new offset for virtual addr	2024-07-15 12:42:27 +08:00
ext_mem_layout.h	refactor(esp_mm): reformat code with astyle_py	2023-10-08 10:36:04 +08:00
linker.lf	esp_mm: fix dependency to esp_psram	2023-02-28 10:42:22 +08:00