This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/nuttx-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 38ee852160 Publishing docs: 295bf8c3858f01002b533cc9ba21d57f3937d785
(web: ce9541eb25988a465c6b6507c9019edb890a6db4)
38ee852160 is described below
commit 38ee852160c070e0cabb683a37c92f7e0fde24c8
Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
AuthorDate: Sat Nov 21 00:09:06 2026 +0000
Publishing docs: 295bf8c3858f01002b533cc9ba21d57f3937d785 (web:
ce9541eb25988a465c6b6507c9019edb890a6db4)
---
.../applications/graphics/input/getevent.rst.txt | 4 +-
.../applications/system/input/index.rst.txt | 118 ++++++++++++++++++++
.../_sources/components/tools/checkkconfig.rst.txt | 29 ++++-
.../_sources/components/tools/refresh.rst.txt | 25 +++++
.../guides/chip-specific/stm32_ports.rst.txt | 3 +-
.../signal_events_interrupt_handlers.rst.txt | 8 +-
.../concurrency/thread_local_storage.rst.txt | 2 +-
.../_sources/os/drivers/character/serial.rst.txt | 33 +++---
.../arm/stm32n6/boards/stm32n6570-dk/index.rst.txt | 22 ++++
.../_sources/platforms/arm/stm32n6/index.rst.txt | 2 +-
.../reference/user/01_task_control.rst.txt | 18 ++--
.../reference/user/03_task_control.rst.txt | 8 +-
.../_sources/reference/user/07_signals.rst.txt | 15 +--
.../docs/latest/_sources/standards/posix.rst.txt | 18 ++--
.../applications/graphics/input/getevent.html | 4 +-
.../latest/applications/system/input/index.html | 120 ++++++++++++++++++++-
.../docs/latest/components/tools/checkkconfig.html | 29 ++++-
content/docs/latest/components/tools/refresh.html | 20 ++++
.../latest/guides/chip-specific/stm32_ports.html | 20 ++--
.../signal_events_interrupt_handlers.html | 8 +-
.../guides/concurrency/thread_local_storage.html | 2 +-
.../latest/guides/porting/port_bootsequence.html | 8 +-
.../porting/port_relatedkernelconfigrations.html | 8 +-
.../latest/guides/programs/fully_linked_elf.html | 2 +-
.../guides/programs/partially_linked_elf.html | 2 +-
content/docs/latest/objects.inv | Bin 270117 -> 270173 bytes
.../docs/latest/os/drivers/character/serial.html | 33 +++---
.../arm/stm32n6/boards/stm32n6570-dk/index.html | 21 ++++
.../docs/latest/platforms/arm/stm32n6/index.html | 26 ++---
.../latest/reference/user/01_task_control.html | 18 ++--
.../latest/reference/user/03_task_control.html | 8 +-
content/docs/latest/reference/user/07_signals.html | 15 +--
content/docs/latest/searchindex.js | 2 +-
content/docs/latest/standards/posix.html | 20 ++--
34 files changed, 527 insertions(+), 144 deletions(-)
diff --git
a/content/docs/latest/_sources/applications/graphics/input/getevent.rst.txt
b/content/docs/latest/_sources/applications/graphics/input/getevent.rst.txt
index e85e72d393..e8696071d3 100644
--- a/content/docs/latest/_sources/applications/graphics/input/getevent.rst.txt
+++ b/content/docs/latest/_sources/applications/graphics/input/getevent.rst.txt
@@ -77,8 +77,8 @@ The main event loop uses ``poll()`` with a 500 ms timeout to
wait for data on
all open file descriptors. When an event is available, the corresponding read
callback decodes and prints the event structure via ``syslog``.
-``SIGINT`` (``Ctrl+C``) is handled to allow graceful shutdown with proper
-resource cleanup.
+``SIGINT`` (``Ctrl+C``) and ``SIGTERM`` (``kill <pid>``) are handled to allow
+graceful shutdown with proper resource cleanup.
Example Output
==============
diff --git
a/content/docs/latest/_sources/applications/system/input/index.rst.txt
b/content/docs/latest/_sources/applications/system/input/index.rst.txt
index 84d90714ba..a569cbbc78 100644
--- a/content/docs/latest/_sources/applications/system/input/index.rst.txt
+++ b/content/docs/latest/_sources/applications/system/input/index.rst.txt
@@ -1,3 +1,121 @@
====================
``input`` input tool
====================
+
+``input`` is a command-line tool that injects touch, button and mouse wheel
+events through the uinput devices. It is useful for driving graphics
+applications from the shell, for automated UI tests, and for input driver
+bring-up together with :doc:`/applications/graphics/input/getevent`.
+
+The tool is built on the input generator library in
+``apps/graphics/input/generator`` and writes to these devices:
+
+- ``/dev/utouch`` -- touch events (``tap``, ``swipe``, ``drag``)
+- ``/dev/ubutton`` -- button events (``button``)
+- ``/dev/umouse`` -- mouse wheel events (``wheel``, ``scroll``)
+
+Configuration
+=============
+
+Enable the tool in the NuttX configuration. It depends on the uinput
+devices and the input generator library::
+
+ CONFIG_UINPUT_TOUCH=y
+ CONFIG_UINPUT_BUTTONS=y
+ CONFIG_UINPUT_MOUSE=y
+ CONFIG_GRAPHICS_INPUT_GENERATOR=y
+ CONFIG_GRAPHICS_INPUT_TOOL=y
+
+The ``wheel`` and ``scroll`` commands also require::
+
+ CONFIG_INPUT_MOUSE_WHEEL=y
+
+Optional settings:
+
+.. list-table::
+ :header-rows: 1
+
+ * - Option
+ - Default
+ - Description
+ * - ``CONFIG_GRAPHICS_INPUT_TOOL_STACKSIZE``
+ - ``4096``
+ - Stack size for the input task
+ * - ``CONFIG_GRAPHICS_INPUT_TOOL_PRIORITY``
+ - ``110``
+ - Task priority
+ * - ``CONFIG_GRAPHICS_INPUT_TOOL_SCROLL_THRESHOLD``
+ - ``10``
+ - Scroll activation threshold used by ``scroll`` (range 0 to 32766).
+ It should match the threshold of the application that receives the
+ events. Requires ``CONFIG_INPUT_MOUSE_WHEEL``.
+
+Usage
+=====
+
+::
+
+ input <command> [<arg>...]
+
+Coordinates and wheel values are signed 16-bit integers. Durations are in
+milliseconds. An unknown command or an invalid argument prints the usage
+text and the tool exits with a failure status.
+
+``help``
+ Print the list of commands.
+
+``sleep <ms>``
+ Wait for the given time.
+
+``tap <x> <y>``
+ Press at ``(x, y)`` for 50 ms and release.
+
+``swipe <x1> <y1> <x2> <y2> [duration]``
+ Move a touch point from ``(x1, y1)`` to ``(x2, y2)`` in ``duration``
+ milliseconds (default 300), then release.
+
+``drag <x1> <y1> <x2> <y2> [duration]``, ``draganddrop ...``
+ Like ``swipe``, but press for 50 ms before moving and hold for 5 ms
+ before releasing. The default ``duration`` is 500 ms.
+
+``button <buttonvalue> [duration]``
+ Press the buttons in the mask ``buttonvalue`` (decimal or ``0x``
+ hexadecimal) and release them. Without ``duration`` the buttons are held
+ for 100 ms; with ``duration`` they are held for that long (long press).
+
+``wheel <value>``
+ Send a single mouse wheel report with ``value``.
+
+``scroll <value>``, ``scroll --axis SCROLL,<value>``
+ Send a paced sequence of mouse wheel reports for applications that only
+ start scrolling once a threshold is exceeded:
+
+ 1. One activation report of the scroll threshold plus one, in the
+ direction of ``value``. The threshold is
+ ``CONFIG_GRAPHICS_INPUT_TOOL_SCROLL_THRESHOLD``.
+ 2. ``value`` split into steps of ``max(1, |value| / 10)``, with the last
+ step taking the remainder, sent 30 ms apart.
+
+ The activation report is sent in addition to ``value``. ``scroll 0``
+ sends nothing. The ``--axis`` form follows the Android ``input scroll``
+ syntax.
+
+Examples
+========
+
+::
+
+ nsh> input tap 100 200
+ nsh> input swipe 10 10 200 200 300
+ nsh> input button 0x01
+ nsh> input button 0x01 1000
+ nsh> input wheel 5
+ nsh> input scroll 100
+ nsh> input scroll --axis SCROLL,-50
+
+Wheel reports of ``input scroll 100`` with the default threshold, as
+printed by ``getevent -m /dev/umouse``::
+
+ [getevent]: wheel : 11
+ [getevent]: wheel : 10
+ ... (ten reports of 10 in total)
diff --git a/content/docs/latest/_sources/components/tools/checkkconfig.rst.txt
b/content/docs/latest/_sources/components/tools/checkkconfig.rst.txt
index 1ec768f906..cc955e109a 100644
--- a/content/docs/latest/_sources/components/tools/checkkconfig.rst.txt
+++ b/content/docs/latest/_sources/components/tools/checkkconfig.rst.txt
@@ -8,19 +8,25 @@ It can be used to check whether my config changes are what I
expected.
Help message::
$ tools/checkkconfig.py -h
- usage: checkkconfig.py [-h] -f FILE (-s CONFIG VALUE | -d DIFF)
+ usage: checkkconfig.py [-h] [-o OUT_DIR] -f FILE
+ (-s CONFIG [VALUE ...] | -d DIFF)
- optional arguments:
+ Simulate the effects of modifying CONFIG items in NuttX
+
+ options:
-h, --help show this help message and exit
+ -o OUT_DIR, --out_dir OUT_DIR
+ Binary dir for CMake configured
-f FILE, --file FILE Path to the input defconfig file
- -s CONFIG_XXX VALUE, --single CONFIG VALUE
- Analyze single change: CONFIG_NAME y/m/n
+ -s CONFIG [VALUE ...], --set CONFIG [VALUE ...]
+ Analyze multiple changes: CONFIG_NAME1 y/m/n
+ CONFIG_NAME2 y/m/n ...
-d DIFF, --diff DIFF Analyze changes from diff file
example: ./tools/checkkconfig.py -f defconfig -s ELF n
outputs:
- Change report for ELF=n
+ Change report for config changes
Config Option Old New
----------------------------------------------------------------------
BINFMT_LOADABLE y n
@@ -41,3 +47,16 @@ it will bring about the following configuration linkage
changes
It can also parse diff files, which can be used to check the changes of
multiple
configs.
+
+``-s``/``--set`` accepts several ``CONFIG VALUE`` pairs, so the combined
effect of
+multiple changes can be checked at once. A value other than ``y``, ``m`` or
+``n`` is set as is, for example a number or a string::
+
+ $ ./tools/checkkconfig.py -f defconfig -s ELF y TASK_NAME_SIZE 16
+
+CMake builds keep the configuration in the build directory instead of the
+top-level NuttX directory. Pass that directory with ``-o``/``--out_dir`` to
+analyze a CMake configuration::
+
+ $ cmake -B build -DBOARD_CONFIG=sim:nsh -GNinja
+ $ ./tools/checkkconfig.py -o build -f build/.config -s ELF y
diff --git a/content/docs/latest/_sources/components/tools/refresh.rst.txt
b/content/docs/latest/_sources/components/tools/refresh.rst.txt
index 81fcf6d6d2..eba49b7360 100644
--- a/content/docs/latest/_sources/components/tools/refresh.rst.txt
+++ b/content/docs/latest/_sources/components/tools/refresh.rst.txt
@@ -44,6 +44,8 @@ Help is also available:
Do not prompt for new default selections; accept all recommended
default values
--nocopy
Do not copy defconfig from nuttx/boards/<board>/configs to
nuttx/.config
+ --cmake
+ Use CMake refresh target instead of make refresh to refresh the
defconfig
--help
Show this help message and exit
<board>
@@ -89,6 +91,23 @@ The steps to refresh the configurations and/or files given
to ``refresh.sh`` are
5. Restore the ``.config`` and ``Make.defs`` files from step 1.
+With the ``--cmake`` option, the configuration is refreshed with the CMake
build
+instead, so it also works for board configurations that have no ``Make.defs``
+file. For each configuration, ``refresh.sh``:
+
+1. Configures a temporary CMake build directory ``refresh/`` in the top-level
+ NuttX directory with ``cmake -B refresh -DBOARD_CONFIG=<config> -GNinja``.
+
+2. Runs ``cmake --build refresh -t refreshsilent``, which updates the
+ configuration with the default values and creates the new defconfig file.
+
+3. Copies the new defconfig file out of ``refresh/``, removes ``refresh/``, and
+ compares and saves the new defconfig file in the same way as the Make-based
+ refresh.
+
+The ``.config`` and ``Make.defs`` files in the top-level directory are not used
+or modified in this mode.
+
Usage examples
--------------
@@ -136,3 +155,9 @@ configuration subdirectory:
.. code:: console
$ ./tools/refresh.sh --defaults
boards/arm/stm32f1/stm32f103-minimum/configs/nsh
+
+Update the `nsh` config from the ``qemu-armv7a`` board with the CMake build:
+
+.. code:: console
+
+ $ ./tools/refresh.sh --silent --cmake qemu-armv7a:nsh
diff --git
a/content/docs/latest/_sources/guides/chip-specific/stm32_ports.rst.txt
b/content/docs/latest/_sources/guides/chip-specific/stm32_ports.rst.txt
index 33d9009a35..01a75fe6bd 100644
--- a/content/docs/latest/_sources/guides/chip-specific/stm32_ports.rst.txt
+++ b/content/docs/latest/_sources/guides/chip-specific/stm32_ports.rst.txt
@@ -662,7 +662,7 @@ QUADSPI to be done
arch/arm/src/stm32h7/stm32_qspi.c
RCC to be done arch/arm/src/stm32h7/stm32_rcc.c
RNG v1 arch/arm/src/common/stm32/stm32_rng_v1.c
RTC to be done arch/arm/src/stm32h7/stm32_rtc.c
-SDMMC to be done arch/arm/src/stm32h7/stm32_sdmmc.c
+SDMMC v2 arch/arm/src/common/stm32/stm32_sdmmc_v2.c
SPI/I2S to be done arch/arm/src/stm32h7/stm32_spi.c
TIM v2, H7RS v3 arch/arm/src/common/stm32/stm32_tim.c
USART/LPUART v4 arch/arm/src/stm32h7/stm32_serial.c
@@ -785,6 +785,7 @@ PWR n6 arch/arm/src/stm32n6/stm32_pwr.c
RCC n6 arch/arm/src/stm32n6/stm32n6xx_rcc.c
RNG v1 arch/arm/src/common/stm32/stm32_rng_v1.c
RTC M33M55 v1 arch/arm/src/common/stm32/stm32_rtcc_m33m55_v1.c
+SDMMC v2 arch/arm/src/common/stm32/stm32_sdmmc_v2.c
SPI/I2S v5 arch/arm/src/common/stm32/stm32_spi_v5.c
TIM v3 arch/arm/src/common/stm32/stm32_tim.c
USART/LPUART M33M55 v3 arch/arm/src/common/stm32/stm32_serial_m33m55_v3.c
diff --git
a/content/docs/latest/_sources/guides/concurrency/signal_events_interrupt_handlers.rst.txt
b/content/docs/latest/_sources/guides/concurrency/signal_events_interrupt_handlers.rst.txt
index e0611efba8..4493ff20ce 100644
---
a/content/docs/latest/_sources/guides/concurrency/signal_events_interrupt_handlers.rst.txt
+++
b/content/docs/latest/_sources/guides/concurrency/signal_events_interrupt_handlers.rst.txt
@@ -220,7 +220,7 @@ about it. It is sometimes a pain because you have to
remember to
handle the ``EINTR`` return value even when you don't care about it.
The POSIX signal definition includes some support that would make this
-easier for you. This support is not currently implemented in NuttX.
+easier for you.
The ``kill()`` interface for example
(http://pubs.opengroup.org/onlinepubs/009695399/functions/kill.html)
supports this behavior:
@@ -239,9 +239,9 @@ an unspecified set of system processes) whose process group
ID is equal to
the absolute value of pid, and for which the process has permission to send
a signal."
-NuttX does not currently support process groups. But that might be a good
-RTOS extension. If you and others think that would be useful I could
-probably add the basics of such a feature in a day or so.
+With ``CONFIG_SCHED_PROCESS_GROUPS``, NuttX supports process groups: a pid
+of 0 or less than -1 sends the signal to each process of the process group.
+A pid of -1 (all processes) is not supported.
``poll()``
==========
diff --git
a/content/docs/latest/_sources/guides/concurrency/thread_local_storage.rst.txt
b/content/docs/latest/_sources/guides/concurrency/thread_local_storage.rst.txt
index 5dd94fa117..3db3738f40 100644
---
a/content/docs/latest/_sources/guides/concurrency/thread_local_storage.rst.txt
+++
b/content/docs/latest/_sources/guides/concurrency/thread_local_storage.rst.txt
@@ -44,6 +44,6 @@ Then you can see ``--disable-tls`` in the output, which means
that your compiler
In this case, you can still use the thread local relative keyword, but it
would be implemented by libgcc's emutls.
-NuttX's libc provides its own version (``CONFIG_TLS_EMUTLS``, set for the GCC
and clang toolchains when libgcc is the builtin library,
``CONFIG_BUILTIN_TOOLCHAIN``; the sim has it with GCC and the GNU linker, as on
Linux and MinGW), and the link sends the calls to ``__emutls_get_address()``
there with ``--wrap``. A libgcc built with the single thread model (``Thread
model: single`` above) keeps one copy of each variable for the whole program;
with the libc version, each thread gets its o [...]
+NuttX's libc provides its own version (``CONFIG_TLS_EMUTLS``, set for the GCC
and clang toolchains when libgcc is the builtin library,
``CONFIG_BUILTIN_TOOLCHAIN``; the sim has it with GCC and the GNU linker, as on
Linux and MinGW), and the link sends the calls to ``__emutls_get_address()``
there with ``--wrap``. A libgcc built with the single thread model (``Thread
model: single`` above) keeps one copy of each variable for the whole program;
with the libc version, each thread gets its o [...]
The image, the modules and the programs of a kernel build are linked with
``--wrap``; code loaded at run time finds the libc version in the system symbol
table (``CONFIG_EXECFUNCS_SYSTEM_SYMTAB``).
diff --git a/content/docs/latest/_sources/os/drivers/character/serial.rst.txt
b/content/docs/latest/_sources/os/drivers/character/serial.rst.txt
index 2f338ea8c5..0d5cd7daff 100644
--- a/content/docs/latest/_sources/os/drivers/character/serial.rst.txt
+++ b/content/docs/latest/_sources/os/drivers/character/serial.rst.txt
@@ -38,13 +38,15 @@ Serial Device Drivers
- **Job control / controlling terminal**. When ``CONFIG_TTY_SIGINT``
or ``CONFIG_TTY_SIGTSTP`` is enabled, the TTY layer can generate
``SIGINT`` (Ctrl-C) and ``SIGTSTP`` (Ctrl-Z) for a foreground task.
- NuttX does not implement POSIX sessions or process groups, so the
- foreground process group is collapsed onto a single PID stored in
- the driver (``pgrp == pid``, one member per group); the signal is
- delivered with ``nxsig_kill(pid, signo)``. The driver discards the
- character that sends the signal, so the task does not read it.
+ The driver keeps the ID of the foreground process group. With
+ ``CONFIG_SCHED_PROCESS_GROUPS``, each process of that process group
+ gets the signal. An ID that no process group has is a process ID
+ (NSH sets one with ``TIOCSCTTY``): that process gets the signal.
+ Without the option, a process group is one process, and the process
+ with that ID gets the signal. The driver discards the character
+ that sends the signal, so the task does not read it.
- The following terminal ``ioctl`` commands manage this PID:
+ The following terminal ``ioctl`` commands manage this ID:
- ``TIOCSCTTY`` makes the terminal the controlling terminal. The
``arg`` is treated as a flag: a value of ``0`` selects the
@@ -59,20 +61,23 @@ Serial Device Drivers
``tcsetpgrp()`` passes it, ``arg`` points to the PID (``pid_t *``);
a ``NULL`` pointer or a PID that is not positive gives ``EINVAL``.
- The C library exposes these through ``tcgetpgrp()``, ``tcsetpgrp()``,
- ``tcgetsid()``, ``setsid()``, ``getsid()`` and ``setpgid()``. A process
- group is one process, so ``kill(-pgrp, signo)`` and ``killpg()`` send
- the signal to the process ``pgrp``, and TTY signals go to the single
- foreground PID.
+ The C library exposes these through ``tcgetpgrp()``, ``tcsetpgrp()``
+ and ``tcgetsid()``. With ``CONFIG_SCHED_PROCESS_GROUPS``, ``setpgid()``,
+ ``getpgid()``, ``setsid()`` and ``getsid()`` keep the process groups
+ and the sessions of POSIX, and ``kill(-pgrp, signo)`` and ``killpg()``
+ send the signal to each process of the process group. Without it, a
+ process group is one process: ``setpgid()`` accepts only the process
+ ID as the process group ID, and ``kill(-pgrp, signo)`` and
+ ``killpg()`` send the signal to the process ``pgrp``.
- **Window size**. ``TIOCGWINSZ`` returns the terminal size in a
``struct winsize`` and ``TIOCSWINSZ`` sets it. The size is 0 rows
and 0 columns until a program sets it (for example ``openpty()`` or
a remote login server). A change of the size sends ``SIGWINCH`` to
- the foreground PID when ``CONFIG_TTY_SIGINT`` or
+ the foreground process group, as above, when ``CONFIG_TTY_SIGINT`` or
``CONFIG_TTY_SIGTSTP`` is enabled. A pseudo-terminal keeps one size
- for the master and the slave; the signal goes to the foreground PID
- of the slave.
+ for the master and the slave; the signal goes to the foreground
+ process group of the slave.
- **User Access**. Serial drivers are, ultimately, normal
`character drivers <#chardrivers>`__ and are accessed as other
diff --git
a/content/docs/latest/_sources/platforms/arm/stm32n6/boards/stm32n6570-dk/index.rst.txt
b/content/docs/latest/_sources/platforms/arm/stm32n6/boards/stm32n6570-dk/index.rst.txt
index 9d67906bf7..bb878f9b73 100644
---
a/content/docs/latest/_sources/platforms/arm/stm32n6/boards/stm32n6570-dk/index.rst.txt
+++
b/content/docs/latest/_sources/platforms/arm/stm32n6/boards/stm32n6570-dk/index.rst.txt
@@ -191,6 +191,22 @@ IMX335 held in reset (PC8) and registers the sensor as the
V4L2 depth
camera ``/dev/video1`` (Z16, 8x8 or 4x4). INT uses EXTI0, so the TAMP
button has no interrupt when the sensor is enabled.
+microSD
+=======
+
+The microSD slot is on SDMMC2 (4-bit, IDMA): PC2 CK, PC3 CMD, PC4-PC5 D0-D1,
+PC0 D2, PE4 D3 (AF11), card detect PN12 (low with a card) and card power
+enable PQ7 (high). The kernel clock is IC4 = 200 MHz, giving 400 kHz for
+identification and 25 MHz for transfers. The card is ``/dev/mmcsd0``;
+insertion and removal are reported through the card detect interrupt.
+With a FAT formatted card::
+
+ nsh> mount -t vfat /dev/mmcsd0 /mnt
+ nsh> echo hello > /mnt/test.txt
+ nsh> cat /mnt/test.txt
+ nsh> dd if=/dev/zero of=/mnt/big.bin bs=4096 count=256
+ nsh> umount /mnt
+
Clocking
========
@@ -233,3 +249,9 @@ lvgl
``fb`` plus the touch controller, LVGL and its widgets demo. Start it
with ``lvgldemo &``. The image is close to the 511 KiB limit of the boot
ROM, so LVGL logging and extra fonts are left out.
+
+sdcard
+------
+
+NuttShell with the microSD slot on SDMMC2 and the FAT file system, see
+`microSD`_.
diff --git a/content/docs/latest/_sources/platforms/arm/stm32n6/index.rst.txt
b/content/docs/latest/_sources/platforms/arm/stm32n6/index.rst.txt
index 1ca2c7c685..75da5de92e 100644
--- a/content/docs/latest/_sources/platforms/arm/stm32n6/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/arm/stm32n6/index.rst.txt
@@ -41,6 +41,7 @@ RCC Yes HSI/HSE, PLL1-4, IC1-20, bus prescalers
and kernel
RNG Yes Through the common driver.
RTC Yes Calendar, sub-seconds, Alarm A/B and wakeup timer
through the common RTC driver.
+SDMMC Yes SDMMC1-2 through the common IDMA SDMMC driver.
SPI Yes SPI1-6 through the common SPI v5 driver, master
mode, optional GPDMA.
USART Yes USART1-3, UART4-5, USART6, UART7-9, USART10 and
@@ -53,7 +54,6 @@ LPTIM No
MPU No
NPU No
SAI No
-SDMMC No
TIM No
USB No
XSPI No
diff --git
a/content/docs/latest/_sources/reference/user/01_task_control.rst.txt
b/content/docs/latest/_sources/reference/user/01_task_control.rst.txt
index 91ce4c53af..94682edf49 100644
--- a/content/docs/latest/_sources/reference/user/01_task_control.rst.txt
+++ b/content/docs/latest/_sources/reference/user/01_task_control.rst.txt
@@ -633,8 +633,11 @@ Functions
``spawn.h``. It will contains these attributes, not all of which are
supported by NuttX:
- - ``POSIX_SPAWN_SETPGROUP``: Setting of the new task's process group
- is not supported. NuttX does not support process groups.
+ - ``POSIX_SPAWN_SETPGROUP``: The new task joins the process group of
+ ``posix_spawnattr_setpgroup()``, or a new process group if it is
+ ``0`` (with ``CONFIG_SCHED_PROCESS_GROUPS``, else ignored).
+ - ``POSIX_SPAWN_SETSID``: The new task is the leader of a new
+ session (with ``CONFIG_SCHED_PROCESS_GROUPS``, else ignored).
- ``POSIX_SPAWN_SETSCHEDPARAM``: Set new tasks priority to the
``sched_param`` value.
- ``POSIX_SPAWN_SETSCHEDULER``: Set the new task's scheduler policy
@@ -679,8 +682,8 @@ Functions
``CONFIG_LIBC_ENVPATH`` is defined, then only ``posix_spawnp()``
behavior is supported; otherwise, only ``posix_spawn()`` behavior is
supported.
- - Process groups are not supported (See ``POSIX_SPAWN_SETPGROUP``
- above).
+ - Process groups need ``CONFIG_SCHED_PROCESS_GROUPS`` (See
+ ``POSIX_SPAWN_SETPGROUP`` above).
- Effective user IDs are not supported (See ``POSIX_SPAWN_RESETIDS``
above).
- Signal default actions cannot be modified in the newly task executed
@@ -928,8 +931,11 @@ Functions
``spawn.h``. It will contains these attributes, not all of which are
supported by NuttX:
- - ``POSIX_SPAWN_SETPGROUP``: Setting of the new task's process group
- is not supported. NuttX does not support process groups.
+ - ``POSIX_SPAWN_SETPGROUP``: The new task joins the process group of
+ ``posix_spawnattr_setpgroup()``, or a new process group if it is
+ ``0`` (with ``CONFIG_SCHED_PROCESS_GROUPS``, else ignored).
+ - ``POSIX_SPAWN_SETSID``: The new task is the leader of a new
+ session (with ``CONFIG_SCHED_PROCESS_GROUPS``, else ignored).
- ``POSIX_SPAWN_SETSCHEDPARAM``: Set new tasks priority to the
``sched_param`` value.
- ``POSIX_SPAWN_SETSCHEDULER``: Set the new task's scheduler policy
diff --git
a/content/docs/latest/_sources/reference/user/03_task_control.rst.txt
b/content/docs/latest/_sources/reference/user/03_task_control.rst.txt
index fb8dd1a620..4e7b35de59 100644
--- a/content/docs/latest/_sources/reference/user/03_task_control.rst.txt
+++ b/content/docs/latest/_sources/reference/user/03_task_control.rst.txt
@@ -183,8 +183,8 @@ Functions
for any task to complete execution. With
``CONFIG_SCHED_HAVE_PARENT``, ``waitpid()`` will use ``SIGCHLD`` and
can, therefore, wait for any child of the parent to complete. The
- implementation is incomplete in either case, however: NuttX does not
- support any concept of process groups. Nor does NuttX retain the
+ implementation is incomplete in either case, however: it does not
+ support process groups. Nor does NuttX retain the
status of exited tasks so if ``waitpid()`` is called after a task has
exited, then no status will be available. The options argument is
currently ignored.
@@ -323,8 +323,8 @@ Functions
little more compliant to specifications. ``waitpid()`` simply
supports waiting a specific child task (``P_PID`` or for any child
task ``P_ALL`` to complete execution. ``SIGCHLD`` is used. The
- implementation is incomplete in either case, however: NuttX does not
- support any concept of process groups. Nor does NuttX retain the
+ implementation is incomplete in either case, however: it does not
+ support process groups. Nor does NuttX retain the
status of exited tasks so if ``waitpid()`` is called after a task has
exited, then no status will be available. The options argument is
currently ignored.
diff --git a/content/docs/latest/_sources/reference/user/07_signals.rst.txt
b/content/docs/latest/_sources/reference/user/07_signals.rst.txt
index 75ff0146e1..cae32b5807 100644
--- a/content/docs/latest/_sources/reference/user/07_signals.rst.txt
+++ b/content/docs/latest/_sources/reference/user/07_signals.rst.txt
@@ -543,9 +543,12 @@ Equivalent to sigtimedwait() with a NULL timeout
parameter. (see below).
:param pid: The id of the task to receive the signal. The POSIX
``kill()`` specification encodes process group information as zero
- and negative pid values. A process group is one process in NuttX:
- ``0`` is the caller and ``-pid`` is the process ``pid``. ``-1`` (all
- processes) is not supported and gives ``ENOSYS``.
+ and negative pid values. With ``CONFIG_SCHED_PROCESS_GROUPS``, ``0``
+ is the process group of the caller and ``-pid`` is the process group
+ ``pid``: each process of the group that the caller may control gets
+ the signal. Without it, a process group is one process: ``0`` is the
+ caller and ``-pid`` is the process ``pid``. ``-1`` (all processes) is
+ not supported and gives ``ENOSYS``.
:param signo: The signal number to send. If signo is zero, no signal is
sent, but all error checking is performed.
@@ -556,9 +559,9 @@ Equivalent to sigtimedwait() with a NULL timeout parameter.
(see below).
- Default action is to ignore signals.
- Signals are processed one at a time in order
- - A process group is one process, so a signal to a process group goes
- to that process. A signal to all processes (``pid`` -1) is not
- supported.
+ - Without ``CONFIG_SCHED_PROCESS_GROUPS``, a process group is one
+ process, so a signal to a process group goes to that process. A
+ signal to all processes (``pid`` -1) is not supported.
.. c:function:: int pause(void);
diff --git a/content/docs/latest/_sources/standards/posix.rst.txt
b/content/docs/latest/_sources/standards/posix.rst.txt
index 35cab1758a..ff66792492 100644
--- a/content/docs/latest/_sources/standards/posix.rst.txt
+++ b/content/docs/latest/_sources/standards/posix.rst.txt
@@ -221,7 +221,7 @@ Units of Functionality Requirements:
+------------------------------+---------+--------------------------------+
| `POSIX_FILE_SYSTEM_EXT`_ | Yes | |
+------------------------------+---------+--------------------------------+
-| `POSIX_JOB_CONTROL`_ | 1/4 | |
+| `POSIX_JOB_CONTROL`_ | Yes | ``CONFIG_SCHED_PROCESS_GROUPS``|
+------------------------------+---------+--------------------------------+
| `POSIX_REGEXP`_ | Yes | |
+------------------------------+---------+--------------------------------+
@@ -1444,13 +1444,13 @@ Multiple Processes:
+--------------------------------+---------+
| :c:func:`getrlimit` | Yes |
+--------------------------------+---------+
-| getsid() | No |
+| getsid() | Yes |
+--------------------------------+---------+
| :c:func:`quick_exit` | Yes |
+--------------------------------+---------+
| :c:func:`setrlimit` | Yes |
+--------------------------------+---------+
-| setsid() | No |
+| setsid() | Yes |
+--------------------------------+---------+
| :c:func:`sleep` | Yes |
+--------------------------------+---------+
@@ -1894,11 +1894,11 @@ Job Control:
+--------------------------------+---------+
| API | Support |
+================================+=========+
-| setpgid() | No |
+| setpgid() | Yes |
+--------------------------------+---------+
-| tcgetpgrp() | No |
+| tcgetpgrp() | Yes |
+--------------------------------+---------+
-| tcsetpgrp() | No |
+| tcsetpgrp() | Yes |
+--------------------------------+---------+
| :c:func:`tcgetsid` | Yes |
+--------------------------------+---------+
@@ -2386,7 +2386,7 @@ XSI Multiple Process:
+--------------------------------+---------+
| :c:func:`getrusage` | Yes |
+--------------------------------+---------+
-| getsid() | No |
+| getsid() | Yes |
+--------------------------------+---------+
| :c:func:`nice` | Yes |
+--------------------------------+---------+
@@ -3037,7 +3037,7 @@ Depends on ``CONFIG_BUILD_KERNEL``.
+---------------------------------------------+---------+
| :c:func:`posix_spawnattr_getflags` | Yes |
+---------------------------------------------+---------+
-| :c:func:`posix_spawnattr_getpgroup` | No |
+| :c:func:`posix_spawnattr_getpgroup` | Yes |
+---------------------------------------------+---------+
| :c:func:`posix_spawnattr_getsigdefault` | No |
+---------------------------------------------+---------+
@@ -3047,7 +3047,7 @@ Depends on ``CONFIG_BUILD_KERNEL``.
+---------------------------------------------+---------+
| :c:func:`posix_spawnattr_setflags` | Yes |
+---------------------------------------------+---------+
-| :c:func:`posix_spawnattr_setpgroup` | No |
+| :c:func:`posix_spawnattr_setpgroup` | Yes |
+---------------------------------------------+---------+
| :c:func:`posix_spawnattr_setsigdefault` | No |
+---------------------------------------------+---------+
diff --git a/content/docs/latest/applications/graphics/input/getevent.html
b/content/docs/latest/applications/graphics/input/getevent.html
index cca7bdfe31..f74e681d7b 100644
--- a/content/docs/latest/applications/graphics/input/getevent.html
+++ b/content/docs/latest/applications/graphics/input/getevent.html
@@ -310,8 +310,8 @@ devices matching known input device name patterns (<code
class="docutils literal
<p>The main event loop uses <code class="docutils literal notranslate"><span
class="pre">poll()</span></code> with a 500 ms timeout to wait for data on
all open file descriptors. When an event is available, the corresponding read
callback decodes and prints the event structure via <code class="docutils
literal notranslate"><span class="pre">syslog</span></code>.</p>
-<p><code class="docutils literal notranslate"><span
class="pre">SIGINT</span></code> (<code class="docutils literal
notranslate"><span class="pre">Ctrl+C</span></code>) is handled to allow
graceful shutdown with proper
-resource cleanup.</p>
+<p><code class="docutils literal notranslate"><span
class="pre">SIGINT</span></code> (<code class="docutils literal
notranslate"><span class="pre">Ctrl+C</span></code>) and <code class="docutils
literal notranslate"><span class="pre">SIGTERM</span></code> (<code
class="docutils literal notranslate"><span class="pre">kill</span> <span
class="pre"><pid></span></code>) are handled to allow
+graceful shutdown with proper resource cleanup.</p>
</section>
<section id="example-output">
<h2>Example Output<a class="headerlink" href="#example-output"
title="Permalink to this heading"></a></h2>
diff --git a/content/docs/latest/applications/system/input/index.html
b/content/docs/latest/applications/system/input/index.html
index 469c015d6a..9299fb79b6 100644
--- a/content/docs/latest/applications/system/input/index.html
+++ b/content/docs/latest/applications/system/input/index.html
@@ -195,7 +195,12 @@
<li class="toctree-l3"><a class="reference internal"
href="../hexed/index.html"><code class="docutils literal notranslate"><span
class="pre">hexed</span></code> Hex editor</a></li>
<li class="toctree-l3"><a class="reference internal"
href="../hostname/index.html"><code class="docutils literal notranslate"><span
class="pre">hostname</span></code> “hostname” command</a></li>
<li class="toctree-l3"><a class="reference internal"
href="../i2c/index.html"><code class="docutils literal notranslate"><span
class="pre">i2c</span></code> I2C Tool</a></li>
-<li class="toctree-l3 current"><a class="current reference internal"
href="#"><code class="docutils literal notranslate"><span
class="pre">input</span></code> input tool</a></li>
+<li class="toctree-l3 current"><a class="current reference internal"
href="#"><code class="docutils literal notranslate"><span
class="pre">input</span></code> input tool</a><ul>
+<li class="toctree-l4"><a class="reference internal"
href="#configuration">Configuration</a></li>
+<li class="toctree-l4"><a class="reference internal"
href="#usage">Usage</a></li>
+<li class="toctree-l4"><a class="reference internal"
href="#examples">Examples</a></li>
+</ul>
+</li>
<li class="toctree-l3"><a class="reference internal"
href="../ip6tables/index.html"><code class="docutils literal notranslate"><span
class="pre">ip6tables</span></code> IPv6 firewall</a></li>
<li class="toctree-l3"><a class="reference internal"
href="../iptables/index.html"><code class="docutils literal notranslate"><span
class="pre">iptables</span></code> IPv4 firewall</a></li>
<li class="toctree-l3"><a class="reference internal"
href="../kbd/index.html"><code class="docutils literal notranslate"><span
class="pre">kbd</span></code> Keyboard dump and injection</a></li>
@@ -293,6 +298,119 @@
<section id="input-input-tool">
<h1><code class="docutils literal notranslate"><span
class="pre">input</span></code> input tool<a class="headerlink"
href="#input-input-tool" title="Permalink to this heading"></a></h1>
+<p><code class="docutils literal notranslate"><span
class="pre">input</span></code> is a command-line tool that injects touch,
button and mouse wheel
+events through the uinput devices. It is useful for driving graphics
+applications from the shell, for automated UI tests, and for input driver
+bring-up together with <a class="reference internal"
href="../../graphics/input/getevent.html"><span class="doc">getevent Input
Event Monitor</span></a>.</p>
+<p>The tool is built on the input generator library in
+<code class="docutils literal notranslate"><span
class="pre">apps/graphics/input/generator</span></code> and writes to these
devices:</p>
+<ul class="simple">
+<li><p><code class="docutils literal notranslate"><span
class="pre">/dev/utouch</span></code> – touch events (<code class="docutils
literal notranslate"><span class="pre">tap</span></code>, <code class="docutils
literal notranslate"><span class="pre">swipe</span></code>, <code
class="docutils literal notranslate"><span
class="pre">drag</span></code>)</p></li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">/dev/ubutton</span></code> – button events (<code class="docutils
literal notranslate"><span class="pre">button</span></code>)</p></li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">/dev/umouse</span></code> – mouse wheel events (<code
class="docutils literal notranslate"><span class="pre">wheel</span></code>,
<code class="docutils literal notranslate"><span
class="pre">scroll</span></code>)</p></li>
+</ul>
+<section id="configuration">
+<h2>Configuration<a class="headerlink" href="#configuration" title="Permalink
to this heading"></a></h2>
+<p>Enable the tool in the NuttX configuration. It depends on the uinput
+devices and the input generator library:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>CONFIG_UINPUT_TOUCH=y
+CONFIG_UINPUT_BUTTONS=y
+CONFIG_UINPUT_MOUSE=y
+CONFIG_GRAPHICS_INPUT_GENERATOR=y
+CONFIG_GRAPHICS_INPUT_TOOL=y
+</pre></div>
+</div>
+<p>The <code class="docutils literal notranslate"><span
class="pre">wheel</span></code> and <code class="docutils literal
notranslate"><span class="pre">scroll</span></code> commands also require:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>CONFIG_INPUT_MOUSE_WHEEL=y
+</pre></div>
+</div>
+<p>Optional settings:</p>
+<table class="docutils align-default">
+<thead>
+<tr class="row-odd"><th class="head"><p>Option</p></th>
+<th class="head"><p>Default</p></th>
+<th class="head"><p>Description</p></th>
+</tr>
+</thead>
+<tbody>
+<tr class="row-even"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_GRAPHICS_INPUT_TOOL_STACKSIZE</span></code></p></td>
+<td><p><code class="docutils literal notranslate"><span
class="pre">4096</span></code></p></td>
+<td><p>Stack size for the input task</p></td>
+</tr>
+<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_GRAPHICS_INPUT_TOOL_PRIORITY</span></code></p></td>
+<td><p><code class="docutils literal notranslate"><span
class="pre">110</span></code></p></td>
+<td><p>Task priority</p></td>
+</tr>
+<tr class="row-even"><td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_GRAPHICS_INPUT_TOOL_SCROLL_THRESHOLD</span></code></p></td>
+<td><p><code class="docutils literal notranslate"><span
class="pre">10</span></code></p></td>
+<td><p>Scroll activation threshold used by <code class="docutils literal
notranslate"><span class="pre">scroll</span></code> (range 0 to 32766).
+It should match the threshold of the application that receives the
+events. Requires <code class="docutils literal notranslate"><span
class="pre">CONFIG_INPUT_MOUSE_WHEEL</span></code>.</p></td>
+</tr>
+</tbody>
+</table>
+</section>
+<section id="usage">
+<h2>Usage<a class="headerlink" href="#usage" title="Permalink to this
heading"></a></h2>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>input <command> [<arg>...]
+</pre></div>
+</div>
+<p>Coordinates and wheel values are signed 16-bit integers. Durations are in
+milliseconds. An unknown command or an invalid argument prints the usage
+text and the tool exits with a failure status.</p>
+<dl>
+<dt><code class="docutils literal notranslate"><span
class="pre">help</span></code></dt><dd><p>Print the list of commands.</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">sleep</span>
<span class="pre"><ms></span></code></dt><dd><p>Wait for the given
time.</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">tap</span>
<span class="pre"><x></span> <span
class="pre"><y></span></code></dt><dd><p>Press at <code class="docutils
literal notranslate"><span class="pre">(x,</span> <span
class="pre">y)</span></code> for 50 ms and release.</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">swipe</span>
<span class="pre"><x1></span> <span class="pre"><y1></span> <span
class="pre"><x2></span> <span class="pre"><y2></span> <span
class="pre">[duration]</span></code></dt><dd><p>Move a touch point from <code
class="docutils literal notranslate"><span class="pre">(x1,</span> <span
class="pre">y1)</span></code> to <code class="docutils literal
notranslate"><span class="pre">(x2,</span> <span c [...]
+milliseconds (default 300), then release.</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">drag</span>
<span class="pre"><x1></span> <span class="pre"><y1></span> <span
class="pre"><x2></span> <span class="pre"><y2></span> <span
class="pre">[duration]</span></code>, <code class="docutils literal
notranslate"><span class="pre">draganddrop</span> <span
class="pre">...</span></code></dt><dd><p>Like <code class="docutils literal
notranslate"><span class="pre">swipe</span></code>, but press for [...]
+before releasing. The default <code class="docutils literal notranslate"><span
class="pre">duration</span></code> is 500 ms.</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">button</span>
<span class="pre"><buttonvalue></span> <span
class="pre">[duration]</span></code></dt><dd><p>Press the buttons in the mask
<code class="docutils literal notranslate"><span
class="pre">buttonvalue</span></code> (decimal or <code class="docutils literal
notranslate"><span class="pre">0x</span></code>
+hexadecimal) and release them. Without <code class="docutils literal
notranslate"><span class="pre">duration</span></code> the buttons are held
+for 100 ms; with <code class="docutils literal notranslate"><span
class="pre">duration</span></code> they are held for that long (long press).</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">wheel</span>
<span class="pre"><value></span></code></dt><dd><p>Send a single mouse
wheel report with <code class="docutils literal notranslate"><span
class="pre">value</span></code>.</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">scroll</span>
<span class="pre"><value></span></code>, <code class="docutils literal
notranslate"><span class="pre">scroll</span> <span class="pre">--axis</span>
<span class="pre">SCROLL,<value></span></code></dt><dd><p>Send a paced
sequence of mouse wheel reports for applications that only
+start scrolling once a threshold is exceeded:</p>
+<ol class="arabic simple">
+<li><p>One activation report of the scroll threshold plus one, in the
+direction of <code class="docutils literal notranslate"><span
class="pre">value</span></code>. The threshold is
+<code class="docutils literal notranslate"><span
class="pre">CONFIG_GRAPHICS_INPUT_TOOL_SCROLL_THRESHOLD</span></code>.</p></li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">value</span></code> split into steps of <code class="docutils
literal notranslate"><span class="pre">max(1,</span> <span
class="pre">|value|</span> <span class="pre">/</span> <span
class="pre">10)</span></code>, with the last
+step taking the remainder, sent 30 ms apart.</p></li>
+</ol>
+<p>The activation report is sent in addition to <code class="docutils literal
notranslate"><span class="pre">value</span></code>. <code class="docutils
literal notranslate"><span class="pre">scroll</span> <span
class="pre">0</span></code>
+sends nothing. The <code class="docutils literal notranslate"><span
class="pre">--axis</span></code> form follows the Android <code class="docutils
literal notranslate"><span class="pre">input</span> <span
class="pre">scroll</span></code>
+syntax.</p>
+</dd>
+</dl>
+</section>
+<section id="examples">
+<h2>Examples<a class="headerlink" href="#examples" title="Permalink to this
heading"></a></h2>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>nsh> input tap 100 200
+nsh> input swipe 10 10 200 200 300
+nsh> input button 0x01
+nsh> input button 0x01 1000
+nsh> input wheel 5
+nsh> input scroll 100
+nsh> input scroll --axis SCROLL,-50
+</pre></div>
+</div>
+<p>Wheel reports of <code class="docutils literal notranslate"><span
class="pre">input</span> <span class="pre">scroll</span> <span
class="pre">100</span></code> with the default threshold, as
+printed by <code class="docutils literal notranslate"><span
class="pre">getevent</span> <span class="pre">-m</span> <span
class="pre">/dev/umouse</span></code>:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>[getevent]: wheel : 11
+[getevent]: wheel : 10
+... (ten reports of 10 in total)
+</pre></div>
+</div>
+</section>
</section>
diff --git a/content/docs/latest/components/tools/checkkconfig.html
b/content/docs/latest/components/tools/checkkconfig.html
index d3fc3cfc39..66b7fa6219 100644
--- a/content/docs/latest/components/tools/checkkconfig.html
+++ b/content/docs/latest/components/tools/checkkconfig.html
@@ -246,19 +246,25 @@
It can be used to check whether my config changes are what I expected.</p>
<p>Help message:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>$ tools/checkkconfig.py -h
-usage: checkkconfig.py [-h] -f FILE (-s CONFIG VALUE | -d DIFF)
+usage: checkkconfig.py [-h] [-o OUT_DIR] -f FILE
+ (-s CONFIG [VALUE ...] | -d DIFF)
-optional arguments:
+Simulate the effects of modifying CONFIG items in NuttX
+
+options:
-h, --help show this help message and exit
+ -o OUT_DIR, --out_dir OUT_DIR
+ Binary dir for CMake configured
-f FILE, --file FILE Path to the input defconfig file
- -s CONFIG_XXX VALUE, --single CONFIG VALUE
- Analyze single change: CONFIG_NAME y/m/n
+ -s CONFIG [VALUE ...], --set CONFIG [VALUE ...]
+ Analyze multiple changes: CONFIG_NAME1 y/m/n
+ CONFIG_NAME2 y/m/n ...
-d DIFF, --diff DIFF Analyze changes from diff file
example: ./tools/checkkconfig.py -f defconfig -s ELF n
outputs:
-Change report for ELF=n
+Change report for config changes
Config Option Old New
----------------------------------------------------------------------
BINFMT_LOADABLE y n
@@ -279,6 +285,19 @@ if I turn off ELF in defconfig at this time,
it will bring about the following configuration linkage changes</p>
<p>It can also parse diff files, which can be used to check the changes of
multiple
configs.</p>
+<p><code class="docutils literal notranslate"><span
class="pre">-s</span></code>/<code class="docutils literal notranslate"><span
class="pre">--set</span></code> accepts several <code class="docutils literal
notranslate"><span class="pre">CONFIG</span> <span
class="pre">VALUE</span></code> pairs, so the combined effect of
+multiple changes can be checked at once. A value other than <code
class="docutils literal notranslate"><span class="pre">y</span></code>, <code
class="docutils literal notranslate"><span class="pre">m</span></code> or
+<code class="docutils literal notranslate"><span class="pre">n</span></code>
is set as is, for example a number or a string:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>$ ./tools/checkkconfig.py -f defconfig -s
ELF y TASK_NAME_SIZE 16
+</pre></div>
+</div>
+<p>CMake builds keep the configuration in the build directory instead of the
+top-level NuttX directory. Pass that directory with <code class="docutils
literal notranslate"><span class="pre">-o</span></code>/<code class="docutils
literal notranslate"><span class="pre">--out_dir</span></code> to
+analyze a CMake configuration:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>$ cmake -B build -DBOARD_CONFIG=sim:nsh
-GNinja
+$ ./tools/checkkconfig.py -o build -f build/.config -s ELF y
+</pre></div>
+</div>
</section>
diff --git a/content/docs/latest/components/tools/refresh.html
b/content/docs/latest/components/tools/refresh.html
index 41ca409068..b995ed8a51 100644
--- a/content/docs/latest/components/tools/refresh.html
+++ b/content/docs/latest/components/tools/refresh.html
@@ -281,6 +281,8 @@ So an old configuration file may not be usable anymore
until it is refreshed.</p
<span class="go"> Do not prompt for new default selections; accept all
recommended default values</span>
<span class="go"> --nocopy</span>
<span class="go"> Do not copy defconfig from
nuttx/boards/<board>/configs to nuttx/.config</span>
+<span class="go"> --cmake</span>
+<span class="go"> Use CMake refresh target instead of make refresh to
refresh the defconfig</span>
<span class="go"> --help</span>
<span class="go"> Show this help message and exit</span>
<span class="go"> <board></span>
@@ -323,6 +325,20 @@ depending on the <code class="docutils literal
notranslate"><span class="pre">--
</li>
<li><p>Restore the <code class="docutils literal notranslate"><span
class="pre">.config</span></code> and <code class="docutils literal
notranslate"><span class="pre">Make.defs</span></code> files from step
1.</p></li>
</ol>
+<p>With the <code class="docutils literal notranslate"><span
class="pre">--cmake</span></code> option, the configuration is refreshed with
the CMake build
+instead, so it also works for board configurations that have no <code
class="docutils literal notranslate"><span class="pre">Make.defs</span></code>
+file. For each configuration, <code class="docutils literal
notranslate"><span class="pre">refresh.sh</span></code>:</p>
+<ol class="arabic simple">
+<li><p>Configures a temporary CMake build directory <code class="docutils
literal notranslate"><span class="pre">refresh/</span></code> in the top-level
+NuttX directory with <code class="docutils literal notranslate"><span
class="pre">cmake</span> <span class="pre">-B</span> <span
class="pre">refresh</span> <span
class="pre">-DBOARD_CONFIG=<config></span> <span
class="pre">-GNinja</span></code>.</p></li>
+<li><p>Runs <code class="docutils literal notranslate"><span
class="pre">cmake</span> <span class="pre">--build</span> <span
class="pre">refresh</span> <span class="pre">-t</span> <span
class="pre">refreshsilent</span></code>, which updates the
+configuration with the default values and creates the new defconfig
file.</p></li>
+<li><p>Copies the new defconfig file out of <code class="docutils literal
notranslate"><span class="pre">refresh/</span></code>, removes <code
class="docutils literal notranslate"><span class="pre">refresh/</span></code>,
and
+compares and saves the new defconfig file in the same way as the Make-based
+refresh.</p></li>
+</ol>
+<p>The <code class="docutils literal notranslate"><span
class="pre">.config</span></code> and <code class="docutils literal
notranslate"><span class="pre">Make.defs</span></code> files in the top-level
directory are not used
+or modified in this mode.</p>
<section id="usage-examples">
<h2>Usage examples<a class="headerlink" href="#usage-examples"
title="Permalink to this heading"></a></h2>
<p>Update all boards without verbose output:</p>
@@ -355,6 +371,10 @@ configuration subdirectory:</p>
<div class="highlight-console notranslate"><div
class="highlight"><pre><span></span><span class="gp">$
</span>./tools/refresh.sh<span class="w"> </span>--defaults<span class="w">
</span>boards/arm/stm32f1/stm32f103-minimum/configs/nsh
</pre></div>
</div>
+<p>Update the <cite>nsh</cite> config from the <code class="docutils literal
notranslate"><span class="pre">qemu-armv7a</span></code> board with the CMake
build:</p>
+<div class="highlight-console notranslate"><div
class="highlight"><pre><span></span><span class="gp">$
</span>./tools/refresh.sh<span class="w"> </span>--silent<span class="w">
</span>--cmake<span class="w"> </span>qemu-armv7a:nsh
+</pre></div>
+</div>
</section>
</section>
diff --git a/content/docs/latest/guides/chip-specific/stm32_ports.html
b/content/docs/latest/guides/chip-specific/stm32_ports.html
index 50baf0a760..f841206e8f 100644
--- a/content/docs/latest/guides/chip-specific/stm32_ports.html
+++ b/content/docs/latest/guides/chip-specific/stm32_ports.html
@@ -2125,8 +2125,8 @@ exact IP core version has not been documented yet.</p>
<td><p>arch/arm/src/stm32h7/stm32_rtc.c</p></td>
</tr>
<tr class="row-odd"><td><p>SDMMC</p></td>
-<td><p>to be done</p></td>
-<td><p>arch/arm/src/stm32h7/stm32_sdmmc.c</p></td>
+<td><p>v2</p></td>
+<td><p>arch/arm/src/common/stm32/stm32_sdmmc_v2.c</p></td>
</tr>
<tr class="row-even"><td><p>SPI/I2S</p></td>
<td><p>to be done</p></td>
@@ -2540,27 +2540,31 @@ exact IP core version has not been documented yet.</p>
<td><p>M33M55 v1</p></td>
<td><p>arch/arm/src/common/stm32/stm32_rtcc_m33m55_v1.c</p></td>
</tr>
-<tr class="row-odd"><td><p>SPI/I2S</p></td>
+<tr class="row-odd"><td><p>SDMMC</p></td>
+<td><p>v2</p></td>
+<td><p>arch/arm/src/common/stm32/stm32_sdmmc_v2.c</p></td>
+</tr>
+<tr class="row-even"><td><p>SPI/I2S</p></td>
<td><p>v5</p></td>
<td><p>arch/arm/src/common/stm32/stm32_spi_v5.c</p></td>
</tr>
-<tr class="row-even"><td><p>TIM</p></td>
+<tr class="row-odd"><td><p>TIM</p></td>
<td><p>v3</p></td>
<td><p>arch/arm/src/common/stm32/stm32_tim.c</p></td>
</tr>
-<tr class="row-odd"><td><p>USART/LPUART</p></td>
+<tr class="row-even"><td><p>USART/LPUART</p></td>
<td><p>M33M55 v3</p></td>
<td><p>arch/arm/src/common/stm32/stm32_serial_m33m55_v3.c</p></td>
</tr>
-<tr class="row-even"><td><p>USB</p></td>
+<tr class="row-odd"><td><p>USB</p></td>
<td><p>device</p></td>
<td><p>not supported</p></td>
</tr>
-<tr class="row-odd"><td><p>WWDG</p></td>
+<tr class="row-even"><td><p>WWDG</p></td>
<td><p>v3</p></td>
<td><p>arch/arm/src/common/stm32/stm32_wwdg.c</p></td>
</tr>
-<tr class="row-even"><td><p>XSPI</p></td>
+<tr class="row-odd"><td><p>XSPI</p></td>
<td><p>to be done</p></td>
<td><p>not supported</p></td>
</tr>
diff --git
a/content/docs/latest/guides/concurrency/signal_events_interrupt_handlers.html
b/content/docs/latest/guides/concurrency/signal_events_interrupt_handlers.html
index b620d3b8c8..db9d52f667 100644
---
a/content/docs/latest/guides/concurrency/signal_events_interrupt_handlers.html
+++
b/content/docs/latest/guides/concurrency/signal_events_interrupt_handlers.html
@@ -441,7 +441,7 @@ etc., detect the event that generated the signal, and do
something
about it. It is sometimes a pain because you have to remember to
handle the <code class="docutils literal notranslate"><span
class="pre">EINTR</span></code> return value even when you don’t care about
it.</p>
<p>The POSIX signal definition includes some support that would make this
-easier for you. This support is not currently implemented in NuttX.
+easier for you.
The <code class="docutils literal notranslate"><span
class="pre">kill()</span></code> interface for example
(<a class="reference external"
href="http://pubs.opengroup.org/onlinepubs/009695399/functions/kill.html">http://pubs.opengroup.org/onlinepubs/009695399/functions/kill.html</a>)
supports this behavior:</p>
@@ -456,9 +456,9 @@ signal.”</p>
an unspecified set of system processes) whose process group ID is equal to
the absolute value of pid, and for which the process has permission to send
a signal.”</p>
-<p>NuttX does not currently support process groups. But that might be a good
-RTOS extension. If you and others think that would be useful I could
-probably add the basics of such a feature in a day or so.</p>
+<p>With <code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_PROCESS_GROUPS</span></code>, NuttX supports process
groups: a pid
+of 0 or less than -1 sends the signal to each process of the process group.
+A pid of -1 (all processes) is not supported.</p>
</section>
<section id="poll">
<h2><code class="docutils literal notranslate"><span
class="pre">poll()</span></code><a class="headerlink" href="#poll"
title="Permalink to this heading"></a></h2>
diff --git a/content/docs/latest/guides/concurrency/thread_local_storage.html
b/content/docs/latest/guides/concurrency/thread_local_storage.html
index 3ffca04007..5ad6cd477d 100644
--- a/content/docs/latest/guides/concurrency/thread_local_storage.html
+++ b/content/docs/latest/guides/concurrency/thread_local_storage.html
@@ -272,7 +272,7 @@ the platform support pthreads.
</div>
<p>Then you can see <code class="docutils literal notranslate"><span
class="pre">--disable-tls</span></code> in the output, which means that your
compiler does not support TLS.</p>
<p>In this case, you can still use the thread local relative keyword, but it
would be implemented by libgcc’s emutls.</p>
-<p>NuttX’s libc provides its own version (<code class="docutils literal
notranslate"><span class="pre">CONFIG_TLS_EMUTLS</span></code>, set for the GCC
and clang toolchains when libgcc is the builtin library, <code class="docutils
literal notranslate"><span class="pre">CONFIG_BUILTIN_TOOLCHAIN</span></code>;
the sim has it with GCC and the GNU linker, as on Linux and MinGW), and the
link sends the calls to <code class="docutils literal notranslate"><span
class="pre">__emutls_get_address( [...]
+<p>NuttX’s libc provides its own version (<code class="docutils literal
notranslate"><span class="pre">CONFIG_TLS_EMUTLS</span></code>, set for the GCC
and clang toolchains when libgcc is the builtin library, <code class="docutils
literal notranslate"><span class="pre">CONFIG_BUILTIN_TOOLCHAIN</span></code>;
the sim has it with GCC and the GNU linker, as on Linux and MinGW), and the
link sends the calls to <code class="docutils literal notranslate"><span
class="pre">__emutls_get_address( [...]
<p>The image, the modules and the programs of a kernel build are linked with
<code class="docutils literal notranslate"><span
class="pre">--wrap</span></code>; code loaded at run time finds the libc
version in the system symbol table (<code class="docutils literal
notranslate"><span
class="pre">CONFIG_EXECFUNCS_SYSTEM_SYMTAB</span></code>).</p>
</section>
</section>
diff --git a/content/docs/latest/guides/porting/port_bootsequence.html
b/content/docs/latest/guides/porting/port_bootsequence.html
index 6267e5703b..7e6d3286aa 100644
--- a/content/docs/latest/guides/porting/port_bootsequence.html
+++ b/content/docs/latest/guides/porting/port_bootsequence.html
@@ -151,13 +151,7 @@
<li class="toctree-l2"><a class="reference internal"
href="../build/platform_directories.html">Platform Directories</a></li>
<li class="toctree-l2"><a class="reference internal"
href="customboards.html">Custom Boards How-To</a></li>
<li class="toctree-l2"><a class="reference internal"
href="include_files_board_h.html">Including Files in board.h</a></li>
-<li class="toctree-l2 current"><a class="reference internal"
href="port.html">How to port</a><ul class="current">
-<li class="toctree-l3 current"><a class="current reference internal"
href="#">The diagram of boot sequence</a></li>
-<li class="toctree-l3"><a class="reference internal"
href="port_relatedkernelconfigrations.html">The list of related kernel
configurations</a></li>
-<li class="toctree-l3"><a class="reference internal"
href="port.html#porting-procedure">Porting procedure</a></li>
-<li class="toctree-l3"><a class="reference internal"
href="port.html#porting-case-studies">Porting Case Studies</a></li>
-</ul>
-</li>
+<li class="toctree-l2"><a class="reference internal" href="port.html">How to
port</a></li>
<li class="toctree-l2 current"><a class="current reference internal"
href="#">The diagram of boot sequence</a></li>
<li class="toctree-l2"><a class="reference internal"
href="port_relatedkernelconfigrations.html">The list of related kernel
configurations</a></li>
<li class="toctree-l2"><a class="reference internal"
href="specialstuff_in_nuttxheaderfiles.html">Why can’t I put my special stuff
in NuttX header files?</a></li>
diff --git
a/content/docs/latest/guides/porting/port_relatedkernelconfigrations.html
b/content/docs/latest/guides/porting/port_relatedkernelconfigrations.html
index f5d65a44b7..d902cccbda 100644
--- a/content/docs/latest/guides/porting/port_relatedkernelconfigrations.html
+++ b/content/docs/latest/guides/porting/port_relatedkernelconfigrations.html
@@ -151,13 +151,7 @@
<li class="toctree-l2"><a class="reference internal"
href="../build/platform_directories.html">Platform Directories</a></li>
<li class="toctree-l2"><a class="reference internal"
href="customboards.html">Custom Boards How-To</a></li>
<li class="toctree-l2"><a class="reference internal"
href="include_files_board_h.html">Including Files in board.h</a></li>
-<li class="toctree-l2 current"><a class="reference internal"
href="port.html">How to port</a><ul class="current">
-<li class="toctree-l3"><a class="reference internal"
href="port_bootsequence.html">The diagram of boot sequence</a></li>
-<li class="toctree-l3 current"><a class="current reference internal"
href="#">The list of related kernel configurations</a></li>
-<li class="toctree-l3"><a class="reference internal"
href="port.html#porting-procedure">Porting procedure</a></li>
-<li class="toctree-l3"><a class="reference internal"
href="port.html#porting-case-studies">Porting Case Studies</a></li>
-</ul>
-</li>
+<li class="toctree-l2"><a class="reference internal" href="port.html">How to
port</a></li>
<li class="toctree-l2"><a class="reference internal"
href="port_bootsequence.html">The diagram of boot sequence</a></li>
<li class="toctree-l2 current"><a class="current reference internal"
href="#">The list of related kernel configurations</a></li>
<li class="toctree-l2"><a class="reference internal"
href="specialstuff_in_nuttxheaderfiles.html">Why can’t I put my special stuff
in NuttX header files?</a></li>
diff --git a/content/docs/latest/guides/programs/fully_linked_elf.html
b/content/docs/latest/guides/programs/fully_linked_elf.html
index c9ee47a3c4..a6c3503847 100644
--- a/content/docs/latest/guides/programs/fully_linked_elf.html
+++ b/content/docs/latest/guides/programs/fully_linked_elf.html
@@ -488,7 +488,7 @@ NuttX package: <code class="docutils literal
notranslate"><span class="pre">nutt
<div
class="admonition-here-is-an-alternative-minimal-and-possibly-outdated-version
admonition">
<p class="admonition-title">Here is an alternative minimal (and possibly
outdated) version</p>
<div class="sphinx_collapse docutils">
-<input class="sphinx_collapse__input"
id="8c3749e3-8c5e-4c5d-88cd-6e8983a6f68c"
name="8c3749e3-8c5e-4c5d-88cd-6e8983a6f68c" type="checkbox"><label
class="sphinx_collapse__label" for="8c3749e3-8c5e-4c5d-88cd-6e8983a6f68c"><i
class="sphinx_collapse__icon"></i>Show content:</label><div
class="sphinx_collapse__content docutils">
+<input class="sphinx_collapse__input"
id="9094dcc7-fc4a-4040-97bd-9173e2195580"
name="9094dcc7-fc4a-4040-97bd-9173e2195580" type="checkbox"><label
class="sphinx_collapse__label" for="9094dcc7-fc4a-4040-97bd-9173e2195580"><i
class="sphinx_collapse__icon"></i>Show content:</label><div
class="sphinx_collapse__content docutils">
<div class="highlight-text notranslate"><div
class="highlight"><pre><span></span>SECTIONS
{
.text 0x00000000 :
diff --git a/content/docs/latest/guides/programs/partially_linked_elf.html
b/content/docs/latest/guides/programs/partially_linked_elf.html
index a6741042eb..5f99a87abb 100644
--- a/content/docs/latest/guides/programs/partially_linked_elf.html
+++ b/content/docs/latest/guides/programs/partially_linked_elf.html
@@ -514,7 +514,7 @@ NuttX package: <code class="docutils literal
notranslate"><span class="pre">nutt
<div
class="admonition-here-is-an-alternative-minimal-and-possibly-outdated-version
admonition">
<p class="admonition-title">Here is an alternative minimal (and possibly
outdated) version</p>
<div class="sphinx_collapse docutils">
-<input class="sphinx_collapse__input"
id="01f53f60-88b8-46bb-9134-7158eee99b73"
name="01f53f60-88b8-46bb-9134-7158eee99b73" type="checkbox"><label
class="sphinx_collapse__label" for="01f53f60-88b8-46bb-9134-7158eee99b73"><i
class="sphinx_collapse__icon"></i>Show content:</label><div
class="sphinx_collapse__content docutils">
+<input class="sphinx_collapse__input"
id="1831d130-720e-465b-9641-82f7585155cb"
name="1831d130-720e-465b-9641-82f7585155cb" type="checkbox"><label
class="sphinx_collapse__label" for="1831d130-720e-465b-9641-82f7585155cb"><i
class="sphinx_collapse__icon"></i>Show content:</label><div
class="sphinx_collapse__content docutils">
<div class="highlight-text notranslate"><div
class="highlight"><pre><span></span>SECTIONS
{
.text 0x00000000 :
diff --git a/content/docs/latest/objects.inv b/content/docs/latest/objects.inv
index 3bc91f190a..6e1e5dd092 100644
Binary files a/content/docs/latest/objects.inv and
b/content/docs/latest/objects.inv differ
diff --git a/content/docs/latest/os/drivers/character/serial.html
b/content/docs/latest/os/drivers/character/serial.html
index aafb0b9c86..36621a195d 100644
--- a/content/docs/latest/os/drivers/character/serial.html
+++ b/content/docs/latest/os/drivers/character/serial.html
@@ -237,12 +237,14 @@ If``TTY_LAUNCH_FILE`` you can set file path by <code
class="docutils literal not
<li><p><strong>Job control / controlling terminal</strong>. When <code
class="docutils literal notranslate"><span
class="pre">CONFIG_TTY_SIGINT</span></code>
or <code class="docutils literal notranslate"><span
class="pre">CONFIG_TTY_SIGTSTP</span></code> is enabled, the TTY layer can
generate
<code class="docutils literal notranslate"><span
class="pre">SIGINT</span></code> (Ctrl-C) and <code class="docutils literal
notranslate"><span class="pre">SIGTSTP</span></code> (Ctrl-Z) for a foreground
task.
-NuttX does not implement POSIX sessions or process groups, so the
-foreground process group is collapsed onto a single PID stored in
-the driver (<code class="docutils literal notranslate"><span
class="pre">pgrp</span> <span class="pre">==</span> <span
class="pre">pid</span></code>, one member per group); the signal is
-delivered with <code class="docutils literal notranslate"><span
class="pre">nxsig_kill(pid,</span> <span class="pre">signo)</span></code>. The
driver discards the
-character that sends the signal, so the task does not read it.</p>
-<p>The following terminal <code class="docutils literal notranslate"><span
class="pre">ioctl</span></code> commands manage this PID:</p>
+The driver keeps the ID of the foreground process group. With
+<code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_PROCESS_GROUPS</span></code>, each process of that
process group
+gets the signal. An ID that no process group has is a process ID
+(NSH sets one with <code class="docutils literal notranslate"><span
class="pre">TIOCSCTTY</span></code>): that process gets the signal.
+Without the option, a process group is one process, and the process
+with that ID gets the signal. The driver discards the character
+that sends the signal, so the task does not read it.</p>
+<p>The following terminal <code class="docutils literal notranslate"><span
class="pre">ioctl</span></code> commands manage this ID:</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span
class="pre">TIOCSCTTY</span></code> makes the terminal the controlling
terminal. The
<code class="docutils literal notranslate"><span class="pre">arg</span></code>
is treated as a flag: a value of <code class="docutils literal
notranslate"><span class="pre">0</span></code> selects the
@@ -257,20 +259,23 @@ session leader PID.</p></li>
<code class="docutils literal notranslate"><span
class="pre">tcsetpgrp()</span></code> passes it, <code class="docutils literal
notranslate"><span class="pre">arg</span></code> points to the PID (<code
class="docutils literal notranslate"><span class="pre">pid_t</span> <span
class="pre">*</span></code>);
a <code class="docutils literal notranslate"><span
class="pre">NULL</span></code> pointer or a PID that is not positive gives
<code class="docutils literal notranslate"><span
class="pre">EINVAL</span></code>.</p></li>
</ul>
-<p>The C library exposes these through <code class="docutils literal
notranslate"><span class="pre">tcgetpgrp()</span></code>, <code class="docutils
literal notranslate"><span class="pre">tcsetpgrp()</span></code>,
-<code class="docutils literal notranslate"><span
class="pre">tcgetsid()</span></code>, <code class="docutils literal
notranslate"><span class="pre">setsid()</span></code>, <code class="docutils
literal notranslate"><span class="pre">getsid()</span></code> and <code
class="docutils literal notranslate"><span class="pre">setpgid()</span></code>.
A process
-group is one process, so <code class="docutils literal notranslate"><span
class="pre">kill(-pgrp,</span> <span class="pre">signo)</span></code> and <code
class="docutils literal notranslate"><span class="pre">killpg()</span></code>
send
-the signal to the process <code class="docutils literal notranslate"><span
class="pre">pgrp</span></code>, and TTY signals go to the single
-foreground PID.</p>
+<p>The C library exposes these through <code class="docutils literal
notranslate"><span class="pre">tcgetpgrp()</span></code>, <code class="docutils
literal notranslate"><span class="pre">tcsetpgrp()</span></code>
+and <code class="docutils literal notranslate"><span
class="pre">tcgetsid()</span></code>. With <code class="docutils literal
notranslate"><span class="pre">CONFIG_SCHED_PROCESS_GROUPS</span></code>, <code
class="docutils literal notranslate"><span class="pre">setpgid()</span></code>,
+<code class="docutils literal notranslate"><span
class="pre">getpgid()</span></code>, <code class="docutils literal
notranslate"><span class="pre">setsid()</span></code> and <code class="docutils
literal notranslate"><span class="pre">getsid()</span></code> keep the process
groups
+and the sessions of POSIX, and <code class="docutils literal
notranslate"><span class="pre">kill(-pgrp,</span> <span
class="pre">signo)</span></code> and <code class="docutils literal
notranslate"><span class="pre">killpg()</span></code>
+send the signal to each process of the process group. Without it, a
+process group is one process: <code class="docutils literal notranslate"><span
class="pre">setpgid()</span></code> accepts only the process
+ID as the process group ID, and <code class="docutils literal
notranslate"><span class="pre">kill(-pgrp,</span> <span
class="pre">signo)</span></code> and
+<code class="docutils literal notranslate"><span
class="pre">killpg()</span></code> send the signal to the process <code
class="docutils literal notranslate"><span class="pre">pgrp</span></code>.</p>
</li>
<li><p><strong>Window size</strong>. <code class="docutils literal
notranslate"><span class="pre">TIOCGWINSZ</span></code> returns the terminal
size in a
<code class="docutils literal notranslate"><span class="pre">struct</span>
<span class="pre">winsize</span></code> and <code class="docutils literal
notranslate"><span class="pre">TIOCSWINSZ</span></code> sets it. The size is 0
rows
and 0 columns until a program sets it (for example <code class="docutils
literal notranslate"><span class="pre">openpty()</span></code> or
a remote login server). A change of the size sends <code class="docutils
literal notranslate"><span class="pre">SIGWINCH</span></code> to
-the foreground PID when <code class="docutils literal notranslate"><span
class="pre">CONFIG_TTY_SIGINT</span></code> or
+the foreground process group, as above, when <code class="docutils literal
notranslate"><span class="pre">CONFIG_TTY_SIGINT</span></code> or
<code class="docutils literal notranslate"><span
class="pre">CONFIG_TTY_SIGTSTP</span></code> is enabled. A pseudo-terminal
keeps one size
-for the master and the slave; the signal goes to the foreground PID
-of the slave.</p></li>
+for the master and the slave; the signal goes to the foreground
+process group of the slave.</p></li>
<li><p><strong>User Access</strong>. Serial drivers are, ultimately, normal
<a class="reference external" href="#chardrivers">character drivers</a> and
are accessed as other
character drivers.</p></li>
diff --git
a/content/docs/latest/platforms/arm/stm32n6/boards/stm32n6570-dk/index.html
b/content/docs/latest/platforms/arm/stm32n6/boards/stm32n6570-dk/index.html
index 712438c734..3ee7906a89 100644
--- a/content/docs/latest/platforms/arm/stm32n6/boards/stm32n6570-dk/index.html
+++ b/content/docs/latest/platforms/arm/stm32n6/boards/stm32n6570-dk/index.html
@@ -437,6 +437,22 @@ IMX335 held in reset (PC8) and registers the sensor as the
V4L2 depth
camera <code class="docutils literal notranslate"><span
class="pre">/dev/video1</span></code> (Z16, 8x8 or 4x4). INT uses EXTI0, so
the TAMP
button has no interrupt when the sensor is enabled.</p>
</section>
+<section id="microsd">
+<h2>microSD<a class="headerlink" href="#microsd" title="Permalink to this
heading"></a></h2>
+<p>The microSD slot is on SDMMC2 (4-bit, IDMA): PC2 CK, PC3 CMD, PC4-PC5 D0-D1,
+PC0 D2, PE4 D3 (AF11), card detect PN12 (low with a card) and card power
+enable PQ7 (high). The kernel clock is IC4 = 200 MHz, giving 400 kHz for
+identification and 25 MHz for transfers. The card is <code class="docutils
literal notranslate"><span class="pre">/dev/mmcsd0</span></code>;
+insertion and removal are reported through the card detect interrupt.
+With a FAT formatted card:</p>
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>nsh> mount -t vfat /dev/mmcsd0 /mnt
+nsh> echo hello > /mnt/test.txt
+nsh> cat /mnt/test.txt
+nsh> dd if=/dev/zero of=/mnt/big.bin bs=4096 count=256
+nsh> umount /mnt
+</pre></div>
+</div>
+</section>
<section id="clocking">
<h2>Clocking<a class="headerlink" href="#clocking" title="Permalink to this
heading"></a></h2>
<p>By default the CPU runs at 800 MHz and the system buses at 400 MHz. PLL1 is
@@ -473,6 +489,11 @@ draws nested coloured rectangles on the panel.</p>
with <code class="docutils literal notranslate"><span
class="pre">lvgldemo</span> <span class="pre">&</span></code>. The image
is close to the 511 KiB limit of the boot
ROM, so LVGL logging and extra fonts are left out.</p>
</section>
+<section id="sdcard">
+<h3>sdcard<a class="headerlink" href="#sdcard" title="Permalink to this
heading"></a></h3>
+<p>NuttShell with the microSD slot on SDMMC2 and the FAT file system, see
+<a class="reference internal" href="#microsd">microSD</a>.</p>
+</section>
</section>
</section>
diff --git a/content/docs/latest/platforms/arm/stm32n6/index.html
b/content/docs/latest/platforms/arm/stm32n6/index.html
index a614bd78a2..431b0e8bbc 100644
--- a/content/docs/latest/platforms/arm/stm32n6/index.html
+++ b/content/docs/latest/platforms/arm/stm32n6/index.html
@@ -384,45 +384,45 @@ clock selection from board.h.</p></td>
<td><p>Calendar, sub-seconds, Alarm A/B and wakeup timer
through the common RTC driver.</p></td>
</tr>
-<tr class="row-odd"><td><p>SPI</p></td>
+<tr class="row-odd"><td><p>SDMMC</p></td>
+<td><p>Yes</p></td>
+<td><p>SDMMC1-2 through the common IDMA SDMMC driver.</p></td>
+</tr>
+<tr class="row-even"><td><p>SPI</p></td>
<td><p>Yes</p></td>
<td><p>SPI1-6 through the common SPI v5 driver, master
mode, optional GPDMA.</p></td>
</tr>
-<tr class="row-even"><td><p>USART</p></td>
+<tr class="row-odd"><td><p>USART</p></td>
<td><p>Yes</p></td>
<td><p>USART1-3, UART4-5, USART6, UART7-9, USART10 and
LPUART1 through the common U(S)ART driver.</p></td>
</tr>
-<tr class="row-odd"><td><p>ADC</p></td>
-<td><p>No</p></td>
-<td></td>
-</tr>
-<tr class="row-even"><td><p>DCMIPP</p></td>
+<tr class="row-even"><td><p>ADC</p></td>
<td><p>No</p></td>
<td></td>
</tr>
-<tr class="row-odd"><td><p>IWDG</p></td>
+<tr class="row-odd"><td><p>DCMIPP</p></td>
<td><p>No</p></td>
<td></td>
</tr>
-<tr class="row-even"><td><p>LPTIM</p></td>
+<tr class="row-even"><td><p>IWDG</p></td>
<td><p>No</p></td>
<td></td>
</tr>
-<tr class="row-odd"><td><p>MPU</p></td>
+<tr class="row-odd"><td><p>LPTIM</p></td>
<td><p>No</p></td>
<td></td>
</tr>
-<tr class="row-even"><td><p>NPU</p></td>
+<tr class="row-even"><td><p>MPU</p></td>
<td><p>No</p></td>
<td></td>
</tr>
-<tr class="row-odd"><td><p>SAI</p></td>
+<tr class="row-odd"><td><p>NPU</p></td>
<td><p>No</p></td>
<td></td>
</tr>
-<tr class="row-even"><td><p>SDMMC</p></td>
+<tr class="row-even"><td><p>SAI</p></td>
<td><p>No</p></td>
<td></td>
</tr>
diff --git a/content/docs/latest/reference/user/01_task_control.html
b/content/docs/latest/reference/user/01_task_control.html
index e88c352055..f113a91786 100644
--- a/content/docs/latest/reference/user/01_task_control.html
+++ b/content/docs/latest/reference/user/01_task_control.html
@@ -841,8 +841,11 @@ The <code class="docutils literal notranslate"><span
class="pre">posix_spawnattr
<code class="docutils literal notranslate"><span
class="pre">spawn.h</span></code>. It will contains these attributes, not all
of which are
supported by NuttX:</p>
<ul>
-<li><p><code class="docutils literal notranslate"><span
class="pre">POSIX_SPAWN_SETPGROUP</span></code>: Setting of the new task’s
process group
-is not supported. NuttX does not support process groups.</p></li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">POSIX_SPAWN_SETPGROUP</span></code>: The new task joins the process
group of
+<code class="docutils literal notranslate"><span
class="pre">posix_spawnattr_setpgroup()</span></code>, or a new process group
if it is
+<code class="docutils literal notranslate"><span class="pre">0</span></code>
(with <code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_PROCESS_GROUPS</span></code>, else ignored).</p></li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">POSIX_SPAWN_SETSID</span></code>: The new task is the leader of a
new
+session (with <code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_PROCESS_GROUPS</span></code>, else ignored).</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">POSIX_SPAWN_SETSCHEDPARAM</span></code>: Set new tasks priority to
the
<code class="docutils literal notranslate"><span
class="pre">sched_param</span></code> value.</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">POSIX_SPAWN_SETSCHEDULER</span></code>: Set the new task’s
scheduler policy
@@ -892,8 +895,8 @@ depending upon the setting of <code class="docutils literal
notranslate"><span c
<code class="docutils literal notranslate"><span
class="pre">CONFIG_LIBC_ENVPATH</span></code> is defined, then only <code
class="docutils literal notranslate"><span
class="pre">posix_spawnp()</span></code>
behavior is supported; otherwise, only <code class="docutils literal
notranslate"><span class="pre">posix_spawn()</span></code> behavior is
supported.</p></li>
-<li><p>Process groups are not supported (See <code class="docutils literal
notranslate"><span class="pre">POSIX_SPAWN_SETPGROUP</span></code>
-above).</p></li>
+<li><p>Process groups need <code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_PROCESS_GROUPS</span></code> (See
+<code class="docutils literal notranslate"><span
class="pre">POSIX_SPAWN_SETPGROUP</span></code> above).</p></li>
<li><p>Effective user IDs are not supported (See <code class="docutils literal
notranslate"><span class="pre">POSIX_SPAWN_RESETIDS</span></code>
above).</p></li>
<li><p>Signal default actions cannot be modified in the newly task executed
@@ -1270,8 +1273,11 @@ The <code class="docutils literal notranslate"><span
class="pre">posix_spawnattr
<code class="docutils literal notranslate"><span
class="pre">spawn.h</span></code>. It will contains these attributes, not all
of which are
supported by NuttX:</p>
<ul>
-<li><p><code class="docutils literal notranslate"><span
class="pre">POSIX_SPAWN_SETPGROUP</span></code>: Setting of the new task’s
process group
-is not supported. NuttX does not support process groups.</p></li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">POSIX_SPAWN_SETPGROUP</span></code>: The new task joins the process
group of
+<code class="docutils literal notranslate"><span
class="pre">posix_spawnattr_setpgroup()</span></code>, or a new process group
if it is
+<code class="docutils literal notranslate"><span class="pre">0</span></code>
(with <code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_PROCESS_GROUPS</span></code>, else ignored).</p></li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">POSIX_SPAWN_SETSID</span></code>: The new task is the leader of a
new
+session (with <code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_PROCESS_GROUPS</span></code>, else ignored).</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">POSIX_SPAWN_SETSCHEDPARAM</span></code>: Set new tasks priority to
the
<code class="docutils literal notranslate"><span
class="pre">sched_param</span></code> value.</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">POSIX_SPAWN_SETSCHEDULER</span></code>: Set the new task’s
scheduler policy
diff --git a/content/docs/latest/reference/user/03_task_control.html
b/content/docs/latest/reference/user/03_task_control.html
index 49bbd1b29d..02c9136034 100644
--- a/content/docs/latest/reference/user/03_task_control.html
+++ b/content/docs/latest/reference/user/03_task_control.html
@@ -406,8 +406,8 @@ little more compliant to specifications. Without
for any task to complete execution. With
<code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_HAVE_PARENT</span></code>, <code class="docutils
literal notranslate"><span class="pre">waitpid()</span></code> will use <code
class="docutils literal notranslate"><span class="pre">SIGCHLD</span></code> and
can, therefore, wait for any child of the parent to complete. The
-implementation is incomplete in either case, however: NuttX does not
-support any concept of process groups. Nor does NuttX retain the
+implementation is incomplete in either case, however: it does not
+support process groups. Nor does NuttX retain the
status of exited tasks so if <code class="docutils literal notranslate"><span
class="pre">waitpid()</span></code> is called after a task has
exited, then no status will be available. The options argument is
currently ignored.</p>
@@ -550,8 +550,8 @@ interface. However, as of this writing, the implementation
of
little more compliant to specifications. <code class="docutils literal
notranslate"><span class="pre">waitpid()</span></code> simply
supports waiting a specific child task (<code class="docutils literal
notranslate"><span class="pre">P_PID</span></code> or for any child
task <code class="docutils literal notranslate"><span
class="pre">P_ALL</span></code> to complete execution. <code class="docutils
literal notranslate"><span class="pre">SIGCHLD</span></code> is used. The
-implementation is incomplete in either case, however: NuttX does not
-support any concept of process groups. Nor does NuttX retain the
+implementation is incomplete in either case, however: it does not
+support process groups. Nor does NuttX retain the
status of exited tasks so if <code class="docutils literal notranslate"><span
class="pre">waitpid()</span></code> is called after a task has
exited, then no status will be available. The options argument is
currently ignored.</p>
diff --git a/content/docs/latest/reference/user/07_signals.html
b/content/docs/latest/reference/user/07_signals.html
index 0084ec415a..1783539650 100644
--- a/content/docs/latest/reference/user/07_signals.html
+++ b/content/docs/latest/reference/user/07_signals.html
@@ -955,9 +955,12 @@ delivered more than once.”</p>
<dd class="field-odd"><ul class="simple">
<li><p><strong>pid</strong> – The id of the task to receive the signal. The
POSIX
<code class="docutils literal notranslate"><span
class="pre">kill()</span></code> specification encodes process group
information as zero
-and negative pid values. A process group is one process in NuttX:
-<code class="docutils literal notranslate"><span class="pre">0</span></code>
is the caller and <code class="docutils literal notranslate"><span
class="pre">-pid</span></code> is the process <code class="docutils literal
notranslate"><span class="pre">pid</span></code>. <code class="docutils literal
notranslate"><span class="pre">-1</span></code> (all
-processes) is not supported and gives <code class="docutils literal
notranslate"><span class="pre">ENOSYS</span></code>.</p></li>
+and negative pid values. With <code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_PROCESS_GROUPS</span></code>, <code class="docutils
literal notranslate"><span class="pre">0</span></code>
+is the process group of the caller and <code class="docutils literal
notranslate"><span class="pre">-pid</span></code> is the process group
+<code class="docutils literal notranslate"><span
class="pre">pid</span></code>: each process of the group that the caller may
control gets
+the signal. Without it, a process group is one process: <code class="docutils
literal notranslate"><span class="pre">0</span></code> is the
+caller and <code class="docutils literal notranslate"><span
class="pre">-pid</span></code> is the process <code class="docutils literal
notranslate"><span class="pre">pid</span></code>. <code class="docutils literal
notranslate"><span class="pre">-1</span></code> (all processes) is
+not supported and gives <code class="docutils literal notranslate"><span
class="pre">ENOSYS</span></code>.</p></li>
<li><p><strong>signo</strong> – The signal number to send. If signo is zero,
no signal is
sent, but all error checking is performed.</p></li>
</ul>
@@ -971,9 +974,9 @@ name. Differences from the POSIX interface include:</p>
<ul class="simple">
<li><p>Default action is to ignore signals.</p></li>
<li><p>Signals are processed one at a time in order</p></li>
-<li><p>A process group is one process, so a signal to a process group goes
-to that process. A signal to all processes (<code class="docutils literal
notranslate"><span class="pre">pid</span></code> -1) is not
-supported.</p></li>
+<li><p>Without <code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_PROCESS_GROUPS</span></code>, a process group is one
+process, so a signal to a process group goes to that process. A
+signal to all processes (<code class="docutils literal notranslate"><span
class="pre">pid</span></code> -1) is not supported.</p></li>
</ul>
</dd></dl>
diff --git a/content/docs/latest/searchindex.js
b/content/docs/latest/searchindex.js
index 2392587156..9aad061434 100644
--- a/content/docs/latest/searchindex.js
+++ b/content/docs/latest/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"docnames": ["ReleaseNotes/NuttX-0.1.0",
"ReleaseNotes/NuttX-0.1.1", "ReleaseNotes/NuttX-0.1.2",
"ReleaseNotes/NuttX-0.2.1", "ReleaseNotes/NuttX-0.2.2",
"ReleaseNotes/NuttX-0.2.3", "ReleaseNotes/NuttX-0.2.4",
"ReleaseNotes/NuttX-0.2.5", "ReleaseNotes/NuttX-0.2.6",
"ReleaseNotes/NuttX-0.2.7", "ReleaseNotes/NuttX-0.2.8",
"ReleaseNotes/NuttX-0.2.9", "ReleaseNotes/NuttX-0.3.0",
"ReleaseNotes/NuttX-0.3.1", "ReleaseNotes/NuttX-0.3.10",
"ReleaseNotes/NuttX-0.3.11", "ReleaseNote [...]
\ No newline at end of file
+Search.setIndex({"docnames": ["ReleaseNotes/NuttX-0.1.0",
"ReleaseNotes/NuttX-0.1.1", "ReleaseNotes/NuttX-0.1.2",
"ReleaseNotes/NuttX-0.2.1", "ReleaseNotes/NuttX-0.2.2",
"ReleaseNotes/NuttX-0.2.3", "ReleaseNotes/NuttX-0.2.4",
"ReleaseNotes/NuttX-0.2.5", "ReleaseNotes/NuttX-0.2.6",
"ReleaseNotes/NuttX-0.2.7", "ReleaseNotes/NuttX-0.2.8",
"ReleaseNotes/NuttX-0.2.9", "ReleaseNotes/NuttX-0.3.0",
"ReleaseNotes/NuttX-0.3.1", "ReleaseNotes/NuttX-0.3.10",
"ReleaseNotes/NuttX-0.3.11", "ReleaseNote [...]
\ No newline at end of file
diff --git a/content/docs/latest/standards/posix.html
b/content/docs/latest/standards/posix.html
index 4b9482b20c..4bcb825d58 100644
--- a/content/docs/latest/standards/posix.html
+++ b/content/docs/latest/standards/posix.html
@@ -718,8 +718,8 @@ devices without MMU.</p>
<td></td>
</tr>
<tr class="row-odd"><td><p><a class="reference internal"
href="#posix-job-control">POSIX_JOB_CONTROL</a></p></td>
-<td><p>1/4</p></td>
-<td></td>
+<td><p>Yes</p></td>
+<td><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_PROCESS_GROUPS</span></code></p></td>
</tr>
<tr class="row-even"><td><p><a class="reference internal"
href="#posix-regexp">POSIX_REGEXP</a></p></td>
<td><p>Yes</p></td>
@@ -2313,7 +2313,7 @@ by Kconfig choice option.</p>
<td><p>Yes</p></td>
</tr>
<tr class="row-even"><td><p>getsid()</p></td>
-<td><p>No</p></td>
+<td><p>Yes</p></td>
</tr>
<tr class="row-odd"><td><p><code class="xref c c-func docutils literal
notranslate"><span class="pre">quick_exit()</span></code></p></td>
<td><p>Yes</p></td>
@@ -2322,7 +2322,7 @@ by Kconfig choice option.</p>
<td><p>Yes</p></td>
</tr>
<tr class="row-odd"><td><p>setsid()</p></td>
-<td><p>No</p></td>
+<td><p>Yes</p></td>
</tr>
<tr class="row-even"><td><p><code class="xref c c-func docutils literal
notranslate"><span class="pre">sleep()</span></code></p></td>
<td><p>Yes</p></td>
@@ -2983,13 +2983,13 @@ by Kconfig choice option.</p>
</thead>
<tbody>
<tr class="row-even"><td><p>setpgid()</p></td>
-<td><p>No</p></td>
+<td><p>Yes</p></td>
</tr>
<tr class="row-odd"><td><p>tcgetpgrp()</p></td>
-<td><p>No</p></td>
+<td><p>Yes</p></td>
</tr>
<tr class="row-even"><td><p>tcsetpgrp()</p></td>
-<td><p>No</p></td>
+<td><p>Yes</p></td>
</tr>
<tr class="row-odd"><td><p><code class="xref c c-func docutils literal
notranslate"><span class="pre">tcgetsid()</span></code></p></td>
<td><p>Yes</p></td>
@@ -3705,7 +3705,7 @@ by Kconfig choice option.</p>
<td><p>Yes</p></td>
</tr>
<tr class="row-even"><td><p>getsid()</p></td>
-<td><p>No</p></td>
+<td><p>Yes</p></td>
</tr>
<tr class="row-odd"><td><p><code class="xref c c-func docutils literal
notranslate"><span class="pre">nice()</span></code></p></td>
<td><p>Yes</p></td>
@@ -4677,7 +4677,7 @@ permissions cannot be enforced.</p>
<td><p>Yes</p></td>
</tr>
<tr class="row-even"><td><p><code class="xref c c-func docutils literal
notranslate"><span
class="pre">posix_spawnattr_getpgroup()</span></code></p></td>
-<td><p>No</p></td>
+<td><p>Yes</p></td>
</tr>
<tr class="row-odd"><td><p><code class="xref c c-func docutils literal
notranslate"><span
class="pre">posix_spawnattr_getsigdefault()</span></code></p></td>
<td><p>No</p></td>
@@ -4692,7 +4692,7 @@ permissions cannot be enforced.</p>
<td><p>Yes</p></td>
</tr>
<tr class="row-odd"><td><p><code class="xref c c-func docutils literal
notranslate"><span
class="pre">posix_spawnattr_setpgroup()</span></code></p></td>
-<td><p>No</p></td>
+<td><p>Yes</p></td>
</tr>
<tr class="row-even"><td><p><code class="xref c c-func docutils literal
notranslate"><span
class="pre">posix_spawnattr_setsigdefault()</span></code></p></td>
<td><p>No</p></td>