This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-nuttx-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 3b1e674 Publishing web: feb249977349f687d40e57cfe5f0d39e5c5c71f9
docs: d8d19911ef416948efc9fc41a6695a2a601fb7e3
3b1e674 is described below
commit 3b1e67458277a7762a2974ea9dc66c8d40f23d55
Author: Matias <mat...@protobits.dev>
AuthorDate: Wed Oct 21 00:55:16 2020 +0000
Publishing web: feb249977349f687d40e57cfe5f0d39e5c5c71f9 docs:
d8d19911ef416948efc9fc41a6695a2a601fb7e3
---
.../_sources/applications/nsh/commands.rst.txt | 20 ++++++++++----------
.../latest/_sources/applications/nsh/config.rst.txt | 2 +-
.../components/drivers/character/index.rst.txt | 2 +-
.../components/drivers/special/syslog.rst.txt | 2 +-
.../docs/latest/_sources/components/nxflat.rst.txt | 4 ++--
content/docs/latest/_sources/guides/nfs.rst.txt | 2 +-
.../docs/latest/_sources/guides/simulator.rst.txt | 2 +-
.../latest/_sources/guides/tasktraceuser.rst.txt | 13 ++++++++++++-
.../_sources/introduction/detailed_support.rst.txt | 10 +++++-----
.../latest/_sources/introduction/resources.rst.txt | 2 +-
.../latest/_sources/quickstart/organization.rst.txt | 2 +-
.../reference/user/02_task_scheduling.rst.txt | 2 +-
.../_sources/reference/user/09_env_vars.rst.txt | 2 +-
.../_sources/reference/user/10_filesystem.rst.txt | 2 +-
.../latest/_sources/reference/user/index.rst.txt | 4 ++--
content/docs/latest/applications/nsh/commands.html | 20 ++++++++++----------
content/docs/latest/applications/nsh/config.html | 2 +-
.../latest/components/drivers/character/index.html | 2 +-
.../latest/components/drivers/special/syslog.html | 2 +-
content/docs/latest/components/nxflat.html | 4 ++--
content/docs/latest/guides/nfs.html | 2 +-
content/docs/latest/guides/simulator.html | 2 +-
content/docs/latest/guides/tasktraceuser.html | 12 +++++++++++-
content/docs/latest/index.html | 2 +-
.../docs/latest/introduction/detailed_support.html | 10 +++++-----
content/docs/latest/introduction/resources.html | 2 +-
content/docs/latest/quickstart/organization.html | 2 +-
.../latest/reference/user/02_task_scheduling.html | 2 +-
content/docs/latest/reference/user/09_env_vars.html | 2 +-
.../docs/latest/reference/user/10_filesystem.html | 2 +-
content/docs/latest/reference/user/index.html | 4 ++--
content/docs/latest/searchindex.js | 2 +-
content/feed.xml | 4 ++--
33 files changed, 85 insertions(+), 64 deletions(-)
diff --git a/content/docs/latest/_sources/applications/nsh/commands.rst.txt
b/content/docs/latest/_sources/applications/nsh/commands.rst.txt
index 5b00e09..39d642a 100644
--- a/content/docs/latest/_sources/applications/nsh/commands.rst.txt
+++ b/content/docs/latest/_sources/applications/nsh/commands.rst.txt
@@ -736,7 +736,7 @@ at <link> for the existing file or directory, <target>. This
implementation is simplified for use with NuttX in these ways:
- Links may be created only within the NuttX top-level, `pseudo
- file system <NuttxUserGuide.html#FileSystemOverview>`__. No
+ file system <NuttXUserGuide.html#FileSystemOverview>`__. No
file system currently supported by NuttX provides symbolic
links.
- For the same reason, only soft links are implemented.
@@ -875,7 +875,7 @@ of ``<path>`` except the final directory name must exist on
a
mounted file system; the final directory must not.
**Limited to Mounted File Systems**. Recall that NuttX uses a
-`pseudo file system <NuttxUserGuide.html#FileSystemOverview>`__
+`pseudo file system <NuttXUserGuide.html#FileSystemOverview>`__
for its root file system. The ``mkdir`` command can only be used
to create directories in volumes set up with the
```mount`` <#cmdmount>`__ command; it cannot be used to create
@@ -916,7 +916,7 @@ zero because the FAT32 root directory is a cluster chain.
NSH provides this command to access the
```mkfatfs()`` <mkfatfs>`__ NuttX API. This block device must
reside in the NuttX `pseudo file
-system <NuttxUserGuide.html#FileSystemOverview>`__ and must have
+system <NuttXUserGuide.html#FileSystemOverview>`__ and must have
been created by some call to ``register_blockdriver()`` (see
``include/nuttx/fs/fs.h``).
@@ -933,7 +933,7 @@ be needed to complete the ``<path>``. By convention,
however,
device drivers are place in the standard ``/dev`` directory. After
it is created, the FIFO device may be used as any other device
driver. NSH provides this command to access the
-```mkfifo()`` <NuttxUserGuide.html#mkfifo>`__ NuttX API.
+```mkfifo()`` <NuttXUserGuide.html#mkfifo>`__ NuttX API.
**Example**::
@@ -1018,23 +1018,23 @@ way association, binding:
supported value for ``<fstype>``
#. **Block Device.** The ``<block-device>`` argument is the full
or relative path to a block driver inode in the `pseudo file
- system <NuttxUserGuide.html#FileSystemOverview>`__. By
+ system <NuttXUserGuide.html#FileSystemOverview>`__. By
convention, this is a name under the ``/dev`` sub-directory.
This ``<block-device>`` must have been previously formatted
with the same file system type as specified by ``<fstype>``
#. **Mount Point.** The mount point, ``<dir-path>``, is the
location in the `pseudo file
- system <NuttxUserGuide.html#FileSystemOverview>`__ where the
+ system <NuttXUserGuide.html#FileSystemOverview>`__ where the
mounted volume will appear. This mount point can only reside in
the NuttX `pseudo file
- system <NuttxUserGuide.html#FileSystemOverview>`__. By
+ system <NuttXUserGuide.html#FileSystemOverview>`__. By
convention, this mount point is a subdirectory under ``/mnt``.
The mount command will create whatever pseudo directories that
may be needed to complete the full path but the full path must
not already exist.
After the volume has been mounted in the NuttX `pseudo file
-system <NuttxUserGuide.html#FileSystemOverview>`__, it may be
+system <NuttXUserGuide.html#FileSystemOverview>`__, it may be
access in the same way as other objects in the file system.
**Examples**:
@@ -1207,7 +1207,7 @@ Remove a File (rm)
**Synopsis**. Remove the specified ``<file-path>`` name from the
mounted file system. Recall that NuttX uses a `pseudo file
-system <NuttxUserGuide.html#FileSystemOverview>`__ for its root
+system <NuttXUserGuide.html#FileSystemOverview>`__ for its root
file system. The ``rm`` command can only be used to remove
(unlink) files in volumes set up with the
```mount`` <#cmdmount>`__ command; it cannot be used to remove
@@ -1234,7 +1234,7 @@ Remove a Directory (rmdir)
**Synopsis**. Remove the specified ``<dir-path>`` directory from
the mounted file system. Recall that NuttX uses a `pseudo file
-system <NuttxUserGuide.html#FileSystemOverview>`__ for its root
+system <NuttXUserGuide.html#FileSystemOverview>`__ for its root
file system. The ``rmdir`` command can only be used to remove
directories from volumes set up with the ```mount`` <#cmdmount>`__
command; it cannot be used to remove directories from the *pseudo*
diff --git a/content/docs/latest/_sources/applications/nsh/config.rst.txt
b/content/docs/latest/_sources/applications/nsh/config.rst.txt
index 6e48881..a2a277a 100644
--- a/content/docs/latest/_sources/applications/nsh/config.rst.txt
+++ b/content/docs/latest/_sources/applications/nsh/config.rst.txt
@@ -10,7 +10,7 @@ The availability of the above commands depends upon features
that may or
may not be enabled in the NuttX configuration file. The following
`table <#cmddependencies>`__ indicates the dependency of each command on
NuttX configuration settings. General configuration settings are
-discussed in the `NuttX Porting Guide. <NuttxPortingGuide.html>`__
+discussed in the `NuttX Porting Guide. <NuttXPortingGuide.html>`__
Configuration settings specific to NSH as discussed at the
`bottom <#nshconfiguration>`__ of this document.
diff --git
a/content/docs/latest/_sources/components/drivers/character/index.rst.txt
b/content/docs/latest/_sources/components/drivers/character/index.rst.txt
index 7ebdfe0..6983fbb 100644
--- a/content/docs/latest/_sources/components/drivers/character/index.rst.txt
+++ b/content/docs/latest/_sources/components/drivers/character/index.rst.txt
@@ -20,7 +20,7 @@ Character device drivers have these properties:
- **User Access**. After it has been registered, the character
driver can be accessed by user code using the standard `driver
- operations <NuttxUserGuide.html#driveroperations>`__ including
+ operations <NuttXUserGuide.html#driveroperations>`__ including
``open()``, ``close()``, ``read()``, ``write()``, etc.
- **Specialized Character Drivers**. Within the common character
diff --git
a/content/docs/latest/_sources/components/drivers/special/syslog.rst.txt
b/content/docs/latest/_sources/components/drivers/special/syslog.rst.txt
index a19f3e4..7e27766 100644
--- a/content/docs/latest/_sources/components/drivers/special/syslog.rst.txt
+++ b/content/docs/latest/_sources/components/drivers/special/syslog.rst.txt
@@ -467,7 +467,7 @@ debugging output in a circular buffer in RAM. It differs
from a
pipe in numerous details as needed to support logging.
This driver is built when ``CONFIG_RAMLOG`` is defined in the
-Nuttx configuration.
+NuttX configuration.
``dmesg`` command
-----------------
diff --git a/content/docs/latest/_sources/components/nxflat.rst.txt
b/content/docs/latest/_sources/components/nxflat.rst.txt
index 9a31823..f7547cb 100644
--- a/content/docs/latest/_sources/components/nxflat.rst.txt
+++ b/content/docs/latest/_sources/components/nxflat.rst.txt
@@ -42,7 +42,7 @@ NXFLAT is derived from `XFLAT
<http://xflat.sourceforge.net/>`__. XFLAT
is a toolchain add that provides full shared library and XIP executable
support for processors that have no Memory Management Unit
(MMU:sup:`1`). NXFLAT is greatly simplified for the deeply embedded
-environment targeted by Nuttx:
+environment targeted by NuttX:
- NXFLAT does not support shared libraries, because
- NXFLAT does not support *exportation* of symbol values from a module
@@ -142,7 +142,7 @@ will need version 0.1.7 or later.
Here are some general build instructions:
-- You must have already configured Nuttx in ``<some-dir>/nuttx``
+- You must have already configured NuttX in ``<some-dir>/nuttx``
- Download the buildroot package ``buildroot-0.x.y`` into
``<some-dir>``
- Unpack ``<some-dir>/buildroot-0.x.y.tar.gz`` using a command like ``tar zxf
buildroot-0.x.y``. This will result in a new directory like
``<some-dir>/buildroot-0.x.y``
diff --git a/content/docs/latest/_sources/guides/nfs.rst.txt
b/content/docs/latest/_sources/guides/nfs.rst.txt
index 8c267f5..fda1a84 100644
--- a/content/docs/latest/_sources/guides/nfs.rst.txt
+++ b/content/docs/latest/_sources/guides/nfs.rst.txt
@@ -26,7 +26,7 @@ Mount Interface
A low-level, C-callable interface is provided to mount a file system.
That interface is called ``mount()`` and is mentioned in the
-```porting guide`` <NuttxPortingGuide.html#NxFileSystem>`__ and is
+```porting guide`` <NuttXPortingGuide.html#NxFileSystem>`__ and is
prototyped in the header file ``include/sys/mount.h``:
.. c:function:: int mount(const char *source, const char *target, const char
*filesystemtype, unsigned long mountflags, const void *data)
diff --git a/content/docs/latest/_sources/guides/simulator.rst.txt
b/content/docs/latest/_sources/guides/simulator.rst.txt
index 1cbfbe4..a97ff55 100644
--- a/content/docs/latest/_sources/guides/simulator.rst.txt
+++ b/content/docs/latest/_sources/guides/simulator.rst.txt
@@ -134,7 +134,7 @@ Accessing the Network
need to pick the one that's right for your system.
Then, on Linux do this to set up the tap network interface and route that
will let
- the Apache Nuttx simulator access the network:
+ the Apache NuttX simulator access the network:
.. code-block:: console
diff --git a/content/docs/latest/_sources/guides/tasktraceuser.rst.txt
b/content/docs/latest/_sources/guides/tasktraceuser.rst.txt
index 5dad737..b04db80 100644
--- a/content/docs/latest/_sources/guides/tasktraceuser.rst.txt
+++ b/content/docs/latest/_sources/guides/tasktraceuser.rst.txt
@@ -41,6 +41,7 @@ The following configurations are configurable parameters for
trace.
- Bit 0 = Enable instrumentation
- Bit 1 = Enable syscall instrumentation
- Bit 2 = Enable IRQ instrumentation
+ - Bit 3 = Enable collecting syscall arguments
- ``CONFIG_SCHED_INSTRUMENTATION_NOTERAM_BUFSIZE``
@@ -52,6 +53,10 @@ The following configurations are configurable parameters for
trace.
- If enabled, stop overwriting old notes in the circular buffer when the
buffer is full by default.
This is useful to keep instrumentation data of the beginning of a system
boot.
+- ``CONFIG_SCHED_INSTRUMENTATION_HIRES``
+
+ - If enabled, use higher resolution system timer for instrumentation.
+
After the configuration, rebuild the NuttX kernel and application.
If the trace function is enabled, "``trace``" :doc:`../components/nsh/builtin`
will be available.
@@ -232,7 +237,7 @@ The default value is given by the kernel configuration
``CONFIG_SCHED_INSTRUMENT
.. code-block::
- trace mode [{+|-}{o|s|i}...]
+ trace mode [{+|-}{o|s|a|i}...]
- ``+o`` : Enable overwrite mode.
The trace buffer is a ring buffer and it can overwrite old data if no free
space is available in the buffer.
@@ -248,6 +253,11 @@ The default value is given by the kernel configuration
``CONFIG_SCHED_INSTRUMENT
- ``-s`` : Disable system call trace.
+- ``+a`` : Enable recording the system call arguments.
+ It records the arguments passed to the issued system call to the trace data.
+
+- ``-a`` : Disable recording the system call arguments.
+
- ``+i`` : Enable interrupt trace.
It records the event of enter/leave interrupt handler which is occured while
the tracing.
All IRQs are recorded by default. ``trace irq`` command can filter the IRQs
to be recorded.
@@ -266,6 +276,7 @@ If no command parameters are specified, display the current
mode as the follows.
Overwrite : on (+o)
Syscall trace : on (+s)
Filtered Syscalls : 16
+ Syscall trace with args : on (+a)
IRQ trace : on (+i)
Filtered IRQs : 2
diff --git a/content/docs/latest/_sources/introduction/detailed_support.rst.txt
b/content/docs/latest/_sources/introduction/detailed_support.rst.txt
index 0fd0c6a..4c49ff2 100644
--- a/content/docs/latest/_sources/introduction/detailed_support.rst.txt
+++ b/content/docs/latest/_sources/introduction/detailed_support.rst.txt
@@ -185,7 +185,7 @@ There are ports to two Microchip SAMA5D3 boards:
- A full-loaded NuttShell (:ref:`NSH <nsh>`) configuration
that demonstrates all of the SAMA5D3x features.
- The following support was added in Nuttx 6.30:
+ The following support was added in NuttX 6.30:
- DMA support, and
- PIO interrupts,
@@ -973,7 +973,7 @@ Three configurations are available:
the STM32F103 or STM32F107 part.
#. A network-enabled NuttShell (NSH) configuration that will work only
with the STM32F107 part.
-#. The configuration that was used to verify the Nuttx `high-priority,
+#. The configuration that was used to verify the NuttX `high-priority,
nested interrupt
feature
<https://cwiki.apache.org/confluence/display/NUTTX/High+Performance%2C+Zero+Latency+Interrupts>`__.
@@ -1173,7 +1173,7 @@ boards.
Zilogic System's ARM development Kit, ZKIT-ARM-1769. This board is
based on the NXP LPC1769. The initial release was included
- NuttX-6.26. The Nuttx Buildroot toolchain is used by default. Verifed
+ NuttX-6.26. The NuttX Buildroot toolchain is used by default. Verifed
configurations include the "Hello, World!" example application and a
THTTPD demonstration. Refer to the NuttX board
`README
<https://github.com/apache/incubator-nuttx/blob/master/boards/arm/lpc17xx_40xx/zkit-arm-1769/README.txt>`__
@@ -2455,7 +2455,7 @@ Also refer to the NuttX board
`README
<https://github.com/apache/incubator-nuttx/blob/master/boards/arm/samd5e5/metro-m4/README.txt>`__
file for further information about the current state of the port.
-Nuttx-9.0 added basic support for Microchip SAME54 Xplained Pro board.
+NuttX-9.0 added basic support for Microchip SAME54 Xplained Pro board.
An ethernet driver was also added to the SAME5x familly.
STMicro STM32 F72x/F73x
@@ -3039,7 +3039,7 @@ Parallel-Ultra-Low-Power design.
`Sipeed Maix bit <#k210>`__
-Initial support for the Sipeed Maix bit board was added in Nuttx-9.0.
+Initial support for the Sipeed Maix bit board was added in NuttX-9.0.
LiteX on ARTY A7
----------------
diff --git a/content/docs/latest/_sources/introduction/resources.rst.txt
b/content/docs/latest/_sources/introduction/resources.rst.txt
index fad8152..8fc4855 100644
--- a/content/docs/latest/_sources/introduction/resources.rst.txt
+++ b/content/docs/latest/_sources/introduction/resources.rst.txt
@@ -9,7 +9,7 @@ Here's a list of Apache NuttX resources that you might find
helpful:
* Apache NuttX
* `Apache NuttX website <https://apache.nuttx.org>`_
- * `Apache NuttX online documentation
<https://cwiki.apache.org/confluence/display/NUTTX/Nuttx>`_
+ * `Apache NuttX online documentation
<https://cwiki.apache.org/confluence/display/NUTTX/NuttX>`_
* `Apache NuttX mailing list <https://nuttx.apache.org/community/>`_ – a
very active mailing list, the place to get help with your application or any
questions you have about NuttX.
* `Apache NuttX YouTube channel
<https://www.youtube.com/channel/UC0QciIlcUnjJkL5yJJBmluw/videos>`_ – Alan
Carvalho de Assis's YouTube channel on NuttX. It's a source of a lot of great
practical information.
* `Apache NuttX Coding Standard
<https://cwiki.apache.org/confluence/display/NUTTX/Coding+Standard>`_ — How
code should look when you submit new files or modify existing ones.
diff --git a/content/docs/latest/_sources/quickstart/organization.rst.txt
b/content/docs/latest/_sources/quickstart/organization.rst.txt
index b03d5c2..eaf3b95 100644
--- a/content/docs/latest/_sources/quickstart/organization.rst.txt
+++ b/content/docs/latest/_sources/quickstart/organization.rst.txt
@@ -316,7 +316,7 @@ contents of these configuration files.
which is the path to the root directory of the build. This
makefile fragment should include:
- - ``$(TOPDIR)/.config`` : Nuttx configuration
+ - ``$(TOPDIR)/.config`` : NuttX configuration
- ``$(TOPDIR)/tools/Config.mk`` : Common definitions
Definitions in the ``Make.defs`` file probably depend on some
diff --git
a/content/docs/latest/_sources/reference/user/02_task_scheduling.rst.txt
b/content/docs/latest/_sources/reference/user/02_task_scheduling.rst.txt
index 6ccb7c4..c24b2dc 100644
--- a/content/docs/latest/_sources/reference/user/02_task_scheduling.rst.txt
+++ b/content/docs/latest/_sources/reference/user/02_task_scheduling.rst.txt
@@ -6,7 +6,7 @@ priority have exclusive access to the CPU until they become
blocked. At
that time, the CPU is available to tasks of lower priority. Tasks of
equal priority are scheduled FIFO.
-Optionally, a Nuttx task or thread can be configured with round-robin or
+Optionally, a NuttX task or thread can be configured with round-robin or
*sporadic* scheduler. The round-robin is similar to priority scheduling
*except* that tasks with equal priority and share CPU time via
*time-slicing*. The time-slice interval is a constant determined by the
diff --git a/content/docs/latest/_sources/reference/user/09_env_vars.rst.txt
b/content/docs/latest/_sources/reference/user/09_env_vars.rst.txt
index 9d7b65d..5b82469 100644
--- a/content/docs/latest/_sources/reference/user/09_env_vars.rst.txt
+++ b/content/docs/latest/_sources/reference/user/09_env_vars.rst.txt
@@ -25,7 +25,7 @@ Programming Interfaces
======================
The following environment variable
-programming interfaces are provided by Nuttx and are described in detail
+programming interfaces are provided by NuttX and are described in detail
in the following paragraphs.
- :c:func:`getenv`
diff --git a/content/docs/latest/_sources/reference/user/10_filesystem.rst.txt
b/content/docs/latest/_sources/reference/user/10_filesystem.rst.txt
index 40ccbb9..4d2762e 100644
--- a/content/docs/latest/_sources/reference/user/10_filesystem.rst.txt
+++ b/content/docs/latest/_sources/reference/user/10_filesystem.rst.txt
@@ -20,7 +20,7 @@ system).
Any user supplied data or logic can be accessed via the pseudo-file
system. Built in support is provided for character and block
-`driver <NuttxPortingGuide.html#DeviceDrivers>`__ *nodes* in the any
+`driver <NuttXPortingGuide.html#DeviceDrivers>`__ *nodes* in the any
pseudo file system directory. (By convention, however, all driver nodes
should be in the ``/dev`` pseudo file system directory).
diff --git a/content/docs/latest/_sources/reference/user/index.rst.txt
b/content/docs/latest/_sources/reference/user/index.rst.txt
index b6f3774..4eb87e1 100644
--- a/content/docs/latest/_sources/reference/user/index.rst.txt
+++ b/content/docs/latest/_sources/reference/user/index.rst.txt
@@ -13,11 +13,11 @@ limited to addressing only NuttX RTOS APIs that are
available to the
application developer. As such, this document does not focus on any
technical details of the organization or implementation of NuttX. Those
technical details are provided in the `NuttX Porting
-Guide <NuttxPortingGuide.html>`__.
+Guide <NuttXPortingGuide.html>`__.
Information about configuring and building NuttX is also needed by the
application developer. That information can also be found in the `NuttX
-Porting Guide <NuttxPortingGuide.html#configandbuild>`__.
+Porting Guide <NuttXPortingGuide.html#configandbuild>`__.
.. toctree::
:maxdepth: 1
diff --git a/content/docs/latest/applications/nsh/commands.html
b/content/docs/latest/applications/nsh/commands.html
index 1fed773..e5a350e 100644
--- a/content/docs/latest/applications/nsh/commands.html
+++ b/content/docs/latest/applications/nsh/commands.html
@@ -968,7 +968,7 @@ at <link> for the existing file or directory,
<target>. This
implementation is simplified for use with NuttX in these ways:</p>
<blockquote>
<div><ul class="simple">
-<li><p>Links may be created only within the NuttX top-level, <a
class="reference external" href="NuttxUserGuide.html#FileSystemOverview">pseudo
+<li><p>Links may be created only within the NuttX top-level, <a
class="reference external" href="NuttXUserGuide.html#FileSystemOverview">pseudo
file system</a>. No
file system currently supported by NuttX provides symbolic
links.</p></li>
@@ -1128,7 +1128,7 @@ have been mounted with a command like:</p>
of <code class="docutils literal notranslate"><span
class="pre"><path></span></code> except the final directory name must
exist on a
mounted file system; the final directory must not.</p>
<p><strong>Limited to Mounted File Systems</strong>. Recall that NuttX uses a
-<a class="reference external"
href="NuttxUserGuide.html#FileSystemOverview">pseudo file system</a>
+<a class="reference external"
href="NuttXUserGuide.html#FileSystemOverview">pseudo file system</a>
for its root file system. The <code class="docutils literal notranslate"><span
class="pre">mkdir</span></code> command can only be used
to create directories in volumes set up with the
<code class="docutils literal notranslate"><span
class="pre">`mount</span></code> <#cmdmount>`__ command; it cannot be
used to create
@@ -1164,7 +1164,7 @@ cards. The default is 512 entries in all cases.</p>
zero because the FAT32 root directory is a cluster chain.</p>
<p>NSH provides this command to access the
<code class="docutils literal notranslate"><span
class="pre">`mkfatfs()</span></code> <mkfatfs>`__ NuttX API. This block
device must
-reside in the NuttX <a class="reference external"
href="NuttxUserGuide.html#FileSystemOverview">pseudo file
+reside in the NuttX <a class="reference external"
href="NuttXUserGuide.html#FileSystemOverview">pseudo file
system</a> and must have
been created by some call to <code class="docutils literal notranslate"><span
class="pre">register_blockdriver()</span></code> (see
<code class="docutils literal notranslate"><span
class="pre">include/nuttx/fs/fs.h</span></code>).</p>
@@ -1181,7 +1181,7 @@ be needed to complete the <code class="docutils literal
notranslate"><span class
device drivers are place in the standard <code class="docutils literal
notranslate"><span class="pre">/dev</span></code> directory. After
it is created, the FIFO device may be used as any other device
driver. NSH provides this command to access the
-<code class="docutils literal notranslate"><span
class="pre">`mkfifo()</span></code> <NuttxUserGuide.html#mkfifo>`__ NuttX
API.</p>
+<code class="docutils literal notranslate"><span
class="pre">`mkfifo()</span></code> <NuttXUserGuide.html#mkfifo>`__ NuttX
API.</p>
<p><strong>Example</strong>:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>nsh> ls -l /dev
/dev:
@@ -1262,16 +1262,16 @@ type of file system that has been formatted on the
<code class="docutils literal notranslate"><span
class="pre"><block-device></span></code>. As of this writing, <code
class="docutils literal notranslate"><span class="pre">vfat</span></code> is
the only
supported value for <code class="docutils literal notranslate"><span
class="pre"><fstype></span></code></p></li>
<li><p><strong>Block Device.</strong> The <code class="docutils literal
notranslate"><span class="pre"><block-device></span></code> argument is
the full
-or relative path to a block driver inode in the <a class="reference external"
href="NuttxUserGuide.html#FileSystemOverview">pseudo file
+or relative path to a block driver inode in the <a class="reference external"
href="NuttXUserGuide.html#FileSystemOverview">pseudo file
system</a>. By
convention, this is a name under the <code class="docutils literal
notranslate"><span class="pre">/dev</span></code> sub-directory.
This <code class="docutils literal notranslate"><span
class="pre"><block-device></span></code> must have been previously
formatted
with the same file system type as specified by <code class="docutils literal
notranslate"><span class="pre"><fstype></span></code></p></li>
<li><p><strong>Mount Point.</strong> The mount point, <code class="docutils
literal notranslate"><span class="pre"><dir-path></span></code>, is the
-location in the <a class="reference external"
href="NuttxUserGuide.html#FileSystemOverview">pseudo file
+location in the <a class="reference external"
href="NuttXUserGuide.html#FileSystemOverview">pseudo file
system</a> where the
mounted volume will appear. This mount point can only reside in
-the NuttX <a class="reference external"
href="NuttxUserGuide.html#FileSystemOverview">pseudo file
+the NuttX <a class="reference external"
href="NuttXUserGuide.html#FileSystemOverview">pseudo file
system</a>. By
convention, this mount point is a subdirectory under <code class="docutils
literal notranslate"><span class="pre">/mnt</span></code>.
The mount command will create whatever pseudo directories that
@@ -1279,7 +1279,7 @@ may be needed to complete the full path but the full path
must
not already exist.</p></li>
</ol>
</div></blockquote>
-<p>After the volume has been mounted in the NuttX <a class="reference
external" href="NuttxUserGuide.html#FileSystemOverview">pseudo file
+<p>After the volume has been mounted in the NuttX <a class="reference
external" href="NuttXUserGuide.html#FileSystemOverview">pseudo file
system</a>, it may be
access in the same way as other objects in the file system.</p>
<p><strong>Examples</strong>:</p>
@@ -1447,7 +1447,7 @@ redundant.</p>
</pre></div>
</div>
<p><strong>Synopsis</strong>. Remove the specified <code class="docutils
literal notranslate"><span class="pre"><file-path></span></code> name
from the
-mounted file system. Recall that NuttX uses a <a class="reference external"
href="NuttxUserGuide.html#FileSystemOverview">pseudo file
+mounted file system. Recall that NuttX uses a <a class="reference external"
href="NuttXUserGuide.html#FileSystemOverview">pseudo file
system</a> for its root
file system. The <code class="docutils literal notranslate"><span
class="pre">rm</span></code> command can only be used to remove
(unlink) files in volumes set up with the
@@ -1473,7 +1473,7 @@ nsh>
</pre></div>
</div>
<p><strong>Synopsis</strong>. Remove the specified <code class="docutils
literal notranslate"><span class="pre"><dir-path></span></code> directory
from
-the mounted file system. Recall that NuttX uses a <a class="reference
external" href="NuttxUserGuide.html#FileSystemOverview">pseudo file
+the mounted file system. Recall that NuttX uses a <a class="reference
external" href="NuttXUserGuide.html#FileSystemOverview">pseudo file
system</a> for its root
file system. The <code class="docutils literal notranslate"><span
class="pre">rmdir</span></code> command can only be used to remove
directories from volumes set up with the <code class="docutils literal
notranslate"><span class="pre">`mount</span></code> <#cmdmount>`__
diff --git a/content/docs/latest/applications/nsh/config.html
b/content/docs/latest/applications/nsh/config.html
index c6bc5d7..0bd2012 100644
--- a/content/docs/latest/applications/nsh/config.html
+++ b/content/docs/latest/applications/nsh/config.html
@@ -221,7 +221,7 @@
may not be enabled in the NuttX configuration file. The following
<a class="reference external" href="#cmddependencies">table</a> indicates the
dependency of each command on
NuttX configuration settings. General configuration settings are
-discussed in the <a class="reference external"
href="NuttxPortingGuide.html">NuttX Porting Guide.</a>
+discussed in the <a class="reference external"
href="NuttXPortingGuide.html">NuttX Porting Guide.</a>
Configuration settings specific to NSH as discussed at the
<a class="reference external" href="#nshconfiguration">bottom</a> of this
document.</p>
<p>Note that in addition to general NuttX configuration settings, each NSH
diff --git a/content/docs/latest/components/drivers/character/index.html
b/content/docs/latest/components/drivers/character/index.html
index 979d35e..8954f0c 100644
--- a/content/docs/latest/components/drivers/character/index.html
+++ b/content/docs/latest/components/drivers/character/index.html
@@ -243,7 +243,7 @@ Each character driver registers itself by calling
appear in the <a class="reference external"
href="#NxFileSystem">pseudo-file-system</a> and it’s
initialized instance of <code class="docutils literal notranslate"><span
class="pre">struct</span> <span
class="pre">file_operations</span></code>.</p></li>
<li><p><strong>User Access</strong>. After it has been registered, the
character
-driver can be accessed by user code using the standard <a class="reference
external" href="NuttxUserGuide.html#driveroperations">driver
+driver can be accessed by user code using the standard <a class="reference
external" href="NuttXUserGuide.html#driveroperations">driver
operations</a> including
<code class="docutils literal notranslate"><span
class="pre">open()</span></code>, <code class="docutils literal
notranslate"><span class="pre">close()</span></code>, <code class="docutils
literal notranslate"><span class="pre">read()</span></code>, <code
class="docutils literal notranslate"><span class="pre">write()</span></code>,
etc.</p></li>
<li><p><strong>Specialized Character Drivers</strong>. Within the common
character
diff --git a/content/docs/latest/components/drivers/special/syslog.html
b/content/docs/latest/components/drivers/special/syslog.html
index 432854a..26cd31a 100644
--- a/content/docs/latest/components/drivers/special/syslog.html
+++ b/content/docs/latest/components/drivers/special/syslog.html
@@ -629,7 +629,7 @@ when used with time critical drivers.</p>
debugging output in a circular buffer in RAM. It differs from a
pipe in numerous details as needed to support logging.</p>
<p>This driver is built when <code class="docutils literal notranslate"><span
class="pre">CONFIG_RAMLOG</span></code> is defined in the
-Nuttx configuration.</p>
+NuttX configuration.</p>
<div class="section" id="dmesg-command">
<h3><code class="docutils literal notranslate"><span
class="pre">dmesg</span></code> command<a class="headerlink"
href="#dmesg-command" title="Permalink to this headline">¶</a></h3>
<p>When the RAMLOG (with SYSLOG) is enabled, a new NuttShell (NSH)
diff --git a/content/docs/latest/components/nxflat.html
b/content/docs/latest/components/nxflat.html
index d2fbc70..9e71063 100644
--- a/content/docs/latest/components/nxflat.html
+++ b/content/docs/latest/components/nxflat.html
@@ -268,7 +268,7 @@ support execution NXFLAT binaries from an SRAM copy as
well.</p>
is a toolchain add that provides full shared library and XIP executable
support for processors that have no Memory Management Unit
(MMU:sup:<cite>1</cite>). NXFLAT is greatly simplified for the deeply embedded
-environment targeted by Nuttx:</p>
+environment targeted by NuttX:</p>
<blockquote>
<div><ul class="simple">
<li><p>NXFLAT does not support shared libraries, because</p></li>
@@ -364,7 +364,7 @@ buildroot can be downloaded from
will need version 0.1.7 or later.</p>
<p>Here are some general build instructions:</p>
<ul class="simple">
-<li><p>You must have already configured Nuttx in <code class="docutils literal
notranslate"><span class="pre"><some-dir>/nuttx</span></code></p></li>
+<li><p>You must have already configured NuttX in <code class="docutils literal
notranslate"><span class="pre"><some-dir>/nuttx</span></code></p></li>
<li><p>Download the buildroot package <code class="docutils literal
notranslate"><span class="pre">buildroot-0.x.y</span></code> into
<code class="docutils literal notranslate"><span
class="pre"><some-dir></span></code></p></li>
<li><p>Unpack <code class="docutils literal notranslate"><span
class="pre"><some-dir>/buildroot-0.x.y.tar.gz</span></code> using a
command like <code class="docutils literal notranslate"><span
class="pre">tar</span> <span class="pre">zxf</span> <span
class="pre">buildroot-0.x.y</span></code>. This will result in a new directory
like <code class="docutils literal notranslate"><span
class="pre"><some-dir>/buildroot-0.x.y</span></code></p></li>
diff --git a/content/docs/latest/guides/nfs.html
b/content/docs/latest/guides/nfs.html
index 436a457..4336099 100644
--- a/content/docs/latest/guides/nfs.html
+++ b/content/docs/latest/guides/nfs.html
@@ -237,7 +237,7 @@ minimum, you need to have the following selections:</p>
<h2>Mount Interface<a class="headerlink" href="#mount-interface"
title="Permalink to this headline">¶</a></h2>
<p>A low-level, C-callable interface is provided to mount a file system.
That interface is called <code class="docutils literal notranslate"><span
class="pre">mount()</span></code> and is mentioned in the
-<code class="docutils literal notranslate"><span class="pre">`porting</span>
<span class="pre">guide</span></code>
<NuttxPortingGuide.html#NxFileSystem>`__ and is
+<code class="docutils literal notranslate"><span class="pre">`porting</span>
<span class="pre">guide</span></code>
<NuttXPortingGuide.html#NxFileSystem>`__ and is
prototyped in the header file <code class="docutils literal notranslate"><span
class="pre">include/sys/mount.h</span></code>:</p>
<dl class="c function">
<dt id="c.mount">
diff --git a/content/docs/latest/guides/simulator.html
b/content/docs/latest/guides/simulator.html
index da65d98..85f68ac 100644
--- a/content/docs/latest/guides/simulator.html
+++ b/content/docs/latest/guides/simulator.html
@@ -345,7 +345,7 @@ be an ethernet or wireless network adapter. Do this:</p>
that it has an IP address on the local net. There may be other interfaces
listed, you’ll
need to pick the one that’s right for your system.</p>
<p>Then, on Linux do this to set up the tap network interface and route that
will let
-the Apache Nuttx simulator access the network:</p>
+the Apache NuttX simulator access the network:</p>
<blockquote>
<div><div class="highlight-console notranslate"><div
class="highlight"><pre><span></span><span class="gp">$</span> sudo
./tools/simhostroute.sh wlp0s20f3 on
<span class="gp">$</span> ping -c <span class="m">1</span> <span
class="m">10</span>.0.1.2 <span class="c1"># nuttx system</span>
diff --git a/content/docs/latest/guides/tasktraceuser.html
b/content/docs/latest/guides/tasktraceuser.html
index 476becf..69e2441 100644
--- a/content/docs/latest/guides/tasktraceuser.html
+++ b/content/docs/latest/guides/tasktraceuser.html
@@ -249,6 +249,7 @@ If the following bits are set, the corresponding
instrumentations are enabled on
<li><p>Bit 0 = Enable instrumentation</p></li>
<li><p>Bit 1 = Enable syscall instrumentation</p></li>
<li><p>Bit 2 = Enable IRQ instrumentation</p></li>
+<li><p>Bit 3 = Enable collecting syscall arguments</p></li>
</ul>
</li>
</ul>
@@ -265,6 +266,11 @@ Higher value can hold more note records, but consumes more
kernel memory.</p></l
This is useful to keep instrumentation data of the beginning of a system
boot.</p></li>
</ul>
</li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_SCHED_INSTRUMENTATION_HIRES</span></code></p>
+<ul>
+<li><p>If enabled, use higher resolution system timer for
instrumentation.</p></li>
+</ul>
+</li>
</ul>
<p>After the configuration, rebuild the NuttX kernel and application.</p>
<p>If the trace function is enabled, “<code class="docutils literal
notranslate"><span class="pre">trace</span></code>” <span class="xref std
std-doc">../components/nsh/builtin</span> will be available.</p>
@@ -392,7 +398,7 @@ If not specified, the trace result is displayed to
console.</p></li>
<p>Set the task trace mode options.
The default value is given by the kernel configuration <code class="docutils
literal notranslate"><span
class="pre">CONFIG_SCHED_INSTRUMENTATION_FILTER_DEFAULT_MODE</span></code>.</p>
<p><strong>Command Syntax:</strong></p>
-<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>trace mode [{+|-}{o|s|i}...]
+<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>trace mode [{+|-}{o|s|a|i}...]
</pre></div>
</div>
<ul class="simple">
@@ -406,6 +412,9 @@ This is useful to keep the data of the beginning of the
trace.</p></li>
It records the event of enter/leave system call which is issued by the
application.
All system calls are recorded by default. <code class="docutils literal
notranslate"><span class="pre">trace</span> <span
class="pre">syscall</span></code> command can filter the system calls to be
recorded.</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">-s</span></code> : Disable system call trace.</p></li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">+a</span></code> : Enable recording the system call arguments.
+It records the arguments passed to the issued system call to the trace
data.</p></li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">-a</span></code> : Disable recording the system call
arguments.</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">+i</span></code> : Enable interrupt trace.
It records the event of enter/leave interrupt handler which is occured while
the tracing.
All IRQs are recorded by default. <code class="docutils literal
notranslate"><span class="pre">trace</span> <span class="pre">irq</span></code>
command can filter the IRQs to be recorded.</p></li>
@@ -419,6 +428,7 @@ Task trace mode:
Overwrite : on (+o)
Syscall trace : on (+s)
Filtered Syscalls : 16
+ Syscall trace with args : on (+a)
IRQ trace : on (+i)
Filtered IRQs : 2
</pre></div>
diff --git a/content/docs/latest/index.html b/content/docs/latest/index.html
index 57770d1..41cf349 100644
--- a/content/docs/latest/index.html
+++ b/content/docs/latest/index.html
@@ -207,7 +207,7 @@ by following these <a class="reference internal"
href="contributing/documentatio
<div class="section" id="nuttx-documentation">
<h1>NuttX Documentation<a class="headerlink" href="#nuttx-documentation"
title="Permalink to this headline">¶</a></h1>
<p>NuttX is a real-time operating system (RTOS) with an emphasis on standards
compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller
environments, the primary governing standards in NuttX are POSIX and ANSI
standards. Additional standard APIs from Unix and other common RTOS’s (such as
VxWorks) are adopted for functionality not available under these standards, or
for functionality that is not appropriate for deeply-embedded environments
(such as fork()).</p>
-<p>Last Updated: 20 October 20 at 00:53</p>
+<p>Last Updated: 21 October 20 at 00:53</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Table of Contents</span></p>
<ul class="current">
diff --git a/content/docs/latest/introduction/detailed_support.html
b/content/docs/latest/introduction/detailed_support.html
index 973627b..bbb3ca6 100644
--- a/content/docs/latest/introduction/detailed_support.html
+++ b/content/docs/latest/introduction/detailed_support.html
@@ -552,7 +552,7 @@ that can be used as the basis for further application
development.</p></li>
<li><p>A full-loaded NuttShell (<a class="reference internal"
href="../applications/nsh/nsh.html#nsh"><span class="std
std-ref">NSH</span></a>) configuration
that demonstrates all of the SAMA5D3x features.</p></li>
</ul>
-<p>The following support was added in Nuttx 6.30:</p>
+<p>The following support was added in NuttX 6.30:</p>
<ul class="simple">
<li><p>DMA support, and</p></li>
<li><p>PIO interrupts,</p></li>
@@ -1261,7 +1261,7 @@ Networking, LCD, and touchscreen support were added in
NuttX-6.33.</p>
the STM32F103 or STM32F107 part.</p></li>
<li><p>A network-enabled NuttShell (NSH) configuration that will work only
with the STM32F107 part.</p></li>
-<li><p>The configuration that was used to verify the Nuttx <a class="reference
external"
href="https://cwiki.apache.org/confluence/display/NUTTX/High+Performance%2C+Zero+Latency+Interrupts";>high-priority,
+<li><p>The configuration that was used to verify the NuttX <a class="reference
external"
href="https://cwiki.apache.org/confluence/display/NUTTX/High+Performance%2C+Zero+Latency+Interrupts";>high-priority,
nested interrupt
feature</a>.</p></li>
</ol>
@@ -1449,7 +1449,7 @@ file for further information.</p>
<li><p><strong>Zilogic’s ZKIT-ARM-1769 board</strong></p>
<p>Zilogic System’s ARM development Kit, ZKIT-ARM-1769. This board is
based on the NXP LPC1769. The initial release was included
-NuttX-6.26. The Nuttx Buildroot toolchain is used by default. Verifed
+NuttX-6.26. The NuttX Buildroot toolchain is used by default. Verifed
configurations include the “Hello, World!” example application and a
THTTPD demonstration. Refer to the NuttX board
<a class="reference external"
href="https://github.com/apache/incubator-nuttx/blob/master/boards/arm/lpc17xx_40xx/zkit-arm-1769/README.txt";>README</a>
@@ -2593,7 +2593,7 @@ NuttX-7.26 release. These unverfied drivers include: SPI,
I2C, DMA, USB.
Also refer to the NuttX board
<a class="reference external"
href="https://github.com/apache/incubator-nuttx/blob/master/boards/arm/samd5e5/metro-m4/README.txt";>README</a>
file for further information about the current state of the port.</p>
-<p>Nuttx-9.0 added basic support for Microchip SAME54 Xplained Pro board.
+<p>NuttX-9.0 added basic support for Microchip SAME54 Xplained Pro board.
An ethernet driver was also added to the SAME5x familly.</p>
</div>
<div class="section" id="stmicro-stm32-f72x-f73x">
@@ -3111,7 +3111,7 @@ and a cluster of 8 RI5CY cores that runs at a bit slower
speed. The GAP8
is an implementation of the opensource PULP platform, a
Parallel-Ultra-Low-Power design.</p>
<p><a class="reference external" href="#k210">Sipeed Maix bit</a></p>
-<p>Initial support for the Sipeed Maix bit board was added in Nuttx-9.0.</p>
+<p>Initial support for the Sipeed Maix bit board was added in NuttX-9.0.</p>
</div>
<div class="section" id="litex-on-arty-a7">
<h3>LiteX on ARTY A7<a class="headerlink" href="#litex-on-arty-a7"
title="Permalink to this headline">¶</a></h3>
diff --git a/content/docs/latest/introduction/resources.html
b/content/docs/latest/introduction/resources.html
index 6113e79..b40c989 100644
--- a/content/docs/latest/introduction/resources.html
+++ b/content/docs/latest/introduction/resources.html
@@ -217,7 +217,7 @@
<li><p>Apache NuttX</p>
<ul>
<li><p><a class="reference external" href="https://apache.nuttx.org";>Apache
NuttX website</a></p></li>
-<li><p><a class="reference external"
href="https://cwiki.apache.org/confluence/display/NUTTX/Nuttx";>Apache NuttX
online documentation</a></p></li>
+<li><p><a class="reference external"
href="https://cwiki.apache.org/confluence/display/NUTTX/NuttX";>Apache NuttX
online documentation</a></p></li>
<li><p><a class="reference external"
href="https://nuttx.apache.org/community/";>Apache NuttX mailing list</a> – a
very active mailing list, the place to get help with your application or any
questions you have about NuttX.</p></li>
<li><p><a class="reference external"
href="https://www.youtube.com/channel/UC0QciIlcUnjJkL5yJJBmluw/videos";>Apache
NuttX YouTube channel</a> – Alan Carvalho de Assis’s YouTube channel on NuttX.
It’s a source of a lot of great practical information.</p></li>
<li><p><a class="reference external"
href="https://cwiki.apache.org/confluence/display/NUTTX/Coding+Standard";>Apache
NuttX Coding Standard</a> — How code should look when you submit new files or
modify existing ones.</p></li>
diff --git a/content/docs/latest/quickstart/organization.html
b/content/docs/latest/quickstart/organization.html
index 588d8a3..4d84314 100644
--- a/content/docs/latest/quickstart/organization.html
+++ b/content/docs/latest/quickstart/organization.html
@@ -529,7 +529,7 @@ fragment should define:</p>
which is the path to the root directory of the build. This
makefile fragment should include:</p>
<ul class="simple">
-<li><p><code class="docutils literal notranslate"><span
class="pre">$(TOPDIR)/.config</span></code> : Nuttx configuration</p></li>
+<li><p><code class="docutils literal notranslate"><span
class="pre">$(TOPDIR)/.config</span></code> : NuttX configuration</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">$(TOPDIR)/tools/Config.mk</span></code> : Common
definitions</p></li>
</ul>
<p>Definitions in the <code class="docutils literal notranslate"><span
class="pre">Make.defs</span></code> file probably depend on some
diff --git a/content/docs/latest/reference/user/02_task_scheduling.html
b/content/docs/latest/reference/user/02_task_scheduling.html
index 6816350..a04fb76 100644
--- a/content/docs/latest/reference/user/02_task_scheduling.html
+++ b/content/docs/latest/reference/user/02_task_scheduling.html
@@ -226,7 +226,7 @@
priority have exclusive access to the CPU until they become blocked. At
that time, the CPU is available to tasks of lower priority. Tasks of
equal priority are scheduled FIFO.</p>
-<p>Optionally, a Nuttx task or thread can be configured with round-robin or
+<p>Optionally, a NuttX task or thread can be configured with round-robin or
<em>sporadic</em> scheduler. The round-robin is similar to priority scheduling
<em>except</em> that tasks with equal priority and share CPU time via
<em>time-slicing</em>. The time-slice interval is a constant determined by the
diff --git a/content/docs/latest/reference/user/09_env_vars.html
b/content/docs/latest/reference/user/09_env_vars.html
index d213d48..8505bfc 100644
--- a/content/docs/latest/reference/user/09_env_vars.html
+++ b/content/docs/latest/reference/user/09_env_vars.html
@@ -246,7 +246,7 @@ parentage.</p></li>
<div class="section" id="programming-interfaces">
<h2>Programming Interfaces<a class="headerlink" href="#programming-interfaces"
title="Permalink to this headline">¶</a></h2>
<p>The following environment variable
-programming interfaces are provided by Nuttx and are described in detail
+programming interfaces are provided by NuttX and are described in detail
in the following paragraphs.</p>
<blockquote>
<div><ul class="simple">
diff --git a/content/docs/latest/reference/user/10_filesystem.html
b/content/docs/latest/reference/user/10_filesystem.html
index dc9a0f8..242ba43 100644
--- a/content/docs/latest/reference/user/10_filesystem.html
+++ b/content/docs/latest/reference/user/10_filesystem.html
@@ -238,7 +238,7 @@ Linux <code class="docutils literal notranslate"><span
class="pre">/proc</span><
system).</p>
<p>Any user supplied data or logic can be accessed via the pseudo-file
system. Built in support is provided for character and block
-<a class="reference external"
href="NuttxPortingGuide.html#DeviceDrivers">driver</a> <em>nodes</em> in the any
+<a class="reference external"
href="NuttXPortingGuide.html#DeviceDrivers">driver</a> <em>nodes</em> in the any
pseudo file system directory. (By convention, however, all driver nodes
should be in the <code class="docutils literal notranslate"><span
class="pre">/dev</span></code> pseudo file system directory).</p>
<p><strong>Mounted File Systems</strong> The simple in-memory file system can
be
diff --git a/content/docs/latest/reference/user/index.html
b/content/docs/latest/reference/user/index.html
index f5834b3..dff1277 100644
--- a/content/docs/latest/reference/user/index.html
+++ b/content/docs/latest/reference/user/index.html
@@ -228,10 +228,10 @@ implementing applications on NuttX. Specifically, this
documented is
limited to addressing only NuttX RTOS APIs that are available to the
application developer. As such, this document does not focus on any
technical details of the organization or implementation of NuttX. Those
-technical details are provided in the <a class="reference external"
href="NuttxPortingGuide.html">NuttX Porting
+technical details are provided in the <a class="reference external"
href="NuttXPortingGuide.html">NuttX Porting
Guide</a>.</p>
<p>Information about configuring and building NuttX is also needed by the
-application developer. That information can also be found in the <a
class="reference external" href="NuttxPortingGuide.html#configandbuild">NuttX
+application developer. That information can also be found in the <a
class="reference external" href="NuttXPortingGuide.html#configandbuild">NuttX
Porting Guide</a>.</p>
<div class="toctree-wrapper compound">
<p class="caption"><span class="caption-text">Contents</span></p>
diff --git a/content/docs/latest/searchindex.js
b/content/docs/latest/searchindex.js
index 74b4ae4..5a9b15f 100644
--- a/content/docs/latest/searchindex.js
+++ b/content/docs/latest/searchindex.js
@@ -1 +1 @@
-Search.setIndex({docnames:["applications/index","applications/nsh/builtin","applications/nsh/commands","applications/nsh/config","applications/nsh/customizing","applications/nsh/index","applications/nsh/installation","applications/nsh/login","applications/nsh/nsh","boards/index","components/binfmt","components/drivers/block/index","components/drivers/character/analog","components/drivers/character/can","components/drivers/character/index","components/drivers/character/keypad","components
[...]
\ No newline at end of file
+Search.setIndex({docnames:["applications/index","applications/nsh/builtin","applications/nsh/commands","applications/nsh/config","applications/nsh/customizing","applications/nsh/index","applications/nsh/installation","applications/nsh/login","applications/nsh/nsh","boards/index","components/binfmt","components/drivers/block/index","components/drivers/character/analog","components/drivers/character/can","components/drivers/character/index","components/drivers/character/keypad","components
[...]
\ No newline at end of file
diff --git a/content/feed.xml b/content/feed.xml
index 9c6dd1b..4e4786f 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -5,8 +5,8 @@
<description></description>
<link>/</link>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Tue, 20 Oct 2020 00:55:10 +0000</pubDate>
- <lastBuildDate>Tue, 20 Oct 2020 00:55:10 +0000</lastBuildDate>
+ <pubDate>Wed, 21 Oct 2020 00:55:14 +0000</pubDate>
+ <lastBuildDate>Wed, 21 Oct 2020 00:55:14 +0000</lastBuildDate>
<generator>Jekyll v3.8.5</generator>
<item>
