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 8927abd Publishing web: 6758fc5efbbf5ed16c807ccdfb012d94d1db201a
docs: 40144a652d8c5e86e4a0c578ee57adf298466dfd
8927abd is described below
commit 8927abd443f24e4b352aeb7c09f676a456ef2f6b
Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
AuthorDate: Tue Oct 4 00:18:15 2022 +0000
Publishing web: 6758fc5efbbf5ed16c807ccdfb012d94d1db201a docs:
40144a652d8c5e86e4a0c578ee57adf298466dfd
---
content/docs/10.0.0/index.html | 2 +-
content/docs/10.0.1/index.html | 2 +-
content/docs/10.1.0/index.html | 2 +-
content/docs/10.2.0/index.html | 2 +-
content/docs/10.3.0/index.html | 2 +-
.../_sources/platforms/xtensa/esp32/index.rst.txt | 5 +++--
.../reference/user/05_counting_semaphore.rst.txt | 17 -----------------
content/docs/latest/index.html | 2 +-
content/docs/latest/platforms/xtensa/esp32/index.html | 5 +++--
.../latest/reference/user/05_counting_semaphore.html | 16 ----------------
content/docs/latest/searchindex.js | 2 +-
content/feed.xml | 4 ++--
12 files changed, 15 insertions(+), 46 deletions(-)
diff --git a/content/docs/10.0.0/index.html b/content/docs/10.0.0/index.html
index c23b88b..271a41f 100644
--- a/content/docs/10.0.0/index.html
+++ b/content/docs/10.0.0/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 32-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: 03 October 22 at 00:15</p>
+<p>Last Updated: 04 October 22 at 00:15</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/10.0.1/index.html b/content/docs/10.0.1/index.html
index 599ffed..737e231 100644
--- a/content/docs/10.0.1/index.html
+++ b/content/docs/10.0.1/index.html
@@ -217,7 +217,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 32-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: 03 October 22 at 00:15</p>
+<p>Last Updated: 04 October 22 at 00:16</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/10.1.0/index.html b/content/docs/10.1.0/index.html
index 20d042f..39021b7 100644
--- a/content/docs/10.1.0/index.html
+++ b/content/docs/10.1.0/index.html
@@ -217,7 +217,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: 03 October 22 at 00:15</p>
+<p>Last Updated: 04 October 22 at 00:16</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/10.2.0/index.html b/content/docs/10.2.0/index.html
index 01fdd64..628da19 100644
--- a/content/docs/10.2.0/index.html
+++ b/content/docs/10.2.0/index.html
@@ -218,7 +218,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: 03 October 22 at 00:15</p>
+<p>Last Updated: 04 October 22 at 00:16</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/10.3.0/index.html b/content/docs/10.3.0/index.html
index 7074b9e..628da19 100644
--- a/content/docs/10.3.0/index.html
+++ b/content/docs/10.3.0/index.html
@@ -218,7 +218,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: 03 October 22 at 00:16</p>
+<p>Last Updated: 04 October 22 at 00:16</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/_sources/platforms/xtensa/esp32/index.rst.txt
b/content/docs/latest/_sources/platforms/xtensa/esp32/index.rst.txt
index 6e5eec9..c8110b1 100644
--- a/content/docs/latest/_sources/platforms/xtensa/esp32/index.rst.txt
+++ b/content/docs/latest/_sources/platforms/xtensa/esp32/index.rst.txt
@@ -298,11 +298,12 @@ to connect your smartphone or laptop to your board::
nsh> ifup wlan1
nsh> dhcpd_start wlan1
- nsh> wapi psk wlan0 mypasswd 1
+ nsh> wapi psk wlan1 mypasswd 3
nsh> wapi essid wlan1 nuttxap 1
In this case, you are creating the access point ``nuttxapp`` in your board and
to
-connect to it on your smartphone you will be required to type the password
``mypasswd``.
+connect to it on your smartphone you will be required to type the password
``mypasswd``
+using WPA2.
The ``dhcpd_start`` is necessary to let your board to associate an IP to your
smartphone.
Bluetooth
diff --git
a/content/docs/latest/_sources/reference/user/05_counting_semaphore.rst.txt
b/content/docs/latest/_sources/reference/user/05_counting_semaphore.rst.txt
index 3f940e7..693ba40 100644
--- a/content/docs/latest/_sources/reference/user/05_counting_semaphore.rst.txt
+++ b/content/docs/latest/_sources/reference/user/05_counting_semaphore.rst.txt
@@ -77,23 +77,6 @@ implementation:
slightly increased code size and around 6-12 bytes times the value of
``CONFIG_SEM_PREALLOCHOLDERS``.
- - ``CONFIG_SEM_NNESTPRIO``: In addition, there may be multiple
- threads of various priorities that need to wait for a count from the
- semaphore. These, the lower priority thread holding the semaphore may
- have to be boosted numerous times and, to make things more complex,
- will have to keep track of all of the boost priorities values in
- order to correctly restore the priorities after a count has been
- handed out to the higher priority thread. The
- ``CONFIG_SEM_NNESTPRIO`` defines the size of an array, one array per
- active thread. This setting is the maximum number of higher priority
- threads (minus 1) than can be waiting for another thread to release a
- count on a semaphore. This value may be set to zero if no more than
- one thread is expected to wait for a semaphore.
-
- The cost associated with setting ``CONFIG_SEM_NNESTPRIO`` is slightly
- increased code size and (``CONFIG_SEM_PREALLOCHOLDERS`` + 1) times
- the maximum number of active threads.
-
- **Increased Susceptibility to Bad Thread Behavior**. These various
structures tie the semaphore implementation more tightly to the
behavior of the implementation. For examples, if a thread executes
diff --git a/content/docs/latest/index.html b/content/docs/latest/index.html
index 7074b9e..d363d15 100644
--- a/content/docs/latest/index.html
+++ b/content/docs/latest/index.html
@@ -218,7 +218,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: 03 October 22 at 00:16</p>
+<p>Last Updated: 04 October 22 at 00:17</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/platforms/xtensa/esp32/index.html
b/content/docs/latest/platforms/xtensa/esp32/index.html
index a201345..d46465c 100644
--- a/content/docs/latest/platforms/xtensa/esp32/index.html
+++ b/content/docs/latest/platforms/xtensa/esp32/index.html
@@ -895,12 +895,13 @@ boards config examples called sta_softap which enables
this support</p>
to connect your smartphone or laptop to your board:</p>
<div class="highlight-none notranslate"><div
class="highlight"><pre><span></span>nsh> ifup wlan1
nsh> dhcpd_start wlan1
-nsh> wapi psk wlan0 mypasswd 1
+nsh> wapi psk wlan1 mypasswd 3
nsh> wapi essid wlan1 nuttxap 1
</pre></div>
</div>
<p>In this case, you are creating the access point <code class="docutils
literal notranslate"><span class="pre">nuttxapp</span></code> in your board and
to
-connect to it on your smartphone you will be required to type the password
<code class="docutils literal notranslate"><span
class="pre">mypasswd</span></code>.
+connect to it on your smartphone you will be required to type the password
<code class="docutils literal notranslate"><span
class="pre">mypasswd</span></code>
+using WPA2.
The <code class="docutils literal notranslate"><span
class="pre">dhcpd_start</span></code> is necessary to let your board to
associate an IP to your smartphone.</p>
</div>
<div class="section" id="bluetooth">
diff --git a/content/docs/latest/reference/user/05_counting_semaphore.html
b/content/docs/latest/reference/user/05_counting_semaphore.html
index 2f52d6c..028d4a8 100644
--- a/content/docs/latest/reference/user/05_counting_semaphore.html
+++ b/content/docs/latest/reference/user/05_counting_semaphore.html
@@ -307,22 +307,6 @@ using a counting semaphore.</p>
slightly increased code size and around 6-12 bytes times the value of
<code class="docutils literal notranslate"><span
class="pre">CONFIG_SEM_PREALLOCHOLDERS</span></code>.</p>
</li>
-<li><p><code class="docutils literal notranslate"><span
class="pre">CONFIG_SEM_NNESTPRIO</span></code>: In addition, there may be
multiple
-threads of various priorities that need to wait for a count from the
-semaphore. These, the lower priority thread holding the semaphore may
-have to be boosted numerous times and, to make things more complex,
-will have to keep track of all of the boost priorities values in
-order to correctly restore the priorities after a count has been
-handed out to the higher priority thread. The
-<code class="docutils literal notranslate"><span
class="pre">CONFIG_SEM_NNESTPRIO</span></code> defines the size of an array,
one array per
-active thread. This setting is the maximum number of higher priority
-threads (minus 1) than can be waiting for another thread to release a
-count on a semaphore. This value may be set to zero if no more than
-one thread is expected to wait for a semaphore.</p>
-<p>The cost associated with setting <code class="docutils literal
notranslate"><span class="pre">CONFIG_SEM_NNESTPRIO</span></code> is slightly
-increased code size and (<code class="docutils literal notranslate"><span
class="pre">CONFIG_SEM_PREALLOCHOLDERS</span></code> + 1) times
-the maximum number of active threads.</p>
-</li>
<li><p><strong>Increased Susceptibility to Bad Thread Behavior</strong>. These
various
structures tie the semaphore implementation more tightly to the
behavior of the implementation. For examples, if a thread executes
diff --git a/content/docs/latest/searchindex.js
b/content/docs/latest/searchindex.js
index 7f80334..a880bc9 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","components/binfmt","components/drivers/block/index","components/drivers/character/analog","components/drivers/character/can","components/drivers/character/foc","components/drivers/character/index","components/drivers/character
[...]
\ 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","components/binfmt","components/drivers/block/index","components/drivers/character/analog","components/drivers/character/can","components/drivers/character/foc","components/drivers/character/index","components/drivers/character
[...]
\ No newline at end of file
diff --git a/content/feed.xml b/content/feed.xml
index 836f3ca..eae6188 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>Mon, 03 Oct 2022 00:17:36 +0000</pubDate>
- <lastBuildDate>Mon, 03 Oct 2022 00:17:36 +0000</lastBuildDate>
+ <pubDate>Tue, 04 Oct 2022 00:18:12 +0000</pubDate>
+ <lastBuildDate>Tue, 04 Oct 2022 00:18:12 +0000</lastBuildDate>
<generator>Jekyll v3.8.5</generator>
<item>
