raul_chen e0373cc39d arch/arm/ameba: cache SDK config, add ameba_menuconfig, silence vendor warning ... The NP and bootloader images are built from the vendored ameba-rtos SDK. Rework how that sub-build is configured and driven: - Materialize the SDK menuconfig once, guarded by a stamp (SDK revision + board overlay). A no-change rebuild no longer rewrites the SDK .config, so the SDK stops reconfiguring and recompiling most of the NP image every time; only the AP-driven "noused" file is regenerated. (ameba_sdk_config.sh) - Configure the SDK from a two-tier prj.conf-style overlay per board: ameba_sdk.conf (user-editable) layered under ameba_sdk_force.conf (forced options such as CONFIG_SHELL=n, always applied last and re-applied after an edit), so options that must stay fixed cannot be overridden. - Add "make ameba_menuconfig": edit the SDK options in the SDK's own native menuconfig UI and save the diff back to the board overlay. - Silence -Wint-conversion for the vendored SDK sources (both the NuttX fwlib compile and the SDK NP/boot build): the SDK passes NULL to irq_register()'s u32 "Data" argument in many places; the warning is suppressed for vendor code instead of editing every call site. Signed-off-by: raul_chen <raul_chen@realsil.com.cn>		2026-07-16 12:11:19 -04:00
..
ameba_menuconfig.sh	arch/arm/ameba: cache SDK config, add ameba_menuconfig, silence vendor warning	2026-07-16 12:11:19 -04:00
Config.mk	arch/arm/ameba: cache SDK config, add ameba_menuconfig, silence vendor warning	2026-07-16 12:11:19 -04:00