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

   depends-on: [apache/nuttx/pull/20089 apache/nuttx/pull/20130 
apache/nuttx/pull/20131]
   
   ## Summary
   
   The last part of the FDPIC series: what it is, and a configuration that runs 
it.
   
   `Documentation/components/fdpic.rst` covers what an FDPIC module is and what 
it adds over the position independent ELF support already in the tree, how the 
loader places one, where shared libraries come from and how they are found, 
which entry points resolve a function descriptor and the rules for adding 
another, and how to build a module and a library. A comparison table places it 
against NXFLAT and PIC ELF, and the reference section records the object layout 
and the relocations.
   
   `pimoroni-pico-2-plus:xipfs-fdpic` is the configuration the series was 
tested on: xipfs on the board's QSPI flash, the ELF loader with `CONFIG_FDPIC`, 
`apps/examples/fdpicxip` and `apps/testing/fs/xipfs`.
   
   `CONFIG_DEFAULT_TASK_STACKSIZE` is 4096 there rather than the rp23xx default 
of 2048. Both sides of the loader need it: a module that calls into the 
firmware's `printf` family overflows 2048, and with no MPU that is a lockup 
rather than a diagnostic. `CONFIG_ELF_STACKSIZE` follows it, and 
`apps/testing/fs/xipfs` sizes its own task from it.
   
   ## Impact
   
   Documentation, one board configuration, and a line in two index pages. No 
code.
   
   ## Testing
   
   `pimoroni-pico-2-plus:xipfs-fdpic` builds standing alone on master.
   
   `tools/refresh.sh` leaves the new defconfig unchanged, so the CI normalize 
step stays clean.
   
   `tools/checkpatch.sh -c -u -m -g` passes.
   
   ## Draft
   
   Draft because it is the tail of the series, and because `[9/10]`, which 
loads `DT_NEEDED` libraries, is not yet opened. The `xipfs` suite this 
configuration runs covers cases that need it, so this should not merge before 
it.
   


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