jerpelea opened a new pull request, #20285:
URL: https://github.com/apache/nuttx/pull/20285

   ## Summary
   
   Switch every rv-virt (qemu-rv) flat-build defconfig whose init entry point 
was
   nsh_main to nxinit (init_main): citest, citest64, fb, fb64, flats, flats64,
   leds, leds64, leds64_rust, leds64_zig, libcxx, libcxx64, lvgl64_vector, 
netnsh,
   netnsh64, netnsh64_smp, netnsh_smp, nsh, nsh64, python, smp, smp64, virt_nsh,
   plus pnsh/pnsh64 (CONFIG_BUILD_PROTECTED=y) — 25 configs total. nsh now runs
   as a "console sh" service started by init.rc instead of being the top-level
   init task, matching the pattern already used by boards/arm/qemu-armv7a,
   boards/arm64/qemu-armv8a and boards/sim.
   
   elf (entrypoint elf_main) and the 11 kernel-build configs
   (CONFIG_INIT_FILEPATH="/system/bin/init") are out of scope and untouched.
   
   Each switched defconfig only gains the nxinit-essential keys (minimal delta,
   regenerated with make savedefconfig): CONFIG_INIT_ENTRYPOINT="init_main",
   CONFIG_SYSTEM_NXINIT=y (+ its deps EXPERIMENTAL, LIBC_EXECFUNCS,
   SCHED_CHILD_STATUS), CONFIG_ETC_ROMFS=y/CONFIG_FS_ROMFS=y to ship
   init.rc. Board changes: new src/etc/init.d/init.rc, Makefile/CMakeLists.txt
   to ship it via ROMFS, and a CONFIG_FS_BINFS-gated
   mount(NULL, CONFIG_PATH_INITIAL, "binfs", ...) in qemu_rv_boardinit.c so
   posix_spawnp("sh") can resolve the builtin. CONFIG_PATH_INITIAL is left at 
its pre-existing "/system/bin" and binfs is
   mounted at that same CONFIG_PATH_INITIAL path, so no defconfig needs a
   PATH_INITIAL change.
   
   smp/smp64 additionally re-enable binfmt (they had CONFIG_DEFAULT_SMALL=y 
pulling
   in CONFIG_BINFMT_DISABLE=y, which would block LIBC_EXECFUNCS→SYSTEM_NXINIT).
   pnsh/pnsh64 rely on the boardctl(BOARDIOC_BUILTINS) hand-off; see the second 
commit.
   
   ## Impact
   
   RELEASE
   
   ## Testing
   
   CI


-- 
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]

Reply via email to