aviralgarg05 commented on PR #3644: URL: https://github.com/apache/nuttx-apps/pull/3644#issuecomment-4994519524
> Can we resolve this with FAR designators? `FAR` is defined as empty on this target (Xtensa/flat 32-bit memory model). It only expands to something real on segmented 8/16-bit architectures like 8051 (`__xdata`) or old x86 memory models (`far`/`_Far`), where it's about pointer segment qualification, not memory placement. The actual problem here is static/BSS footprint at link time — a large static array is always-resident regardless of what pointer qualifier you put on it, `FAR` included. That's a different axis from what `FAR` addresses, so it won't help with the DRAM budget concern. The Kconfig-gated heap allocation is still the mechanism that actually moves the buffer's footprint onto the PSRAM-backed heap instead of internal SRAM. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
